Thanks for your response!
I'm sorry I didn't see this earlier -- I get I had problems with my email
Hugh Perkins wrote:
> Well, I've been playing with using an adapted version of cccl, and
> setting CC to cccl and CXX to cccl prior to running configure.
> This way, cccl handles the // escaping for you.
Thanks for mentioning cccl; I wasn't aware of it. Unfortunately, in addition to
the Microsoft compiler, I need to handle Borland and Comeau for Windows, which
also use '/' switches.
> OTOH I cant tell you that this works perfectly since configure crashes
> my computer :-/ but this might be just my own computer/drivers so you
> might want to experiment.
> There's a copy of my current version of cccl, called ccclming, in an
> earlier thread called "forking issue on Windows XP?"
> On 6/6/05, Jonathan Turkanis <technews@...> wrote:
>> I'm trying to execute a makefile designed for use with GNU make and
>> the Microsoft C++ command-line tools. I find that the environment
>> translates some command-line swicthes as if they were file
>> pathnames. For instance, /EHsc becomes C:/Tools/msys/1.0/EHsc. It
>> only happens in some cases; for example, the linker option /OUT:
>> doesn't get translated.
>> I've found I can disable this behavior by changing the makefile to
>> use "//" instead of "/". This is not an acceptable solution,
>> however, since it would render the makefile unusable in other
>> What can I do to disable the translations?