El 2016-08-01, a las 16:01, Jeremy Huddleston Sequoia escribió: > >> On Aug 1, 2016, at 11:55, [ftp83plus] <ges...@ftp83plus.net> wrote: >> >> >> El 2016-08-01, a las 02:49, Ryan Schmidt escribió: >> >>> On Aug 1, 2016, at 00:40, [ftp83plus] wrote: >>>> >>>> El 2016-07-31, a las 16:30, Ryan Schmidt escribió: >>>>> >>>>> Could you also show us the CMakeOutput.log? >>>> >>>> Sure, here it is: >>>> CMakeOutput.log >>>> http://pastebin.com/XZ3WHA0F >>> >>> This again shows: >>> >>> ld: warning: ignoring file /usr/lib/libc++.dylib, file was built for >>> unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 >>> 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked >>> (i386): /usr/lib/libc++.dylib >>> >>> libcxx needs to be installed with the universal variant prior to this step. >>> I still think it would be a good idea if we made the libcxx port install >>> with the universal variant automatically since not having it installed >>> universal will cause problems like these. >>> >> @Jeremy: >> >> So should Bootstrapping 2, Step 2, after: >> sudo port -v install libcxx >> have an additional step with: >> sudo port -v -s upgrade --enforce-variants libcxx +universal > > No, because it's the default variant right now. It won't be an issue for > future users like it was for you. You just need to manually do that now.
This is a bit unclear: should Bootstrapping 2, step 2 read sudo port -v install libcxx +universal? I did that previously, and it failed to recompile python. The bug is marked as a "New defect", and has no solution AFAIK Thanks, _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
