Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3F183642.108FBB3E@phekda.freeserve.co.uk>
Date:	Fri, 18 Jul 2003 19:02:42 +0100
From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: GCC 3.3 & LIBC - build process change (attempt #2)
References:	<000001c34cf2$43516430$0101a8c0 AT acp42g>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Andrew Cottrell wrote:
> 
> > Looks good, apart from:
> >
> [snip]
> > You can use sed's -f option multiple times. Below is with sed 3.0.28:
> [snip]
> 
> > bash-2.04$ echo -e "foo\nbar\nbaz" | sed -f t.sed -f t2.sed
> [snip]
> The attempt 2 line was :-
> 
> + XNOPGGPP = $(CROSS_GCC) $(shell sed -f $(TOP)/../noprofpp.sed
> $(TOP)/../gcc.opt) -I. -I- -isystem $(TOP)/../../include $(CFLAGS)
> 
> How about the following line?
> XNOPGGPP = $(CROSS_GCC) $(shell sed -f $(TOP)/../noprof.sed -f
> $(TOP)/../gpp_opt.sed $(TOP)/../gcc.opt) -I. -I- -isystem
> $(TOP)/../../include $(CFLAGS)
> 
> If I do this then no separate C++ profiling sed file is required. Is this
> better?

Since you've generated gpp.opt, why not use it? How about:

XNOPGGPP = $(CROSS_GCC) $(shell sed -f $(TOP)/../noprof.sed $(TOP)/../gpp.opt)
-I. -I- -isystem $(TOP)/../../include $(CFLAGS)

Incidentally, what causes gpp.opt to be built? Does the default rule built it?
I couldn't see anything in the patch, to force it to be built.

> If it is okay then I can change the gpp_opt.sed to gpp.sed and
> produce an attempt #3. Third time lucky???
[snip]

Yes, I predict it will be. ;)

Thanks, bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -