From: =?iso-8859-1?Q?G=FCnter_Ladwig?= <gladwig AT iname DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Q: allegro_message
Date: Fri, 9 Jun 2000 21:53:41 +0200
Organization: 1&1 Telekommunikation GmbH
Lines: 56
Message-ID: <8hri2v$kcr$1@news.online.de>
References: <39402637 DOT 409213505 AT news DOT globalserve DOT net> <MPG DOT 13aa45e8bde2587d98bbd9 AT news DOT freeserve DOT net> <39405324 DOT 420716556 AT news DOT globalserve DOT net> <a9q0ksorcmfnk96h3du1fotrpc17oa3ou7 AT 4ax DOT com> <394095cc DOT 436991456 AT news DOT globalserve DOT net> <3940A2B7 DOT 57226F0C AT home DOT com> <3940a2f3 DOT 440359385 AT news DOT globalserve DOT net> <3940FA83 DOT B43AC647 AT home DOT com> <39412ad4 DOT 31251750 AT news DOT globalserve DOT net>
NNTP-Posting-Host: pc19f2a8e.dip0.t-ipconnect.de
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: news.online.de 960580511 20891 193.159.42.142 (9 Jun 2000 19:55:11 GMT)
X-Complaints-To: abuse AT online DOT de
NNTP-Posting-Date: 9 Jun 2000 19:55:11 GMT
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi!

> 1. This would require me to make the dependencies, which would require
>    me to use sed, which would mean booting into Linux to do it, which
>    would mean setting up the gcc over there to cross-compile to DOS.
>    Ouch. No thank you. Allegro should work out of the box, without
>    faffing around, regardless of whether you have previously used an
>    older version.

BTW, the sed exists for DOS as well and installing is only a matter of
unzipping the file in the djgpp directory. And you shouldn't need it anyway,
because Allegro works out of the box. It does so for me and all other
Allegro user on a wide spectrum of configurations.

> 2. Old .o files can't affect anything anyways -- make will see a .o
>    file with a months-old modification time and a source file just
>    created/modified yesterday and say "Hmm, I think this one needs to
>    be updated".

Most of my Allegro files have a modification date of 31/01/2000, certainly
not only a few days old. It is entriely possible that the unzipping over an
old installation affects the new version, in whatever way. And don't say
that it theoretically should be impossible, you don't know everything. Try
it out. You can discuss without an end and the only thing that will stop
this discussion is to actually *try* it. Unzip the file to complete new
directory and try to build Allegro from there.

> 3. The errors I'm seeing also prove it isn't old .o files. An old .o
>    file could only cause problems at *link* time. The errors I saw
>    were *compile* time and included *parse errors* for God's sake.
>    I don't see how a parse error can be caused by any "gotcha"s, only
>    by an actual typo in the sources that were distributed in the zip!
>    I guess it was tested on various targets but not DJGPP, and the
>    error is in a conditionally-compiled section...

Wrong guess, AFAIK the DJGPP version is maintained by Shawn himself and it
is the most stable and the most thoroughly tested part of Allegro. It
compiles fine for me and everybody else. It may be that it was never tested
on your type of configuration, but it can't be possibly tested everywhere.
And so this complaining won't help you, instead look into the source and see
what the reason for the failure was. Or write to the Allegro mailing list.

And you know what? This is the reason why it's called 3.9.32 and not 4.0.
The development till the version 4.0 is nearly complete, but we want to be
sure that the will be no errors in the first release.

ciao

guenter
----
Günter Ladwig
gladwig AT iname DOT com - http://cyberbobby.home.pages.de - ICQ: 14360158
"You know your game is in trouble...when you can look at a Dilbert comic
and not laugh, thinking, 'Been there, done that.'" (C) Steven Woodcock