On Aug 12, 2013, at 7:22, David Barto <dba...@visionpro.com> wrote: > I saw the bug closed, and I'm not seeing anything in port update. > > Should I?
What bug are you referring to? The bug is still open (http://trac.macports.org/ticket/38814), and I'm going to commit soon. > > David > > On Aug 9, 2013, at 1:24 PM, Jeremy Huddleston Sequoia <jerem...@macports.org> > wrote: > >> We don't really need to continue this thread. I have reproduced the issue >> and think I have a workaround. Feel free to file a ticket and assign it to >> me if you want to continue this thread in a more appropriate venue (mailing >> list chatter gets lost more easily than bug reports). >> >> Thanks, >> Jeremy >> >> On Aug 9, 2013, at 13:12, Ryan Schmidt <ryandes...@macports.org> wrote: >> >>> >>> On Aug 9, 2013, at 15:06, "Brian D. McGrew" <br...@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. >>> >>> If gcc48 does not build correctly except when built with gcc48, then I call >>> that a bug in gcc48 that the developers of gcc need to fix, if they want >>> anybody to be able to use gcc48. >>> >>> /usr/bin/gcc is not a compiler, by the way; it's a symlink to a compiler, >>> and which compiler it's a symlink to varies by Xcode version, so it's more >>> useful to talk about the actual compiler. These days, we usually compile >>> with Xcode's clang. The version of clang varies by Xcode version too… >>> >> >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
