Date: Fri, 4 Jun 2010 23:58:58 +0200 From: Alexander Best <alexbestms@uni-muenster.de> To: Doug Barton <dougb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: 'buildworld' not always pulling in /etc/src.conf Message-ID: <AANLkTil7QxbEj5g7agCXvzahJ-goUHWx2Jq4y6WD6R6r@mail.gmail.com> In-Reply-To: <4C093E01.7020909@FreeBSD.org> References: <AANLkTikA4QPoT0e540nCSc0_LAAycIjAOQOGLB-e2BjY@mail.gmail.com> <op.vdojtep843o42p@klevas> <AANLkTilsDmdbqIELw3SkSlOZQ-WzlLjg1bgs2-WhSAQf@mail.gmail.com> <4C093E01.7020909@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Fri, Jun 4, 2010 at 7:55 PM, Doug Barton <dougb@freebsd.org> wrote: > On 06/04/10 10:46, Alexander Best wrote: >> >> src.conf should ALWAYS take priority over make.conf when >> buildworld or buildkernel is being run. > > Defining the same variables in different contexts is always a recipe for the > dreaded "unpredictable results." Even if it were possible to create the > proper rules to enforce what you're asking for allowing users to rely on it > would just be encouraging bad habits. i just found out that src.conf should only contain WITHOUT_* and maybe DEBUG_FLAGS = -g. what i did was to remove all CC, CXX and CPP definitions from make.conf and defined them in src.conf. this however broke buildworld. :( simply add CC=gcc CXX=g++ CPP=cpp to src.conf and bamm! 'buildworld' should fail somewhere in lib/csu (that's ony amd64). so putting compiler related stuff into src.conf isn't such a great idea. > > > Doug > > -- > > ... and that's just a little bit of history repeating. > -- Propellerheads > > Improve the effectiveness of your Internet presence with > a domain name makeover! http://SupersetSolutions.com/ > > -- Alexander Besthome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTil7QxbEj5g7agCXvzahJ-goUHWx2Jq4y6WD6R6r>