Re: [Mingw-msys] Re: [Mingw-users] Paths question.

[Richard Frith-M. <ri...@br...>]

On Tuesday, March 12, 2002, at 12:03 PM, Earnie Boyd wrote:
>> To be honest, I can't actually think of a good way to handle this
>> problem.
>> It looks like configure scripts really need to be carefully hacked to
>> make
>> sure that values substituted into makefile templates are things like
>> -Ic:/msys/1.0/include rather than -I/usr/include
>>
>
> Uh, MSYS does change the /usr/include to c:/msys/1.0/include.  I just
> checked.

I just tried it with gmake ... and that works ... must be that my 
problems
here are being caused by mingw make ... and it just looked like an msys 
problem.

>> It would be good if msys included a path translation utility to make 
>> that
>> easier (though I've just used sed in a shell script to do it).
>>
>
> That's MSYS's job, if it's not happening then it's broken.  BTW, are
> your include files in /usr/include or in /mingw/include?  By default
> there isn't a /usr/include or a /usr/lib.

Sorry ... they were just invented paths for illustration of what seemed 
to be
happening ... in fact I was using headers in a totally separate path.


>> The mingw make program reads the makefile, and attempts to install
>> software
>
> This may be the problem.  Try instead `gmake MAKE=gmake install'.  In
> the next version typing make will get you the MSYS version of make while
> typing make.exe will get you the mingw version of make from the MSYS
> shell.  I wasn't positive which make should be used when I first
> conceptualized MSYS so I named the MSYS version of make `gmake' so that
> you could have a choice.  You can accomplish this now by doing `cp
> /bin/gmake.exe /bin/make'.

Yes thanks ... that seems to solve most of my problems at the moment.


>> Is it actually possible to compile gcc-3.1 under mingw/msys?
>>
>
> I've built gcc-2.95.3 with mingw and msys, so yes it should be possible
> to build gcc-3.1.

Thanks ... I'll try again using gmake.