-
Notifications
You must be signed in to change notification settings - Fork 577
-Alddlflags doesn't work (the way it should) on Linux #13000
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 @nwc10If I configure perl to build as 32 bit on a 32/64 bit system: ./Configure -des -Dusedevel -Accflags=-m32 -Aldflags=-m32 -Alddlflags=-m32 the build fails. This is a re-run of make: ./miniperl -Ilib make_ext.pl lib/auto/B/B.so MAKE=make LIBPERL_A=libperl.a LINKTYPE=dynamic The problem is that the -Alddlflags happens at the wrong time relative to case "$lddlflags" in but because -A processing has already happened, lddlflags is already set to ./myconfig for the bust configuration: Summary of my perl5 (revision 5 version 19 subversion 1) configuration: If I run Configure like this, adding -shared: ./Configure -des -Dusedevel -Accflags=-m32 -Aldflags=-m32 -Alddlflags=-m32\ -shared the build is fine (and all tests pass) Nicholas Clark |
From @TuxOn Mon, 27 May 2013 07:00:33 -0700, Nicholas Clark (via RT)
Is this something common to all builds, or gcc specific? I mean gcc is obviously used as loader on these systems, whereas on That also re-raises the question: do we care enough to add -- |
The RT System itself - Status changed from 'new' to 'open' |
This ticket sounds like the same issue as #13676. In both cases, I would bet we can just fail if someone tries to compile 32bit perl on a 64 bit system. My suspicion is that nobody would complain. |
One of my standard testing configurations includes |
Migrated from rt.perl.org#118199 (status was 'open')
Searchable as RT118199$
The text was updated successfully, but these errors were encountered: