My vote is to ignore.
I don't realy like the copy option anyway. By using copy, when you update autoconf,
you do not get the updated copy of these files in the dist. However, the RPM's were
rolling up the links, instead of the files. I consider this a bug in rpm, or we don't
have the spec file options correct.
-----Original Message-----
From: Ralf Corsepius <[EMAIL PROTECTED]>
Date: Sat, 26 Aug 2000 11:50:15 -0400
To: Alexander Mai <[EMAIL PROTECTED]>
Subject: Re: CVSMake & automake
Alexander Mai wrote:
>
> This week I fixed a problem with our CVSMake & related scripts.
> In a very rare attempt to start from a real clean tree as just from CVS
> I noticed that I get
>
> > automake: configure.in: installing `./install-sh'
> > error while copying
> >
> > automake: configure.in: installing `./mkinstalldirs'
> > error while copying
> >
> > automake: configure.in: installing `./missing'
> > error while copying
>
> I can see this as well when just removing those 3 files and manually running
> automake. Despite the message the files are actually copied and in place
> afterwards.
>
> Do we have an expert here who can explain what's wrong here?
>
It's a bug in automake-1.4.
automake --add-missing --copy is broken. This has been fixed in
development versions of automake, but these are far from being ready
for realize.
For now, a work-around is not to use --copy or to ignore the error
message or to manually copy the relevant files to there locations.
Ralf
--
Ralf Corsepius
Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung
(FAW)
Helmholtzstr. 16, 89081 Ulm, Germany Tel: +49/731/501-8690
mailto:[EMAIL PROTECTED] FAX: +49/731/501-999
http://www.faw.uni-ulm.de
