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
Broken build of perl5.24.0-RC5 on Mac OS X (10.7) #15309
Comments
From mojca@macports.orgDear Developers, Today I started playing with 5.24.0-RC5 for a future inclusion into Undefined symbols for architecture x86_64: I tested on 64-bit Mac OS X 10.7, but I assume the same problem should Configure arguments and the complete build log are available at I will try to build again in a clean environment outside of MacPorts Mojca |
The RT System itself - Status changed from 'new' to 'open' |
From @jhiOn Sat May 07 03:56:11 2016, mojca@macports.org wrote:
FWIW: in El Capitan, using your env and Configure invocation from the macports build log, the RC5 [1] builds fine (well, one problem, see [2]), certainly gets past linking the miniperl and perl, and starts building the extensions. [1] bleadperl as of http://perl5.git.perl.org/perl.git/commit/4f8325bacaec9fddb2bc901248c77835e53720ed [2] The one problem, unrelated to not-building as such, I think: it seems that macports strips the -DPERL_DARWIN flag. The flag really is needed for at least Time::HiRes as it is in the RC5. If it is not there, the OS X emulation of clock_gettime() etc. is not picked up, and the T::H compilation fails. Whether that's the right flag to be needing is another discussion, but it certainly needed now. |
From @jhiOn Sat May 07 06:12:25 2016, jhi wrote:
Hmm, something still is definitely broken in El Capitan with your build setup. Everything builds, and "make minitest" passes, but "make test" doesn't fare that well: ... I'm suspecting the versioning change 53d1d41 is relevant. For the environ failure for you (which I am not seeing in 10.11) see e396210. |
From @craigberryOn Sat, May 7, 2016 at 8:12 AM, Jarkko Hietaniemi via RT
Actually the lack of -DPERL_DARWIN will cause a problem in |
From mojca.miklavec.lists@gmail.comMy emails don't show up here for some reason, but it seems that I found the culprit. MacPorts doesn't strip any -DPERL_DARWIN away. The problem is that it adds -Dccflags="$CFLAGS" and that seems to overwrite any ccflags that are added by Perl's Configure script and needed for a successful compilation. I was told that I should use -Accflags instead of -Dccflags and after removing -Dccflags the compilation succeeds. The tests still fail (https://rt-archive.perl.org/perl5/Ticket/Display.html?id=128095), but that's a different issue altogether. This particular issue seems to be resolved after removing -Dccflags. (I'm not sure whether this is a bug or a feature though. More like you consider this a feature given that an alternative flag exists?) |
From mojca@macports.orgOn 7 May 2016 at 15:12, Jarkko Hietaniemi via RT wrote:
MacPorts doesn't strip -DPERL_DARWIN or at least I didn't find any What it does though is running Configure with -Dccflags="$CFLAGS" and Thank you, |
From mojca@macports.org
Can you please try to build Perl with -Dccflags=""? I'm curious Commit e396210 seems to be fixing Thank you, |
From @tonycozOn Sun May 08 19:31:00 2016, mojca@macports.org wrote:
https://trac.macports.org/ticket/51330 is closed - can this ticket be closed? Tony |
From mojca.miklavec.lists@gmail.comDne Pon 16 Maj 2016 18:05:23 je tonyc napisal:
I closed it after finding the "workaround" and switched to -Accflags rather than -Dccflags. Perl 5.22 still worked with -Dccflags and it seems that it properly added -DPERL_DARWIN even if I used -Dccflags. Then again other perl users/developers told me that one should not use -Dccflags at all, so I'm not sure if you consider this to be a bug or a misuse of flags. I would say that it would probably be nice to get it working either way and I'm willing to dig a bit deeper for that (perhaps do some bi-section on history), but ultimately it should be you giving us the directions and the final decision. If you want me to dig a bit further, let me know. |
From @tonycozOn Tue, 17 May 2016 02:49:06 -0700, mojca.miklavec.lists@gmail.com wrote:
I tried a Configure: ./Configure -des -Dusedevel -Dccflags='-mmacosx-version-min=10.12 -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -DPERL_USE_SAFE_PUTENV' but the resulting config didn't have -DPERL_DARWIN: pallas:perl tony$ grep '^ccflags=' config.sh
-D reapplies it's values are hints have been processed, so hints are effectively ignored for that value. If you supply -Dccflags that aren't enough to build perl correctly, then -Accflags is lot safer and less likely to interfere with perl's configuration/hints processing, but an inappropriate option can still break the build. Tony |
@tonycoz - Status changed from 'open' to 'stalled' |
@tonycoz - Status changed from 'stalled' to 'rejected' |
Migrated from rt.perl.org#128093 (status was 'rejected')
Searchable as RT128093$
The text was updated successfully, but these errors were encountered: