Anyway, I will now try Dmitrys instruction step by step.
Unfortunately this didn't work either. I followed
this instruction (but I added any set statement from my mozenv.cmd which wasn't used with export), but at the configure step I got the following error:
configure:3754: checking whether the C compiler (gcc.exe -Zomf ) works
configure:3770: gcc.exe -o conftest.exe -Zomf -idirafter D:/usr/include/os2tk45 conftest.c -lmmap -lcx -lkai -Zomf 1>&5
emxomf: No such file or directory
emxomfld: a.out to omf conversion failed for 'D:\usr\bin\..\lib\gcc\i386-pc-os2-emx\4.9.2\..\..\..\mmap.a'.
configure: failed program was:
#line 3765 "configure"
#include "confdefs.h"
main(){return(0);}
configure: error: installation or configuration problem: C compiler cannot create executables.
I started again working with Dave's way to build, now I added
export 'CPPFLAGS=-idirafter D:/usr/include/os2tk45'
to D:\usr\locale\share\config.site and
SET CPPFLAGS=-idirafter D:/usr/include/os2tk45
to mozenv.cmd. One of both has to do the trick. And it did
.
But then I got another error:
296:24.16 ../../gfx/ots/src/Unified_cpp_gfx_ots_src0.obj
296:24.18 ../../gfx/ots/src/Unified_cpp_gfx_ots_src1.obj
296:24.20 ../../modules/brotli/Unified_c_modules_brotli0.obj
296:24.23 StaticXULComponentsEnd/StaticXULComponentsEnd.obj
296:24.25
296:24.27 weakld: cannot open library file 'D:\TOOLKIT\SOM\LIB\intl_s.a'.
296:24.29 emxomfld: weak prelinker failed. (rc=8)
296:24.30 make.EXE[4]: *** [xul.dll] Error 1
296:24.32 make.EXE[3]: *** [toolkit/library/target] Error 2
296:24.34 make.EXE[2]: *** [compile] Error 2
296:24.36 make.EXE[1]: *** [default] Error 2
296:24.38 make.EXE: *** [build] Error 2
296:24.44 14 compiler warnings present.
That drives me crazy
What is that "intl_s.a"? And why should it be in "D:\TOOLKIT\SOM\LIB\"? It's nowhere on my hard drive, in no RPM package and googling it I found some makefiles utilising it, but no hint where to get it from. It seems to be related to emx but that's all I found out. I will attach a full dump (set>envset.log) of all environment settings which were set while building, maybe that is of any help.
May I annoy you with another question: When building was interrupted by an error and I fixed it, do I always have to delete obj-sm or may I just start
python mozilla/mach -l build_mach_sm.log build
and it will proceed were it stopped?