Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Jan 1999 20:25:37 +0200 (SAT)
From:      John Hay <jhay@mikom.csir.co.za>
To:        ache@nagual.pp.ru (Andrey A. Chernov)
Cc:        mark@grondar.za, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject:   Re: cvs commit: src/gnu/usr.bin/perl/libperl config.SH-aout.i386 config.SH-elf.alpha config.SH-elf.i386
Message-ID:  <199901171825.UAA25667@zibbi.mikom.csir.co.za>
In-Reply-To: <19990117195413.A30023@nagual.pp.ru> from "Andrey A. Chernov" at "Jan 17, 99 07:54:14 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
> On Sun, Jan 17, 1999 at 06:01:11PM +0200, Mark Murray wrote:
> > "Andrey A. Chernov" wrote:
> > > > In some folks' "make world", during the build of dynaloader, stdio.h was
> > > > not found. *Boom*
> > > 
> > > Can't even imagine how adding "-O -pipe" can affect finding stdio.h. It
> > 
> > Aaah! You didn't add -O -pipe, you defined the previously undefined
> > CFLAGS to be ${<something>}. _That_ is what broke things.
> > 
> > Remember that there are _two_ uses for config-*; one when it is executed
> > as a real shell script, and the other when it is parsed by Perl. When it
> > is parsed by perl, the macro substitution breaks.
> 
> Well, for 
> optimize="${CFLAGS}"
> shell script produce
> optimize=""
> which is right and MakeMaker produce
> OPTIMIZE= ${CFLAGS}
> which is right too.
> Maybe I overlook something?

Well I don't have the whole answer to this thing, but I have a machine
that did a "make world" successfully but failed a "make release". My
/etc/make.conf have "CFLAGS= -O2 -pipe" but I don't do anything
special for "make release", because that is the snaps that end up on
internat. (The script that is run in the chroot environment to do
everything during the "make release" do a "export CFLAGS='-O -pipe'".)

It looks like during my "make world" the gnu/usr.bin/perl/perl/Makefile
didn't pick up the -nostdinc that is being set in src/Makefile.inc1, but
it was picked up during the "make release", but the -I${DESTDIR}/usr/include
that is added to CFLAGS in bsd.prog.mk isn't picked up, so it does not
know where to find the normal include files.

Exactly why I don't know. Perhaps the fact that bsd.prog.mk is included
halfway in the gnu/usr.bin/perl/perl/Makefile may have something to
do with it???

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901171825.UAA25667>