libgcc update ... to 4.9? (and of binary packages and MacPorts install locations)
Lawrence Velázquez
larryv at macports.org
Wed Aug 20 11:06:50 PDT 2014
On Aug 20, 2014, at 5:02 AM, René J.V. Bertin <rjvbertin at gmail.com> wrote:
>>> Would it at least be possible to provide a binary port for libgcc, to avoid having to build (a large part of) 2 gcc versions?
>>
>> There already are binary archives, at least for Intel 64.
>>
>> http://packages.macports.org/libgcc/
>
> Indeed there are. Mystery then why yesterday's upgrade process insisted on installing the port from source (including gcc 4.8.3).
>
> Is it possible that with the latest selfupdate, changes were included to the sandboxing mechanism that further interfere with the possibility/transparence of having /opt/local be a symlink to MacPort's true location?
I'm not sure. You'd have to ask Cal.
I don't suppose you set +universal in variants.conf, or anything like that? What do you see if you run `sudo port -d archivefetch gcc48`? I've attached my log for reference.
vq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcc48_archivefetch.log
Type: application/octet-stream
Size: 1875 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20140820/f4858ed4/attachment.obj>
More information about the macports-users
mailing list