Re: GCC upgrade
Mark wrote:
> One question, though:
>
> ..if ${.CURDIR:M*/ports/*} && !${.CURDIR:M*/work/*}
>
> Why would you NOT want to use the new gcc when in a /work/ directory?
> (where ports builds).
>
> Thanks,
>
> - Mark
This is because these settings are processed in the ports framework and
overwriting whatever became of them in the process by applying them to make
calls from the working directory might break something.
By the way (inserting shameless advertisement), if you find the make syntax
clumsy for configuring ports and portsconf too restrictive, you might want to
have a look at buildflags from the sysutils/bsdadminscripts ports. It offers a
more compact syntax (that actually will be parsed into make syntax) and certain
knobs, that make handling several compilers, ccache, distcc and parallel
building '-j' easier.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: GCC upgrade
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Helge Rohde
> Sent: vrijdag 24 november 2006 17:59
> To: freebsd-questions@freebsd.org
> Subject: Re: GCC upgrade
>
>
>
> On Friday 24 November 2006 16:40, Mark wrote:
>
> > > -Original Message-
> > > From: Kris Kennaway [mailto:[EMAIL PROTECTED]
> > > Sent: vrijdag 24 november 2006 17:11
> > > To: Mark
> > > Cc: freebsd-questions@freebsd.org
> > > Subject: Re: GCC upgrade
> > >
> > > > I tested the new gcc, btw (compiled MySQL server with
> > > > it, which takes quite a while). Seems to work fine.
> > > > But I'm not enough of a C expert to know precisely how
> > > > to do a safe upgrade of this kind.
> > >
> > > If you're not an expert then just leave it alone. Replacing
> > > the system compiler might sound like a cool thing to do, but
> > > what will actually happen is that you'll make your FreeBSD
> > > system unbuildable.
> >
> > Guess I hadn't thought about it that way. Good thinking.
> > It's just that 2.95.4 seems so ancient. :)
> >
> > Only reason I wanted to in the first place, is that I've had several
> > ports that wanted a 3.x series gcc (and kept wanting to build one).
> >
> > Thanks,
>
> You could leave the default in place, define a different gcc
> for the ports in /etc/make.conf and then just add to the list of
> excludes every time you run into problems while building a port.
> Thats what i do, and so far roughly 80% of the ports seem quite
> content with gcc4.2.
Thanks, Helge!
Yours is a very elegant solution. :) I really like the idea of still being
able to build my system (as Kris pointed out), and yet do the ports with
the new gcc. I also like the idea of being able to exclude certain ports
(like I would do for certain already compiled things, like
php4-extensions, of which newly added extensions will presumable need the
system compiler again).
One question, though:
..if ${.CURDIR:M*/ports/*} && !${.CURDIR:M*/work/*}
Why would you NOT want to use the new gcc when in a /work/ directory?
(where ports builds).
Thanks,
- Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GCC upgrade
On Friday 24 November 2006 16:40, Mark wrote: > > -Original Message- > > From: Kris Kennaway [mailto:[EMAIL PROTECTED] > > Sent: vrijdag 24 november 2006 17:11 > > To: Mark > > Cc: freebsd-questions@freebsd.org > > Subject: Re: GCC upgrade > > > > > I tested the new gcc, btw (compiled MySQL server with > > > it, which takes quite a while). Seems to work fine. > > > But I'm not enough of a C expert to know precisely how > > > to do a safe upgrade of this kind. > > > > If you're not an expert then just leave it alone. Replacing > > the system compiler might sound like a cool thing to do, but > > what will actually happen is that you'll make your FreeBSD > > system unbuildable. > > Guess I hadn't thought about it that way. Good thinking. > It's just that 2.95.4 seems so ancient. :) > > Only reason I wanted to in the first place, is that I've had several > ports that wanted a 3.x series gcc (and kept wanting to build one). > > Thanks, You could leave the default in place, define a different gcc for the ports in /etc/make.conf and then just add to the list of excludes every time you run into problems while building a port. Thats what i do, and so far roughly 80% of the ports seem quite content with gcc4.2 If that sounds cool to you, checkout this sample make.conf out of some german Howto. You wont need knowledge of german, Its self explaining enough. http://wiki.bsdforen.de/index.php/Make.conf_optimieren#.2Fetc.2Fmake.conf have fun, Helge ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GCC upgrade
On Fri, Nov 24, 2006 at 04:40:23PM +, Mark wrote: > > -Original Message- > > From: Kris Kennaway [mailto:[EMAIL PROTECTED] > > Sent: vrijdag 24 november 2006 17:11 > > To: Mark > > Cc: freebsd-questions@freebsd.org > > Subject: Re: GCC upgrade > > > > > I tested the new gcc, btw (compiled MySQL server with > > > it, which takes quite a while). Seems to work fine. > > > But I'm not enough of a C expert to know precisely how > > > to do a safe upgrade of this kind. > > > > If you're not an expert then just leave it alone. Replacing > > the system compiler might sound like a cool thing to do, but > > what will actually happen is that you'll make your FreeBSD > > system unbuildable. > > Guess I hadn't thought about it that way. Good thinking. > It's just that 2.95.4 seems so ancient. :) > > Only reason I wanted to in the first place, is that I've had several > ports that wanted a 3.x series gcc (and kept wanting to build one). If you're interested in running gcc 3.x, you can just update to a modern version of FreeBSD (e.g. 6.x). You really should consider doing this on general grounds, since the 4.x branch is scheduled for termination in only a few months (January 2007). Kris pgpEFpp9o1UxE.pgp Description: PGP signature
RE: GCC upgrade
> -Original Message- > From: Kris Kennaway [mailto:[EMAIL PROTECTED] > Sent: vrijdag 24 november 2006 17:11 > To: Mark > Cc: freebsd-questions@freebsd.org > Subject: Re: GCC upgrade > > > I tested the new gcc, btw (compiled MySQL server with > > it, which takes quite a while). Seems to work fine. > > But I'm not enough of a C expert to know precisely how > > to do a safe upgrade of this kind. > > If you're not an expert then just leave it alone. Replacing > the system compiler might sound like a cool thing to do, but > what will actually happen is that you'll make your FreeBSD > system unbuildable. Guess I hadn't thought about it that way. Good thinking. It's just that 2.95.4 seems so ancient. :) Only reason I wanted to in the first place, is that I've had several ports that wanted a 3.x series gcc (and kept wanting to build one). Thanks, - Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GCC upgrade
On Fri, Nov 24, 2006 at 08:09:13AM +, Mark wrote:
> Hello,
>
> I'd like tp upgrade my gcc version (from 2.95.4). I have two questions
> about it, though.
>
> 1) What is the best gcc version to upgrade to? I see plenty in the ports,
> from the whole 3.x series to 4.3. And I wonder why they all still remain
> in the ports? So I'm not sure upgrading to 4.3 is the best idea. And even
> when I upgraded to what I thought was the latest gcc (on a Vmware box), it
> said:
>
> "gcc version 4.1.2 20061103 (prerelease)"
>
> Bummer.
>
> 2): To get ports to actually use the new one, I did something like:
>
> asarian-host: {root} % cd /usr/bin
> asarian-host: {root} % rm gcc
> asarian-host: {root} % ln /usr/local/bin/gcc41 gcc
>
> But there's plenty of 'old' gcc stuff still in /usr/bin/.
>
> Will what I did suffice? Or am I missing some sort of procedure to get rid
> of the gcc environment in /usr/bin/? Subsidiarily, will I run into
> conflicts this way? (with old gcc stuff still residing in /usr/bin/).
>
> I tested the new gcc, btw (compiled MySQL server with it, which takes
> quite a while). Seems to work fine. But I'm not enough of a C expert to
> know precisely how to do a safe upgrade of this kind.
If you're not an expert then just leave it alone. Replacing the
system compiler might sound like a cool thing to do, but what will
actually happen is that you'll make your FreeBSD system unbuildable.
Kris
pgpbwvonGnxoj.pgp
Description: PGP signature
GCC upgrade
Hello,
I'd like tp upgrade my gcc version (from 2.95.4). I have two questions
about it, though.
1) What is the best gcc version to upgrade to? I see plenty in the ports,
from the whole 3.x series to 4.3. And I wonder why they all still remain
in the ports? So I'm not sure upgrading to 4.3 is the best idea. And even
when I upgraded to what I thought was the latest gcc (on a Vmware box), it
said:
"gcc version 4.1.2 20061103 (prerelease)"
Bummer.
2): To get ports to actually use the new one, I did something like:
asarian-host: {root} % cd /usr/bin
asarian-host: {root} % rm gcc
asarian-host: {root} % ln /usr/local/bin/gcc41 gcc
But there's plenty of 'old' gcc stuff still in /usr/bin/.
Will what I did suffice? Or am I missing some sort of procedure to get rid
of the gcc environment in /usr/bin/? Subsidiarily, will I run into
conflicts this way? (with old gcc stuff still residing in /usr/bin/).
I tested the new gcc, btw (compiled MySQL server with it, which takes
quite a while). Seems to work fine. But I'm not enough of a C expert to
know precisely how to do a safe upgrade of this kind.
Thanks,
- Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc upgrade
On Wed, Oct 02, 2002 at 06:59:59PM +0200, Tomasz Koziara wrote: > Hi everybody > > I would like to upgrade form gcc-29.5.4 to gcc-33. > Old gcc comes with FreeBSD as "native" compiler > and is not registerd as eny installed package. > Is it reasonable just to type "make all install clean" > in gcc-33 port directiry ? Will I need to upgrade > my c and c++ libs ( or meaby the will be upgraded > as dependencies ? ). Generally - how to do > all that stuff properly - not to cose a gloal mess > in my system ? I have few projects in development > at the time and only a smart chunk of code needs > newer version of GCC. Probably, I could get by > somhow in case - upgradeing would be to > paintfull. Thanks for Your hints. The output of gcc 3.3 for c++ code is not compatible with c++ binaries from older compilers. Therefore you cannot mix-and-match c++ code, but other C code should be ok. You also cannot compile the base system (make world/kernel) with the newer gcc because it won't work (there were changes required to support it in 5.0-CURRENT). Kris msg03758/pgp0.pgp Description: PGP signature
Re: gcc upgrade
they don't overwrite each other. you invoke it as /usr/local/bin/gcc33. -Adam >> (10.02.2002 @ 0959 PST): Tomasz Koziara said, in 0.7K: << > Hi everybody > > I would like to upgrade form gcc-29.5.4 to gcc-33. > Old gcc comes with FreeBSD as "native" compiler > and is not registerd as eny installed package. > Is it reasonable just to type "make all install clean" > in gcc-33 port directiry ? Will I need to upgrade > my c and c++ libs ( or meaby the will be upgraded > as dependencies ? ). Generally - how to do > all that stuff properly - not to cose a gloal mess > in my system ? I have few projects in development > at the time and only a smart chunk of code needs > newer version of GCC. Probably, I could get by > somhow in case - upgradeing would be to > paintfull. Thanks for Your hints. > > Tom > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > >> end of "gcc upgrade" from Tomasz Koziara << -- "Oh good, my dog found the chainsaw." -Lilo, "Lilo & Stitch" Adam Weinberger [EMAIL PROTECTED] http://vectors.cx To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
gcc upgrade
Hi everybody I would like to upgrade form gcc-29.5.4 to gcc-33. Old gcc comes with FreeBSD as "native" compiler and is not registerd as eny installed package. Is it reasonable just to type "make all install clean" in gcc-33 port directiry ? Will I need to upgrade my c and c++ libs ( or meaby the will be upgraded as dependencies ? ). Generally - how to do all that stuff properly - not to cose a gloal mess in my system ? I have few projects in development at the time and only a smart chunk of code needs newer version of GCC. Probably, I could get by somhow in case - upgradeing would be to paintfull. Thanks for Your hints. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
