Mail Archives: djgpp/2000/06/09/17:18:58
On Fri, 09 Jun 2000 20:29:19 GMT, zargon AT hotmail DOT vom (Zargon) ate too
many hallucinogenic mushrooms and wrote:
>I am well aware that beta products can be expected to have bugs or
>quirks. However, I don't consider it unreasonable to expect that betas
>do *not* contain showstopping errors that prevent the thing from even
>being installed... Alphas can be expected to be that unstable, or CVS
>snapshots, with the occasional build not actually building on some
>targets, or not working on certain configurations...
I might add to this that in my past experience, Allegro has been a
paragon of stability and non-show-stopping-ness, until apparently
yesterday. I do find it difficult to believe that they completely
broke it under DJGPP in the latest WIP; it does seem much more likely
the problem is somewhere in the PGCC specific areas, or else in the
documentation. (Perhaps the documentation is omitting something --
maybe there's a configure script to be run, which would fit with the
"make, make install" paradigm after all...)
--
Any sufficiently advanced magic is indistinguishable from
an Allegro-using C++ program compiled with gcc.
- Raw text -