Date: Fri, 4 Jun 2010 19:46:12 +0200 From: Alexander Best <alexbestms@uni-muenster.de> To: freebsd-current@FreeBSD.org Subject: Re: 'buildworld' not always pulling in /etc/src.conf Message-ID: <AANLkTilsDmdbqIELw3SkSlOZQ-WzlLjg1bgs2-WhSAQf@mail.gmail.com> In-Reply-To: <op.vdojtep843o42p@klevas> References: <AANLkTikA4QPoT0e540nCSc0_LAAycIjAOQOGLB-e2BjY@mail.gmail.com> <op.vdojtep843o42p@klevas>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/6/2 Andrius Mork=C5=ABnas <hinokind@gmail.com>: > On Wed, 02 Jun 2010 18:23:19 +0300, Alexander Best > <alexbestms@uni-muenster.de> wrote: >> >> it seems for some reason gcc44 gets chosen at some point as compiler >> instead of the base gcc. i DO have CC, CXX and CPP defined in my >> /etc/make.conf so that gcc44 gets used for ports and other stuff. >> HOWEVER /stc/src.conf also contains those three variables and they to >> the base version of gcc. of course commenting out those variables in >> /etc/make.conf fixes the problem, but if i'm not mistaken 'buildworld' >> should use /etc/src.conf at all times and thus should be aware that i >> want it to use base gcc. > > buildworld uses both, src.conf and make.conf, and whatever is in > make.conf pretty much overrides everything else. You can use something > like this to set compiler only for ports: > > .if !empty(.CURDIR:M/usr/ports/*) > CC=3Dgcc44 > .endif thanks for the info. actually i had something like this in my make.conf beforehand as stated in http://www.freebsd.org/doc/en_US.ISO8859-1/articles/custom-gcc/configuring-= ports-gcc.html i thought i could get rid of it. imo the current behaviour where make.conf takes priority over src.conf during buildworld is not what users expect. src.conf should ALWAYS take priority over make.conf when buildworld or buildkernel is being run. just my 0,02$. ;) cheers. alex > > -- > Andrius > --=20 Alexander Best
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTilsDmdbqIELw3SkSlOZQ-WzlLjg1bgs2-WhSAQf>