libgcc update ... to 4.9?

["René J.V. Bertin"]

On Aug 21, 2014, at 00:37, Ryan Schmidt wrote:

> 
> On Aug 20, 2014, at 4:05 AM, René J.V. Bertin wrote:
> 
>> In fact, is there a way to get those installed manually, should `port` not pick them up for whatever reason? For ports that take as long to build as gcc or libgcc, replacing the build time with a bit of terminal exercise is still an immense gain of time.
> 
> There are several reasons why MacPorts would not attempt to download a binary:
> 
> * your prefix is not /opt/local
> * your applications_dir is not /Applications/MacPorts
> * your frameworks_dir is not /opt/local/Library/Frameworks
> * the port prohibits the use of binaries
> * you've edited macports.conf and requested source builds only
> 
> There may be other conditions I'm forgetting.
> 

I think my macports.conf file fulfils those conditions, but just in case you forgot something, I've attached it. It still contains the commented-out lines from when I had it point to the actual install location, and it has the sandbox disabled as at some time that  was required to avoid issues with /opt/local being a symlink. Otherwise, the only thing that maybe isn't "stock" is the macports user but that shouldn't influence the decision to install from available binary packages, I guess. Or I should never benefit from those, and yet, fortunately, I do.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: macports.conf
Type: application/octet-stream
Size: 6394 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20140821/03da8574/attachment.obj>
-------------- next part --------------