This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: mingw32 subtle build failure
- From: Christopher Faylor <me at cgf dot cx>
- To: GCC Development <gcc at gcc dot gnu dot org>, dannysmith at users dot sourceforge dot net, FX Coudert <fxcoudert at gmail dot com>, Ranjit Mathew <rmathew at gmail dot com>
- Date: Thu, 1 Jun 2006 11:07:30 -0400
- Subject: Re: mingw32 subtle build failure
- References: <7B5C671C-F4EA-4672-98A6-FD2E1A32AFB0@gmail.com> <D5EDB49A-1B53-40C8-9ABD-64D1DF3A2B5D@gmail.com> <20060531230756.GA8659@trixie.casa.cgf.cx> <447E890F.2020006@gmail.com>
On Thu, Jun 01, 2006 at 11:58:31AM +0530, Ranjit Mathew wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Christopher Faylor wrote:
>> On Wed, May 31, 2006 at 11:37:51PM +0200, FX Coudert wrote:
>>> And I forgot to ask: who the heck is supposed to set USE_MINGW_MSYS?
>>> (grep is soooooo sloooooow on my win32 machine)
>>
>> For the record, I don't do Msys. Please don't cc me about msys problems.
>
>I think he CC-ed you on the message because you seem to be
>the one who added the conditional code using USE_MINGW_MSYS
>to libiberty/pex-win32.c:
>
> http://gcc.gnu.org/ml/gcc-cvs/2005-09/msg00557.html
Fair enough. The USE_MINGW_MSYS conditional is for people who want to
make an Msys aware version of the pex* functions. I included it because
when I volunteered to work on these function, I thought that it was a
requirement, so I reluctantly added features to deal with Msys. Then I
was told that it wasn't necessary. So, rather than nuke my changes, I
added a conditional. It's likely to have bit-rotted by now.
Again, I request that you all not cc me on this thread any further.
cgf