This is the mail archive of the
mailing list for the GCC project.
Re: Your mingw32 patch...
- To: Dan Egnor <egnor at ofb dot net>, mingw-users at sourceforge dot net
- Subject: Re: Your mingw32 patch...
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Fri, 05 Jan 2001 16:30:49 -0500
- CC: gcc at gcc dot gnu dot org
- References: <20010105125334.N17919@ofb.net>
- Reply-To: mingw-users at sourceforge dot net, gcc at gcc dot gnu dot org
Now why would you send this to me personally? Use the list, please.
Dan Egnor wrote:
> It looks like "gcc-2.95.2-mingw-2.95.3-prerelease-1.diff" is a patch
> from the 2.95.2 stock distribution (from gcc.gnu.org) to a version which
> includes both the mingw patches and the 2.95.3-prerelease-1 patches,
> *except* that there's some confusion about the INSTALL directory.
> Notably, to get the patch to install cleanly, I had to first
> mv INSTALL INSTALL.old
> mv install INSTALL
> Oddly, the files which are patched make all sorts of references to the
> "install" directory.
Good, find. This is actually a portability bug in the GCC-2.95.2
release. The archive has an INSTALL directory with a README file in
it. It also later has an install directory whose contents end up on our
Windows systems in INSTALL since on Win32 filesystems INSTALL == install
== Install == ...
Since you're applying the patch on UNIX, you actually get both
directories with the original contents. Someone needs to create a fix
for this and submit the patches to GCC maintainers. The easiest fix is
to move the location of README, but due to GNU standards the fix will
probably involve renaming install.
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com