On Tue, 25 Aug 2009, Szak�ts Viktor wrote:
> No, simply because I didn't know these tools exist.
> It good news they do, and the fix is very simple, the
> condition has to be change from != dos to == win. Well,
> not exactly, because DJGPP build is broken when run from msys.
> You should try because it does it quite strangely
> ("Bad command or filename" + "No command seen." when using
> dj-make). So it rather should be 'HOST_PLAT == win and
> MAKE_PLAT != dos'. Unless you have better idea.
And you still do not want to allow bash.exe from DJGPP to use
as base shell in windows. BTW DJGPP supports nearly full POSIX
environment and DJGPP users quite often use full DJGPP installation.
Not all features are available when you use DJGPP with DOS/Win
shells.
Please remove it at all. If you want you can document that some
combinations of GNU make and MSys was not working in your test
environment but as long as you do not know what is the reason
do not try to block things which can work for other people.
BTW It's highly possible that you have the same problems with as /P64
in TLIB so if you find the reason and solution you will resolve
also this problem.
>>> * config/win/bcc.mk
>>> ! Deleted dbl quotes from tlib commands as it totally confused it
>>> under msys shell.
>>
>> I have not idea if you tested above modification but it has to
>> break POSIX shells builds because non quoted '\' are characters
>> so BCC builds creates now:
>> ..........libwinbcchbcommon.lib
>> instead of:
>> ..\..\..\..\..\lib\win\bcc\hbcommon.lib
>
> I've tested it with msys. It produces quite strange
> results with dbl quotes using msys + mingw32-make:
> ---
> tlib.exe /P64 "..\..\..\..\..\lib\win\bcc\hbcplr.lib" -+complex.obj
> TLIB 4.5 ....
> Warning: unknown command line switch 'm' ignored
> Warning: unknown command line switch '1' ignored
> Warning: 'evl' not found in library
> Warning: 'sys' not found in library
> Warning: '.0' not found in library
> Warning: 'hbcplr' not found in library
> Warning: 'complex' not found in library
> ---
> I've tested further and removing /P64 switch also
> fixes it, although this option is needed. How to
> pass it then?
>
> [ it does show the first warnings everytime you pass
> any "/" prefixed switches, even /?. ]
It's probably side effect of MSYS feature used to translated *nix like
paths to DOS ones.
You can try to disable it but I do not know if it's possible - you should
look at MSys documentation.
Maybe it's possible to disable it selectively using quoting, i.e.
"/P64" or '/P64'.
Or maybe helps moving this switch after library name. You have to try in
real environment.
TLIB does not support '-' as option marker so we cannot use the simplest
solution with -P64.
Anyhow I'm surprised that
tlib.exe /P64 ..\..\..\..\..\lib\win\bcc\hbcplr.lib -+complex.obj
with single backslashes and without quoting was working. It suggest
serious problem with your local MSys copy. AFAIR \ escaping was fully
functional in MSys when I was using it few years ago.
best regards,
Przemek
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
