Date: Wed, 29 Jul 2009 10:48:04 -0400 From: Eric Damien <jafa82@gmail.com> To: ports@freebsd.org Subject: Re: "ghost" ports CFLAGS Message-ID: <4d4ab19d0907290748q5493eb92g6bad8d081388441@mail.gmail.com> In-Reply-To: <441vo0g6tt.fsf@be-well.ilk.org> References: <4A6EED3A.7030101@gmail.com> <441vo0g6tt.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, I just edited the /etc/make.conf. About the clean build directories, I
performed make clean (even if portmaster is already supposed to do so,
unless instructed otherwise); I even deleted the ports tree and made a fresh
portsnap fetch extract: no use.
Not to stay stuck, I decied to include a ports.conf in make.conf just to
switch back to the other compiler (actually gcc43/g++43), on those
problematic ports. But then again, that is a temporary solution.
Do you think there may be another path to explore ?
Thanks,
Eric Damien.
On Tue, Jul 28, 2009 at 11:34 AM, Lowell Gilbert <
freebsd-ports-local@be-well.ilk.org> wrote:
> Eric Damien <jafa82@gmail.com> writes:
>
> > I edited my /etc/make.conf in order to change the default compiler via
> > the CC and CXX variables. I also happened to edit the CFLAGS value,
> > all of this changes enclosed within a conditional check on the
> > directory, of the form:
> > .if ${CURDIR:M*/ports*}
> > CFLAGS= -mtune=amdfam10 -msse4e
> > .endif
> > I made a general config using postmaster.
> > After some trouble with some ports, I decided to get rid of those
> > modifications and commented the above form.
> > But, I was surprised to see that some ports still present this value
> > of CFLAGS at building time.
> > How can I correct this mistake.
>
> Just a guess; you built them previously and didn't clean the build
> directories?
>
> Or maybe you put those options in a portmaster config file?
> [ /usr/local/etc/portmaster.rc or $HOME/.portmasterrc ...]
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4d4ab19d0907290748q5493eb92g6bad8d081388441>