[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.54c can't build and install
From: |
Bernhard Reiter |
Subject: |
Re: 2.54c can't build and install |
Date: |
Fri, 8 Nov 2002 11:03:03 +0100 |
User-agent: |
Mutt/1.3.25i |
On Thu, Nov 07, 2002 at 09:43:52PM +0100, Alexandre Duret-Lutz wrote:
> >>> "Bernhard" == Bernhard Reiter <address@hidden> writes:
>
> Bernhard> I'm trying to build/install a recent autoconf version (2.54c)
> Bernhard> on a machine with an older GNU/Linux installation.
>
> The diagnostics you reported are typically seen on a NFS client
> which isn't synchronized (date-wise) with its NFS server. Is
> that your case? Could you try a local build? (e.g. in /tmp)
I'm building locally,
but you gave me the right hint:
Autoconf only builds properly here
if the modification time is extracted correctly.
I'm usually using the "-m" flag for tar so I can
look at the files and see when I extraced them or which files
I've changed compared to the rest.
This is the first time that a packages did not build
when I used "-m".
So you could analyse that time dependency maybe adding a "touch"
at the right place or added a note to INSTALL. Something like:
"The build autoconf from the tarball you need to extract
the modification time from the archive (e.g. not using the "-m" flag
for tar)."
Thanks,
Bernhard
pgpZjgc8ZLcAo.pgp
Description: PGP signature