Mail Archives: djgpp/2000/06/09/17:57:15
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
- Raw text -