| Re: [AD] make failing on mkdir |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] make failing on mkdir
- From: Matthew Leverton <meffer@xxxxxxxxxx>
- Date: Sat, 29 Jan 2005 12:34:12 -0600
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=t8P2ZBSFg8vYS20bxZ+DjoJzJDOp8wBd+XVTKqBvH7v6LhnqnV6rnpejSE02yAEY0XL4iz6Y0zvKkkOU68bvRt0vQwZL1ua0EU7mM267EoFTrTo6MVvVHqEAPIietoIOh1PuJUEYtPM1KQzCh3X/WuG5LtlUfxJ9WPmovbwwJb8=
It did indeed work on 3.80. If the solution ends up being to tell
people to upgrade, then it should be made painfully clear to the
person installing Allegro. (The first impression will be "Allegro's
broken.") A lot of people probably just have MinGW's make so that they
can build Allegro for MSVC, so they won't necessarily be keeping it up
to date.
If it is known that you must have 3.80 to build (install) Allegro,
then it would be nice if the make process could detect that and tell
the user.
--
Matthew Leverton
> The current version for MinGW is 3.80 and was released on 2003-06-19. IMHO,
> forcing people to upgrade is an acceptable solution.
>
> --
> Daniel Schlyder
> http://bitblaze.com/