Greeting-
I have not been able to get an X11 OSX build to work for firefox.
I always get the same error that indicates missing files in the source
tree. I am doing this with the most current tarball of the sources.
-------------------------cut here--------------------------------------
: ../../dist/bin/components/libnecko2.dylib
+++ making chrome /Users/wynkoop/src/www/mozilla/netwerk/resources =>
../../dist/bin/chrome/comm.jar+++ updating chrome
../../dist/bin/chrome/installed-chrome.txt+++
content,install,url,jar:resource:/chrome/comm.jar!/content/necko/+++
overriding content/necko/contents.rdf updating:
content/necko/contents.rdf (stored 0%)+++ making chrome
/Users/wynkoop/src/www/mozilla/netwerk/resources =>
../../dist/bin/chrome/en-US.jar error: file
'../../toolkit/locales/en-US/chrome/necko/contents.rdf' doesn't exist at
../../config/make-jars.pl line 418. gmake[3]: *** [libs] Error 2
gmake[2]: *** [libs] Error 2
gmake[1]: *** [tier_9] Error 2
gmake: *** [default] Error 2
ibook:~/src/www/mozilla:
------------------------------cut here----------------------------------
Any ideas? I did a ./configure --with-x to force X11 instead of aqua.
-Brett

Signature
DRM is theft! We are the stakeholders! http://www.nyfairuse.org/
Brett Wynkoop - 02 Mar 2005 07:35 GMT
Greeting-
I forgot to mention this is on 10.3.8 with the Apple devtools
installed as well as the BSD package from the CDroms.
-Brett

Signature
DRM is theft! We are the stakeholders! http://www.nyfairuse.org/
Peter Dunkel - 17 Mar 2005 10:10 GMT
Brett Wynkoop schrieb:
> Greeting-
> I forgot to mention this is on 10.3.8 with the Apple devtools
> installed as well as the BSD package from the CDroms.
Hello Brett
take a look to fink (the projekt, that ports many Linux-Apps to MacOSX),
there was a bug in xtools, Apple correct it in November.
Peter
Christian Biesinger - 20 Mar 2005 15:06 GMT
> ../../dist/bin/chrome/en-US.jar error: file
> '../../toolkit/locales/en-US/chrome/necko/contents.rdf' doesn't exist at
You didn't set up your mozconfig correctly. See previous questions on
this error in npm.builds.