-
Notifications
You must be signed in to change notification settings - Fork 577
Configure should use the ccflags and ldflags when probing for libraries. #13676
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 @nwc10Configure should use the ccflags and ldflags when probing for libraries. Right now it doesn't. So on this current Ubuntu x86_64 machine I can build But if I use ./Configure -Dusedevel -des -Accflags=-m32 -Aldflags=-m32 -Alddlflags=-shared\ -m32 then configure aborts like this: Checking your choice of C compiler and flags for coherency... #include <stdio.h> I used the command: cc -o try -O2 -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -m32 -fstack-protector -L/usr/local/lib -m32 try.c -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lc -lgdbm_compat and I got the following output: /usr/bin/ld: cannot find -lgdbm You have a BIG problem. Shall I abort Configure [y] because the library probe returned these results: Checking for optional libraries... which are 64 bit libraries, and not all have a 32 bit version available. IIRC this isn't just a Linux problem. It's also a pain on Solaris, and I think Nicholas Clark |
From @jkeenanOn Wed Mar 19 01:36:53 2014, nicholas wrote:
I tried this command (Linux Ubuntu 13.10), but Configure bombed out even more quickly for me than it did for you. Attaching Configure output and perl -V output. Jim Keenan |
From @jkeenanSummary of my perl5 (revision 5 version 18 subversion 2) configuration: Characteristics of this binary (from libperl): |
The RT System itself - Status changed from 'new' to 'open' |
From @TuxOn Sun, 18 May 2014 15:14:26 -0700, "James E Keenan via RT"
I have mentioned this before, and then there was no reply at all at On Wed, 28 Sep 2011 19:30:49 +0200, "H.Merijn Brand" <h.m.brand@xs4all.nl> wrote:
FWIW, this was also in a reply to a question Nicholas asked I think that the current state will not support a full 32bit build: we -- |
@Tux Perhaps we should just abort with a more clear message on 64 bit systems when you try -m32 and call this not supported? |
@Tux, This was proposed for early 5.33. Any status? |
Sorry, no updates (yet). Severe lack of free time dedicatable to issues like these. |
Migrated from rt.perl.org#121469 (status was 'open')
Searchable as RT121469$
The text was updated successfully, but these errors were encountered: