[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Migrating to autoconf 2.52g
From: |
Tim Van Holder |
Subject: |
Re: Migrating to autoconf 2.52g |
Date: |
04 Feb 2002 15:38:11 +0100 |
On Mon, 2002-02-04 at 15:24, John Poltorak wrote:
> On Mon, Feb 04, 2002 at 01:32:34PM +0100, Tim Van Holder wrote:
> > On Mon, 2002-02-04 at 12:28, John Poltorak wrote:
>
> > > When running autoupdate I get:-
> > >
> > > + autoupdate
> > > autom4te.: no such file or directory: /dev/null
> > > autoupdate.: cannot close autom4te ...
> >
> > I would guess that whatever OS/2 environment you use (EMX I guess) does
> > not provide emulation for /dev/null (or at least bash and/or perl
> > don't). Perhaps autoconf needs to detect this:
> >
> > DEVNULL=/dev/null
> > test -f /dev/null || { test -f NUL && DEVNULL=NUL }
> >
> > or something similar.
>
>
> Can you suggest what I could patch? I'd really like to see if autoupdate
> can provide what I want.
It may be as simple as globally replacing /dev/null with NUL in the
autom4te script. But I can't be sure that is the only problem
preventing autoupdate from working.
- Migrating to autoconf 2.52g, John Poltorak, 2002/02/04
- Re: Migrating to autoconf 2.52g, Tim Van Holder, 2002/02/04
- Re: Migrating to autoconf 2.52g, John Poltorak, 2002/02/04
- Re: Migrating to autoconf 2.52g, Paul Eggert, 2002/02/04
- Re: Migrating to autoconf 2.52g, John Poltorak, 2002/02/04
- Re: Migrating to autoconf 2.52g, Akim Demaille, 2002/02/05
- Re: Migrating to autoconf 2.52g, John Poltorak, 2002/02/05
- Re: Migrating to autoconf 2.52g, Tim Van Holder, 2002/02/05
- Re: Migrating to autoconf 2.52g, Akim Demaille, 2002/02/05