Re: is gtk 64-bit proof ?
- From: Erik Mouw <J A K Mouw its tudelft nl>
- To: gtk-devel-list redhat com
- Cc: Laurent Sauvebois ns mecalog fr
- Subject: Re: is gtk 64-bit proof ?
- Date: Tue, 26 Oct 99 14:57:19 +0200
On Tue, 26 Oct 1999 11:00:02 +0000, Laurent Sauvebois wrote:
> In order to compile a 64 bits object, i need to define CFLAGS as -mabi=64. Ok,
> no trouble, everything is compiling except .... at the end, when the Makefile
> is trying to create the libraries. and then, I got some troubles with the
> linker. I need to give the linker flag "-64", in order to force the linker
> mode in 64-bits-mode ( default is new 32 bits).
>
> so i tried LFLGAS = -64, or LDFLAGS = -64 , and each time, i stop here :
>
> /bin/sh ./libtool --mode=link gcc -mabi=64 -Wall -D_REENTRANT -64 -o
> libglib.la -rpath /usr/local/lib -version-info 0:6:0 -release 1.2
> -export-dynamic garray.lo gcache.lo gcompletion.lo gdataset.lo gdate.lo
> gerror.lo ghash.lo ghook.lo giochannel.lo giounix.lo glist.lo gmain.lo gmem.lo
> gmessages.lo gmutex.lo gnode.lo gprimes.lo grel.lo gscanner.lo gslist.lo
> gstrfuncs.lo gstring.lo gtimer.lo gtree.lo gutils.lo
> rm -fr .libs/libglib.la .libs/libglib.* .libs/libglib-1.2.*
>
> gcc -shared garray.o gcache.o gcompletion.o gdataset.o gdate.o gerror.o
> ghash.o ghook.o giochannel.o giounix.o glist.o gmain.o gmem.o gmessages.o
> gmutex.o gnode.o gprimes.o grel.o gscanner.o gslist.o gstrfuncs.o gstring.o
> gtimer.o gtree.o gutils.o -lc -Wl,-soname -Wl,libglib-1.2.so.1 `test -n
> "sgi1.5:sgi1.4:sgi1.3:sgi1.2:sgi1.1:sgi1.0:sgi1.6" && echo -Wl,-set_version
> -Wl,sgi1.5:sgi1.4:sgi1.3:sgi1.2:sgi1.1:sgi1.0:sgi1.6` -Wl,-update_registry
> -Wl,.libs/so_locations -o .libs/libglib-1.2.so.1.6
>
> ld32: FATAL 12: Expecting n32 objects: garray.o is 64-bit.
> collect2: ld returned 4 exit status
> make[2]: *** [libglib.la] Error 1
> make[2]: Leaving directory `/usr/people/laurent/tmp/glib-1.2.6_64'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/people/laurent/tmp/glib-1.2.6_64'
> make: *** [all-recursive-am] Error 2
>
> does anyone know how I can do this ? ( I would like to keep my versions runing
> on cc AND gcc )
This looks more like a libtool bug to me, contact the libtool maintainers
at libtool@gnu.org. The workaround is to create the library by hand:
copy-n-paste the link line (gcc -shared ...) and add the extra -mabi=64
flag. Another (easier) workaround that *might* work is:
LDFLAGS="-mabi=64 -Wl,-64".
Hope this helps,
Erik
--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands
Phone: +31-15-2785859 Fax: +31-15-2781843 Email J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]