Date: Wed, 09 Jan 2002 12:19:35 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Bruce Evans <bde@zeta.org.au>, peter@FreeBSD.org Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Ruslan Ermilov <ru@FreeBSD.org> Subject: Re: cvs commit: src/usr.bin/colldef Makefile Message-ID: <XFMail.020109121935.jhb@FreeBSD.org> In-Reply-To: <20020110003133.X8745-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09-Jan-02 Bruce Evans wrote:
> On Wed, 9 Jan 2002, Ruslan Ermilov wrote:
>
>> On Tue, Jan 08, 2002 at 12:13:23AM -0800, John Baldwin wrote:
>> > jhb 2002/01/08 00:13:23 PST
>> >
>> > Modified files:
>> > usr.bin/colldef Makefile
>> > Log:
>> > Use -I${.OBJDIR} -I${.CURDIR} rather than -I. so that this compiles in a
>> > cross-build environment.
>> >
>> > Revision Changes Path
>> > 1.18 +1 -1 src/usr.bin/colldef/Makefile
>> >
>> Why do we need -I${.CURDIR}? AFAIK, -nostdinc doesn't enforce -I-.
>
> parse.y #includes "common.h", and gcc-3.mumble apparently broke the
> magic that makes it possible for common.h to be found (the generated
> file parse.c contains a #line statement that gives the full path to
> the source file parse.y, and compilers are apparently supposed to use
> this to resolve ""-style includes).
If it builds ok on gcc3.1, then it is ok for this to be backed out and I will
just stick it in the sparc64 tree. Peter, can you test if colldef builds ok
with gcc3.1?
> Bruce
--
John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
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?XFMail.020109121935.jhb>