From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Mysterious problem with bash/fileutils
Date: Sun, 19 May 2002 14:08:10 +0100
Lines: 41
Message-ID: <3CE7A3BA.623A3F0@phekda.freeserve.co.uk>
References: <Xns9213B81B6892neo1061hotmailcom AT 216 DOT 254 DOT 136 DOT 26> <3CE76C81 DOT 5E0943EE AT phekda DOT freeserve DOT co DOT uk> <Xns92133B3E03E93neo1061hotmailcom AT 216 DOT 254 DOT 136 DOT 26>
NNTP-Posting-Host: modem-223.arizona.dialup.pol.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: newsg3.svr.pol.co.uk 1021813771 21227 62.137.54.223 (19 May 2002 13:09:31 GMT)
NNTP-Posting-Date: 19 May 2002 13:09:31 GMT
X-Complaints-To: abuse AT theplanet DOT net
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586)
X-Accept-Language: de,fr
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hello.

Neo 1061 wrote:
[snip]
> Anyway, I did determine part of the problem. At
> some point during "make"..."make install" the /usr/local/incldue
> directory ceased to exist.

Was it definitely there in the first place? Maybe the Allegro Makefile does
not create the include file directory, before trying to copy files into it.

> Then "make install" went to copy allegro.h
> there, thus creating a *file" called /usr/local/include with the contents
> of allegro.h,

That sounds bogus. I believe install should fail, if the target directory does
not exist.

> and then mkdir choked trying to create a subdirectory of a
> file. There are now two problems -- one is how to restore the include
> directory to its former state (reinstalling gcc didn't help), and that
> may need to be referred to Cygwin experts (is there a *newsgroup*?),
> while the other is getting Allegro installed without recreating the
> problem, which means getting help from people knowledgeable about Allegro
> (and no Cygwin mailing list *or* newsgroup is likely to help there).

I suggest you try to recreate the problem, to get a log of what happened. Then
someone on a Cygwin mailing list can help you. From the way you've described
it, it sounds like a bug in the Cygwin port of Fileutils.

Generate a log like so from bash:

    make install >install.log 2>&1

Maybe you can see whether the install log makes sense. I suggest you send this
log to the Allegro & Cygwin mailing lists, so that they can help you.

Regards,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]