Mail Archives: djgpp/2002/05/19/01:15:09
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Allegro and Cygwin issue.
|
From: | Neo 1061 <invalid AT erehwon DOT invalid>
|
Organization: | Geeks Anonymous
|
Message-ID: | <Xns9213A8B1B97neo1061hotmailcom@216.254.136.26>
|
User-Agent: | Xnews/5.04.25
|
Lines: | 15
|
Date: | Sun, 19 May 2002 05:01:14 GMT
|
NNTP-Posting-Host: | 216.254.209.164
|
X-Complaints-To: | news AT primus DOT ca
|
X-Trace: | news.tor.primus.ca 1021784474 216.254.209.164 (Sun, 19 May 2002 01:01:14 EDT)
|
NNTP-Posting-Date: | Sun, 19 May 2002 01:01:14 EDT
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
Don't bother. I managed to fix it.
I dumped the environment in bash, no MINGDIR=; then I had a closer look at
those export commands in the profile file, where I'd pasted the two new
ones after two pre-existing ones. I moved the new ones to the beginning of
the list, when I noticed that the last old one contained tons of strange
escapes and so did the line after the export lines, and guessed that maybe
that line ended with some code to continue onto the next line. In which
case it would be "eating" one or both new export lines.
I restarted bash and ran make, and it seems to be compiling away merrily
now.
Maybe the Allegro documentation should point out this rather subtle
"gotcha"...
- Raw text -