Problem with gcc4.7 and call_once

Daniel J. Luke dluke at geeklair.net
Fri Aug 9 13:17:36 PDT 2013


On Aug 9, 2013, at 4:12 PM, Ryan Schmidt <ryandesign at macports.org> wrote:
> On Aug 9, 2013, at 15:06, "Brian D. McGrew" <brian at visionpro.com> 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).

If it's the only way to make it work, having the port build itself with the system compiler and use the output to rebuild itself is a possibility.

--
Daniel J. Luke                                                                   
+========================================================+                        
| *---------------- dluke at geeklair.net ----------------* |                          
| *-------------- http://www.geeklair.net -------------* |                          
+========================================================+                        
|   Opinions expressed are mine and do not necessarily   |                          
|          reflect the opinions of my employer.          |                          
+========================================================+





More information about the macports-users mailing list