-
Notifications
You must be signed in to change notification settings - Fork 577
Configure bombs out if it finds wrong-architecture libraries #11691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
From @nwc10Created by @nwc10On this Sparc Linux system, if I try to build 64 bit with this: ./Configure -Dusedevel=y -Dcc=ccache\ gcc -Dld=gcc -Dcf_email='nick@ccl4.org' -Dperladmin='nick@ccl4.org' -Doptimize=-g -Duse64bitall -Dprefix=~/Sandpit/snap5.9.x-$patch -Accflags=-m64 -Aldflags=-m64 -Alddlflags='-m64' [ie adding -m64 to cc, ld and lddl flags], it bombs out in Configure: I used the command: ccache gcc -o try -g -m64 -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -m64 -fstack-protector -L/usr/local/lib try.c -lnsl -ldb -ldl -lm -lcrypt -lutil -lc and I got the following output: /usr/bin/ld: skipping incompatible /usr/lib/gcc/sparc-linux-gnu/4.3.2/../../../libdb.so when searching for -ldb The problem, I think, is that it's *still* searching in /usr/lib etc I *think* that hints/linux.sh isn't perfect either, in that to find the $ /usr/bin/gcc -print-search-dirs | grep libraries | cut -f2- -d= | tr ':' '\n' | grep -v 'gcc' | sed -e 's:/$::' I *think* that we'd be more correct to pass the compiler flags to that gcc $ for file in `/usr/bin/gcc -print-search-dirs | grep libraries | cut -f2- -d= | tr ':' '\n' | grep -v 'gcc' | sed -e 's:/$::'`; do test -e $file && ls -ld $file; done And filtering those for libdb.so ie it would *still* find the 32 bit libdb.so, and then choke on it. The only way I can get Configure to complete is to force the library path In addition, to get the build to complete, I need to manually add -shared I'm not sure what the correct fix for this is. Possibly, Configure's 1: Determine compiler flags which by Configure's standards, is a radical change from what it currently Nicholas Clark Perl Info
|
From @nwc10On Sun, Oct 09, 2011 at 09:17:57AM -0700, Nicholas Clark wrote:
I should add that I think I had the analogous problem on OS X building with But I tried building with -m32 today and I don't have this problem any more. Nicholas Clark * There have only ever been 2 architectures, x86_64 and i386. Honest. |
From @jkeenanOn Sun, 09 Oct 2011 16:17:57 GMT, nicholas wrote: ./Configure gurus: Is this approach, suggested by Nicholas lo these many years ago, worth exploring? Thank you very much. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @arcJames E Keenan via RT <perlbug-followup@perl.org> wrote:
Well, I'd consider it a portability issue rather than specifically a -- |
Is this still something we want to pursue? I'm not sure what the state of Sparc Linux is. |
Migrated from rt.perl.org#100992 (status was 'open')
Searchable as RT100992$
The text was updated successfully, but these errors were encountered: