[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Q] GNUstep Solaris 64 bit compilation
From: |
Vaisburd, Haim |
Subject: |
[Q] GNUstep Solaris 64 bit compilation |
Date: |
Mon, 20 Mar 2006 17:54:36 -0800 |
Hello everybody,
I'm trying to compile GNUstep under Solaris 2.8, 64 bit processor
and I want to make 64-bit system.
I have compiled gcc (4.0.0) myself - it seemed fine, but now
it does not want to link with the libraries for proper architecture.
The configuration command (I removed -I and -L stuff)
CFLAGS="-m64 -mcpu=v9" LDFLAGS="-m64 -mcpu=v9" ./InstallGNUstep
reports
checking whether objc really works... no
because the resulting executable does not specify that
it requires the 64-bit versions of the libraries.
More details look like this.
The following compilation succeeds:
gcc -o conftest -m64 -mcpu=v9 -I<my_prefix> \
-x objective-c -fgnu-runtime -m64 -mcpu=v9 \
-L<my_prefix> config/config.objc.m \
-lffi -lssl -lsocket -lcrypto -liconv -lobjc
but the resulting executable does not know
where to find the libraries:
> ldd conftest
libffi.so.4 => <...>/gcc4gnu/lib/libffi.so.4 - wrong ELF class:
ELFCLASS32
libobjc.so.1 => <...>/gcc4gnu/lib/libobjc.so.1 - wrong ELF class:
ELFCLASS32
libgcc_s.so.1 => <...>/gcc4gnu/lib/libgcc_s.so.1 - wrong ELF class:
ELFCLASS32
[...]
However, I have them all perfectly 64 bits one level down,
in <...>/gcc4gnu/lib/sparcv9 directory.
I can force runtime linker to look there first by unsing LD_LIBRARY_PATH
or with LDFLAGS="-R<path>", but I expected the gcc/gnu ld combination to
select the proper
libraries based on architecture, the same way native Solaris tools do.
What am I missing? What is the right way to configure?
Thank you,
Tima
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Q] GNUstep Solaris 64 bit compilation,
Vaisburd, Haim <=