Re: not specifically MacPorts but tools-related
On Sat, 2007-11-24 at 02:18 -0600, Ryan Schmidt wrote: > On Nov 22, 2007, at 23:30, paul beard wrote: > > > On 11/22/07, Ryan Schmidt wrote: > > > >> I assume the only practical difference between MacPorts gcc_select > >> and Apple gcc_select is that Apple gcc_select only lets you select > >> Apple-installed compilers, while MacPorts lets you (additionally?) > >> select MacPorts-installed compilers. > > > > Apparently, that's the case. Any idea how you add/remove compilers > > from it's list? In either the Apple-supplied one or the MacPorts > > version? > > Based on "man gcc_select" (with the gcc_select port not installed), I > assume it's not possible to modify the list of compilers it can > select. If it had been possible, I assume MacPorts would just > piggyback on Apple's gcc_select instead of reinventing the wheel. > > Configuration of the MacPorts gcc_select seems to be possible (though > I have not tried it myself). Read "man gcc_select" (with the > gcc_select port installed). > You can of course also directly use the various gcc compilers for your programs by calling `gcc-mp-4.2 foo.c -o foo' (etc.); gcc_select is for getting `gcc foo.c -o foo' to work "just like that" for a preselected compiler, like if you always want to build your sources with gcc 4.1 from macports. The MacPorts' gcc_select really is beta and requires some work; it _should_ not interfere with any port build but probably will do with some. So it is not intended for getting ports to build with a different version of gcc -- a goal that would probably require quite some effort. Regards, -Markus -- Dipl. Inf. (FH) Markus Weissmann http://www.mweissmann.de/ http://www.macports.org/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: not specifically MacPorts but tools-related
On Nov 22, 2007, at 23:30, paul beard wrote: On 11/22/07, Ryan Schmidt wrote: I assume the only practical difference between MacPorts gcc_select and Apple gcc_select is that Apple gcc_select only lets you select Apple-installed compilers, while MacPorts lets you (additionally?) select MacPorts-installed compilers. Apparently, that's the case. Any idea how you add/remove compilers from it's list? In either the Apple-supplied one or the MacPorts version? Based on "man gcc_select" (with the gcc_select port not installed), I assume it's not possible to modify the list of compilers it can select. If it had been possible, I assume MacPorts would just piggyback on Apple's gcc_select instead of reinventing the wheel. Configuration of the MacPorts gcc_select seems to be possible (though I have not tried it myself). Read "man gcc_select" (with the gcc_select port installed). ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: not specifically MacPorts but tools-related
On 11/22/07, Ryan Schmidt <[EMAIL PROTECTED]> wrote: > > > On Nov 22, 2007, at 16:11, paul beard wrote: > > > On 11/22/07, Ryan Schmidt wrote: > > > >> gcc_select should probably "never" be used. The system ships with a > >> default compiler (gcc 3.3 on Panther, gcc 4.0 on Tiger and Leopard) > >> and that should probably "never" be changed. Software that needs a > >> different compiler should specify that explicitly. > >> > >> Users who had used gcc_select to select a different compiler used to > >> experience all sorts of weird breakage with some MacPorts software. > >> Recently (1.5.2?), MacPorts was changed so that it doesn't matter > >> what the user has selected with gcc_select; MacPorts will use gcc 3.3 > >> on Panther and 4.0 on Tiger and Leopard unless the portfile specifies > >> something different using configure.compiler. This is a good thing. > >> > >> Apple's gcc 3.3 only builds PowerPC binaries, so it's not suitable > >> for use on Intel Macs. > > > > Is the gcc_select in MacPorts any better? > > > > gcc_select @0.1sysutils/gcc_select > > > > gcc_select 0.1, sysutils/gcc_select (Variants: universal, darwin_7, > > darwin_8_ppc, darwin_8_i386) > > http://svn.macports.org/repository/macports/users/mww/select/ > > > > gcc_select lets you switch the default compiler. It symlinks the > > standard compiler executables in the MacPorts prefix to the > > selected version. > > I assume the only practical difference between MacPorts gcc_select > and Apple gcc_select is that Apple gcc_select only lets you select > Apple-installed compilers, while MacPorts lets you (additionally?) > select MacPorts-installed compilers. > > Apparently, that's the case. Any idea how you add/remove compilers from it's list? In either the Apple-supplied one or the MacPorts version? -- Paul Beard / www.paulbeard.org/ <[EMAIL PROTECTED]/[EMAIL PROTECTED]> ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: not specifically MacPorts but tools-related
On Nov 22, 2007, at 16:11, paul beard wrote: On 11/22/07, Ryan Schmidt wrote: gcc_select should probably "never" be used. The system ships with a default compiler (gcc 3.3 on Panther, gcc 4.0 on Tiger and Leopard) and that should probably "never" be changed. Software that needs a different compiler should specify that explicitly. Users who had used gcc_select to select a different compiler used to experience all sorts of weird breakage with some MacPorts software. Recently (1.5.2?), MacPorts was changed so that it doesn't matter what the user has selected with gcc_select; MacPorts will use gcc 3.3 on Panther and 4.0 on Tiger and Leopard unless the portfile specifies something different using configure.compiler. This is a good thing. Apple's gcc 3.3 only builds PowerPC binaries, so it's not suitable for use on Intel Macs. Is the gcc_select in MacPorts any better? gcc_select @0.1sysutils/gcc_select gcc_select 0.1, sysutils/gcc_select (Variants: universal, darwin_7, darwin_8_ppc, darwin_8_i386) http://svn.macports.org/repository/macports/users/mww/select/ gcc_select lets you switch the default compiler. It symlinks the standard compiler executables in the MacPorts prefix to the selected version. I assume the only practical difference between MacPorts gcc_select and Apple gcc_select is that Apple gcc_select only lets you select Apple-installed compilers, while MacPorts lets you (additionally?) select MacPorts-installed compilers. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: not specifically MacPorts but tools-related
On 11/22/07, Ryan Schmidt <[EMAIL PROTECTED]> wrote: > > > gcc_select should probably "never" be used. The system ships with a > default compiler (gcc 3.3 on Panther, gcc 4.0 on Tiger and Leopard) > and that should probably "never" be changed. Software that needs a > different compiler should specify that explicitly. > > Users who had used gcc_select to select a different compiler used to > experience all sorts of weird breakage with some MacPorts software. > Recently (1.5.2?), MacPorts was changed so that it doesn't matter > what the user has selected with gcc_select; MacPorts will use gcc 3.3 > on Panther and 4.0 on Tiger and Leopard unless the portfile specifies > something different using configure.compiler. This is a good thing. > > Apple's gcc 3.3 only builds PowerPC binaries, so it's not suitable > for use on Intel Macs. Is the gcc_select in MacPorts any better? gcc_select @0.1sysutils/gcc_select gcc_select 0.1, sysutils/gcc_select (Variants: universal, darwin_7, darwin_8_ppc, darwin_8_i386) http://svn.macports.org/repository/macports/users/mww/select/ gcc_select lets you switch the default compiler. It symlinks the standard compiler executables in the MacPorts prefix to the selected version. -- Paul Beard / www.paulbeard.org/ <[EMAIL PROTECTED]/[EMAIL PROTECTED]> ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: not specifically MacPorts but tools-related
On Nov 22, 2007, at 14:43, paul beard wrote: Does anyone have any experience with the gcc 3.3-fast compiler? it's listed as an option on my system but gcc_select says it doesn't really exist. And how do I use the compilers that MacPorts builds, if I ever had a need? gcc33 @3.3.6 lang/gcc33 gcc34 @3.4.6 lang/gcc34 gcc40 @ 4.0.4 lang/gcc40 gcc41 @4.1.2 lang/gcc41 gcc42 @4.2.2 lang/gcc42 gcc43 @4.3-20071116 lang/gcc43 And does gcc_select override what's in the Portfile? For instance, python 2.5 is balking with gcc 4 (the default) but builds with gcc 3.3. I made the change explicit in the Portfile. Could I have saved that step? gcc_select should probably "never" be used. The system ships with a default compiler (gcc 3.3 on Panther, gcc 4.0 on Tiger and Leopard) and that should probably "never" be changed. Software that needs a different compiler should specify that explicitly. Users who had used gcc_select to select a different compiler used to experience all sorts of weird breakage with some MacPorts software. Recently (1.5.2?), MacPorts was changed so that it doesn't matter what the user has selected with gcc_select; MacPorts will use gcc 3.3 on Panther and 4.0 on Tiger and Leopard unless the portfile specifies something different using configure.compiler. This is a good thing. Apple's gcc 3.3 only builds PowerPC binaries, so it's not suitable for use on Intel Macs. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: not specifically MacPorts but tools-related
On 11/22/07, paul beard <[EMAIL PROTECTED]> wrote: > > Does anyone have any experience with the gcc 3.3-fast compiler? it's > listed as an option on my system but gcc_select says it doesn't really > exist. And how do I use the compilers that MacPorts builds, if I ever had a > need? > > gcc33 @3.3.6 lang/gcc33 > gcc34 @3.4.6 lang/gcc34 > gcc40 @ 4.0.4 lang/gcc40 > gcc41 @4.1.2 lang/gcc41 > gcc42 @4.2.2 lang/gcc42 > gcc43 @4.3-20071116 lang/gcc43 > > > And does gcc_select override what's in the Portfile? For instance, python > 2.5 is balking with gcc 4 (the default) but builds with gcc 3.3. I made > the change explicit in the Portfile. Could I have saved that step? > Well, I answered one of my own questions: gcc_select has no effect on the value in a portfile, or to put it another way, you can override it with the portfile's values. So that's python 2.5 sorted. What changed upstream, I wonder? -- Paul Beard / www.paulbeard.org/ <[EMAIL PROTECTED]/[EMAIL PROTECTED]> ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
