Re: [Mingw-users] Q

[Bo Y. <tec...@gm...>]

Jonathan Wilson :
> Just to follow up on this, I have managed to get it to attempt a build.
> I have all the components required for the Mozilla build installed.
> I have a .bat file that looks like this:
> PATH=c:\mozilla-build\moztools\bin;c:\mozilla-build\python25;c:\mozilla-build\info-zip;c:\msys\1.0\bin;c:\mingw\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\WINDOWS\system32\WBEM
> set HOME=c:\home
> set GCC=yes
> set GXX=yes
> set CC=gcc
> set CXX=g++
> set CPP=cpp
> set LD=ld
> set AS=as
> set MOZ_TOOLS=c:\mozilla-build\moztools
>
> my .mozconfig looks like this
> #
> # See http://www.mozilla.org/build/ for build instructions.
> #
>
> # Options for client.mk.
> mk_add_options MOZ_CO_PROJECT=suite
> mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-@CONFIG_GUESS@
> mk_add_options MOZ_MAKE_FLAGS=-j4
>
> # Options for 'configure' (same as command-line options).
> ac_add_options --with-windows-version=501
> ac_add_options --enable-application=suite
> ac_add_options --disable-accessibility
> ac_add_options --disable-installer
>
> Then I run the batch file and then build SeaMonkey with make -f client.mk build
> I end up hitting the following error:
> /c/mingw/bin/windres -O coff --use-temp-file -DMOZILLA_CLIENT=1 -DNDEBUG=1 
> -DXP_PC=1 -DWIN32=1 -DWIN95=1 -D_PR_GLOBAL_THREADS_ONLY=1 -D_X86_=1 
> -DHAVE_STRERROR=1 -DFORCE_PR_LOG -D_NSPR_BUILD_ --include-dir 
> c:/mozilla/obj-i686-pc-mingw32/dist/include/nspr --include-dir 
> /c/mozilla/nsprpub/pr/include --include-dir 
> /c/mozilla/nsprpub/pr/include/private -o nspr.res 
> /c/mozilla/nsprpub/pr/src/nspr.rc
> c:/mozilla/nsprpub/pr/src/nspr.rc:38:20: error: prinit.h: No such file or 
> directory
> c:\mingw\bin\windres.exe: c:\mingw\bin\gcc exited with status 1
>
> Any ideas? Windres bug? Mozilla build system bug? Something I did wrong on 
> my end?
>   
Ah, I can figure out what is the problem behind the scene depending on 
what you give. Where did you get your source? Is that a complete some 
tree? I think the most valuable way to find the problem is to look up 
for prinit.h. To see whether it is really lost. And then you can go 
further for other possibilities.
Thanks!
Bo