options for forcing use of GCC

[Nilton Jose Rizzo]

Em Mon, 28 Apr 2014 08:23:34 -0600, Ian Lepore escreveu
> On Mon, 2014-04-28 at 22:03 +0800, Julian Elischer wrote:
> > On 4/28/14, 8:05 PM, Ian Lepore wrote:
> > > On Mon, 2014-04-28 at 14:54 +0800, Julian Elischer wrote:
> > >> On 4/28/14, 12:30 AM, Ian Lepore wrote:
> > >>> 	WITH_GCC=yes \
> > >>> 	WITH_GNUCXX=yes \
> > >>> 	WITHOUT_CLANG=yes \
> > >>> 	WITHOUT_CLANG_IS_CC=yes \
> > >> forgot to ask.. is this in /etc/make.conf?
> > >> or elsewhere?
> > > Actually in our build system we build in a chroot, and we inject those
> > > args into the environment during the builds so that we can have
> > > different options for building world versus cross-world within the
> > > chroot, but I think the more-normal place would be make.conf.
> > 
> > we also use a combination of environment and make.conf in a chroot.
> > though people sometimes talk about a src.conf (or is that src.mk?) but 
> > I haven't found that one yet.

  You must be create in /etc the src.conf and put this knobs there.

    In my case I would like to use only clang, but have some
 ports that assume gcc as mandatory.

Rizzo

> > >
> > > -- Ian
> > >
> > >
> > >
> 
> In theory, /etc/make.conf affects all builds you do -- world, kernel,
> ports, your own apps, everything -- whereas /etc/src.conf affects 
> only kernel and world.  I've heard it said that the reality falls 
> short of that and src.conf settings inappropriately leak into ports builds.
> 
> -- Ian
> 
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"


---
/*************************************************
**Nilton José Rizzo            UFRRJ
**http://www.rizzo.eng.br      http://www.ufrrj.br
**http://lattes.cnpq.br/0079460703536198
**************************************************/