RFC: gcc-4.0 4062

[danchr@…]

I've created two small ports, one for odcctools and one for Apple GCC 4.0. The odcctools port should work pretty much as expected, but the gcc40 port needs more work: It installs into /usr & /Developer and it doesn't support anything but ppc.

Just wanted to put up here to hear what people thought of it :)

[danchr@…]

Portfile for odcctools

[danchr@…]

Portfile for gcc40

[jmpp@…]

Hey Dan, great additions! Three comments though: first, I think it might be better to create seperate bugs for each new port, and maybe mark one as dependent of the other; second, I have serious concerns about anything installing straight into /usr, even more if you're talking about a compiler that's gonna install a bunch o' libraries and crt files that may seriously mess up the system if mixed with what's already there. Anyway around this last issue? Are these ports supposed to replace what the OS brings out of the box? Or is there something I'm not getting straight here? If you're going for replacing then these ports should be *THOROUGHLY* tested out, and I cannot stress that enough! Last but not least, isn't there anyway around fetching from CVS in the GCC 4.0 port? I know it's a port of a devel snapshot, but it'd stll be nice to avoid CVS to create less of a moving target. Can't you create a tarball yourself of a fixed checkout and fetch that? When you feel like updating the port all you'd have to do is update that tarball with a different timestamp. I do that for my aqua/NmapFE port, which is available in source form only through CVS.

Thanks again for these, they seem like great additions!

-jmpp.

[danchr@…]

(In reply to comment #3)

I've morphed this bug into concerning only GCC 4.0, and filed bug #XXX to deal with odcctools. Also, I'll rename it from gcc40 to gcc-4.0, since it's Apple GCC.

I agree with most of your comments, however, it's worth noting that Apple's GCC is built so you can have several versions installed. When activating this port, I saw no conflicts despite the fact that it installed into /usr. Of course, it shouldn't have installed into /usr in to begin with...

Now if only GCC didn't take forever to bootstrap :/

[mww@…]

what will happen if Apple's gcc4 is/gets installed? (e. g. tigger)

[danchr@…]

(In reply to comment #5)

what will happen if Apple's gcc4 is/gets installed? (e. g. tigger)

They should coexist peacefully, since a finished port would install gcc-4.0 into ${prefix}. It seems Apple's build system is capable of this, but I still have some issues remaining to fix.

[danchr@…]

Completed, committed.