Maurilio:
>David,
>with my latest changes I can build harbour on OS/2 using GCC and make
>(even make -j n works).
You skipped many messages :-)
I started my tests on July 27 and posted a lot of info about behaviour
of make and build processes, including comparative historical info
You can review messages with subject:
"Harbour under OS/2 - eCS"
After some fixes, as summary we have:
- Harbour does not build with make376
- Harbour build with make381 - gcc335 (as in your case)
- Harbour does not build with make381 - watcom 1.8 - original watcom.cf
- Harbour build with make381 - watcom 1.8 - two changes of Przemek in
watcom.cf, without them it fail
- Harbour cross build os2->win work with make381 and adding workarounds
in config\ win \watcom.cf for make381 problems
- Harbour cross build win->os2 work with mingw32-make and deleting
workarounds in conf\ os2 \watcom.cf for make381 problems
mingw32-make does not support some instructions existing in workarounds
for os2-make381
In case of "Harbour build with make381 - watcom 1.8 - two changes of
Przemek in watcom.cf" it show many warnings. Przemek explained it happen
in gcc too but are ignored
To clean these warnings we added other workarounds which are not working
as expected. We are in this point of tests
As explained in previous message, if you try OpenWatcom 1.8 in OS/2 and
Windows you certainly will find same problems
The center of problem is behaviour of os2-make381 in different scenarios
and we are trying to solve all of them
We should not discard OS/2 platform and/or cross build
I have checked many versions of os2-make381
Today I found another one and problems are the same
Can you send me your make.exe/files to check with them ?
I am stopped to test Harbour with gcc346, gcc404, gcc432, gcc433, gcc44
due we rely on current make.exe(381) versions which are doing an
uncertain work
David Macias
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
