This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Allow build to specify what sed mkheaders uses

From: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
To: Bruce Korb <bkorb at gnu dot org>
Cc: Steve Ellcey <sje at cup dot hp dot com>, Paolo Bonzini <bonzini at gnu dot org>, gcc-patches at gcc dot gnu dot org
Date: Wed, 26 Aug 2009 19:56:17 +0200
Subject: Re: [patch] Allow build to specify what sed mkheaders uses
References: <200908252242.n7PMguY13055@lucas.cup.hp.com> <4A94EE84.6050309@gnu.org> <668c430c0908260754hbca92fcp6ff9132afe38dcbf@mail.gmail.com>

Hi Bruce,

* Bruce Korb wrote on Wed, Aug 26, 2009 at 04:54:13PM CEST:
> fixincludes needs a POSIX sed.

If you allow me a naive question: would it be possible to lift that
restriction?  IOW, do you know which non-portable POSIX functionality it
is relying on?

If input lines aren't too long and the sed script isn't either, then so
far I haven't seen sed scripts that weren't convertible to portable
ones; but I realize I'm leaning quite far out the window right now, and
pretty ignorant about fixinclude history.

> BSD
> Linux
> Solaris
> OS/X
> HP/UX if you like, too. ;)

I have access to those to test.  :-)

Thanks,
Ralf

Follow-Ups:
- Re: [patch] Allow build to specify what sed mkheaders uses
  - From: NightStrike
- Re: [patch] Allow build to specify what sed mkheaders uses
  - From: Bruce Korb

References:
- [patch] Allow build to specify what sed mkheaders uses
  - From: Steve Ellcey
- Re: [patch] Allow build to specify what sed mkheaders uses
  - From: Paolo Bonzini
- Re: [patch] Allow build to specify what sed mkheaders uses
  - From: Bruce Korb

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]