Mail Archives: djgpp/2002/05/19/09:56:04
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/ ]
- Raw text -