[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure
From: |
Albert Chin |
Subject: |
Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure |
Date: |
Fri, 8 Jul 2005 20:06:05 -0500 |
User-agent: |
Mutt/1.5.6i |
On Thu, Jul 07, 2005 at 05:02:26PM -0500, Tim Mooney wrote:
> In regard to: Re: FYI: ksh bug on Tru64 UNIX causes current libtool...:
>
> >* Ralf Wildenhues wrote on Wed, Jul 06, 2005 at 05:08:11AM CEST:
> >>
> >>This is a gentle reminder that this issue with Libtool HEAD/branch-2-0
> >>on Tru64 sh is still unsolved. It'd be nice to get a solution into the
> >>next 2.0 release candidate, should such a solution exist.
> >
> >Stupid question: Does Tru64 sh need `^' quoted? The one Solaris one
> >does. I.e., does
> > echo Xbla | sed 1s,^X,,
> >work there? (Libtool currently does not quote this consistently.)
>
> I haven't seen any responses to this, so I will: it does need it quoted:
>
> 05:00 PM dogbert ~$PS1='$ ' /bin/sh
> $ echo Xbla | sed 1s,^X,,
> X,,: not found
> $ sed: Function 1s, cannot be parsed.
What system is this? Works fine on 4.0D and 5.1.
--
albert chin (address@hidden)