On Aug 9, 2013, at 13:17, Daniel J. Luke <[email protected]> wrote:

> On Aug 9, 2013, at 4:12 PM, Ryan Schmidt <[email protected]> wrote:
>> On Aug 9, 2013, at 15:06, "Brian D. McGrew" <[email protected]> wrote:
>>> Well I had to port install gcc48 to build gcc-4.8.1 from source.  Using
>>> /usrŠgcc didn't get me there.  So installing port gcc48, building
>>> gcc-4.8.1 from source in ~ and installing over the top of port installed
>>> gcc worked (backing up /opt/local of course).  Circular for sure, but
>>> effective.
>> 
>> And completely impossible to implement in that fashion in MacPorts. A port 
>> cannot depend on itself.
> 
> not impossible, just impractical (I think we've had other ports that need 
> themselves to bootstrap).

Yes, see apple-gcc42 on Tiger as an example (the +bootstrap variant).  
apple-gcc42 is needed to build dependencies of apple-gcc42 on Tiger.

We really shouldn't be doing that unless there is no other way.


Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to