building CURRENT on netbsd-3-0-RELEASE failed

On Wed, Jun 07, 2006 at 02:27:20PM +0200, Quentin Garnier
wrote:
> You really want to drop that flag from CFLAGS, CXXFLAGS
and COPTS, and
> put it in CPUFLAGS instead.  That way it will only be
used when it is
> actually relevant.

Interesting.  Is this documented somewhere?  

	Geert

On Wed, Jun 07, 2006 at 02:48:10PM +0200, Geert Hendrickx
wrote:
> On Wed, Jun 07, 2006 at 02:27:20PM +0200, Quentin
Garnier wrote:
> > You really want to drop that flag from CFLAGS,
CXXFLAGS and COPTS, and
> > put it in CPUFLAGS instead.  That way it will only
be used when it is
> > actually relevant.
> 
> Interesting.  Is this documented somewhere?  

Indirectly in bsd.README...  Yes, it clearly lacks
documentation.  Also,
the fact that setting CFLAGS and CXXFLAGS in mk.conf is
dangerous should
be better documented.

-- 
Quentin Garnier - cubecubidou.net - cubeNetBSD.org
"When I find the controls, I'll go where I like,
I'll know where I want
to be, but maybe for now I'll stay right here on a silent
sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

On Wed, Jun 07, 2006 at 02:48:10PM +0200, Geert Hendrickx
wrote:
> On Wed, Jun 07, 2006 at 02:27:20PM +0200, Quentin
Garnier wrote:
> > You really want to drop that flag from CFLAGS,
CXXFLAGS and COPTS,
> > and put it in CPUFLAGS instead.  That way it will
only be used when
> > it is actually relevant.
> 
> Interesting.  Is this documented somewhere?  

mk.conf(5):

SEE ALSO
     make(1), packages(7), /usr/share/mk/bsd.README


/usr/share/mk/bsd.README:

CPUFLAGS        Additional flags to the compiler/assembler
to select
                CPU instruction set options, CPU tuning
options, etc.


regards,

-- 
-- Lubomir Sedlacik <salo{NetBSD,Xtrmntr,silcnet}.org>   --