> On 14 Mar 2016, at 12:49 am, [ftp83plus] <[email protected]> wrote: > > I thought I done that with : > >> sudo port clean ld64-136 >> and >> sudo port clean libcxx >> >> as ld54-136 failed to compile as a dependency of libcxx. Received: >> >> Error: Failed to install ld64-136 >> Please see the log file for port ld64-136 for details: >> >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_ld64/ld64-136/main.log >> Error: The following dependencies were not installed: clang-3.4 ld64 >> ld64-136 libcxxab > > > After correcting these lines in the macports.conf file following Ryan's > advice: > > # Whether MacPorts should automatically run rev-upgrade after upgrading > # ports. > #revupgrade_autorun yes > > # Whether rev-upgrade should automatically rebuild ports with broken > # linking or merely report the breakage. Supported values are "report" > # and "rebuild". > revupgrade_mode report > > The last line originally read: > #revupgrade_mode rebuild > > ld64-136 build log is there: http://pastebin.com/rJ95ZwK9 > libcxx build log is there: http://pastebin.com/7DZGYGCV > Both logs were updated at the same time, so I posted them both. > > I don't see the "Skipping complete" anymore in the logs as Ryan said, but the > first error reads: > :info:build src/ld/parsers/lto_file.cpp:36:25: error: unordered_set: No such > file or directory > > Could it be that some important file is missing or wasn't fetched properly?
Unordered_set is only available in C++11, which the ancient gcc 4.2 compiler being used will not support... > > > >> El 2016-03-13, a las 16:11, Chris Jones escribió: >> >> >> >>> On 13 Mar 2016, at 7:02 pm, [ftp83plus] <[email protected]> wrote: >>> >>> Ok, thanks for specifying. >>> >>> Why does it fail, now? >> >> Because you have not changed anything... You are simply explicitly >> specifying some options identical to the defaults... You need to follow the >> advice Ryan has already given you... >> >>> >>>> El 2016-03-13, a las 12:30, Brandon Allbery escribió: >>>> >>>>> On Sun, Mar 13, 2016 at 5:18 AM, [ftp83plus] <[email protected]> wrote: >>>>> Now it's getting even more confusing for me: why would a commented out >>>>> line still be run? >>>> >>>> The comment is showing you what the default action is if you don't say >>>> anything. >>>> >>>> -- >>>> brandon s allbery kf8nh sine nomine >>>> associates >>>> [email protected] >>>> [email protected] >>>> unix, openafs, kerberos, infrastructure, xmonad >>>> http://sinenomine.net >>> >>> _______________________________________________ >>> macports-users mailing list >>> [email protected] >>> https://lists.macosforge.org/mailman/listinfo/macports-users >
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
