Closed Bug 266270 Opened 20 years ago Closed 20 years ago

Firefox 1.0PR fails to build

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
blocker

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: o.flebbe, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040915
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040915

Firefox 1.0PR fails to build on suse 9.0 with 



It fails while building a jar archive because somehow a contents.rdf is missing
(see below).

Reproducible: Always
Steps to Reproduce:
compile firefox 1.0PR

We do essentially a (mozilla itself builds fine with this, but we check it)

./configure --prefix=/usr/local/ --enable-strip --enable-mathml --disable-debug
--disable-tests --enable-optimize --enable-crypto --disable-pedantic
--with-system-zlib --with-system-jpeg

make
Actual Results:  
Compile stop with the following error:

.....

/scr/furud/bogy2/firefox-1.0PR/ARENA/config/nsinstall -R -m 755 libnecko2.so
../../dist/bin/components
../../dist/bin/elf-dynstr-gc ../../dist/bin/components/libnecko2.so
Couldn't GC any strings, exiting.
gmake[3]: Leaving directory
`/net/furud/fs1/scr/furud/bogy2/firefox-1.0PR/ARENA/netwerk/build2'
gmake[3]: Entering directory
`/net/furud/fs1/scr/furud/bogy2/firefox-1.0PR/ARENA/netwerk/resources'
+++ making chrome
/net/furud/fs1/scr/furud/bogy2/firefox-1.0PR/ARENA/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%)
error: file '../../toolkit/locales/en-US/chrome/necko/contents.rdf' doesn't
exist at ../../config/make-jars.plq line 418.
+++ making chrome
/net/furud/fs1/scr/furud/bogy2/firefox-1.0PR/ARENA/netwerk/resources  =>
../../dist/bin/chrome/en-US.jar
gmake[3]: *** [libs] Error 2
gmake[3]: Leaving directory
`/net/furud/fs1/scr/furud/bogy2/firefox-1.0PR/ARENA/netwerk/resources'
gmake[2]: *** [libs] Error 2
gmake[2]: Leaving directory
`/net/furud/fs1/scr/furud/bogy2/firefox-1.0PR/ARENA/netwerk'
gmake[1]: *** [tier_9] Error 2
gmake[1]: Leaving directory `/net/furud/fs1/scr/furud/bogy2/firefox-1.0PR/ARENA'
gmake: *** [default] Error 2


Expected Results:  
dist/bin/chrome/comm.jar contains content/necko/contents.rdf , but there is no
../../toolkit/locales/en-US/chrome/necko/contents.rdf file as expected by
make-jars.pl.

How does that ever work for you?
Bugday 23 nov 2004

As 1.0 is out, is this should be closed as WONTFIX ?
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → UNCONFIRMED
Resolution: WONTFIX → ---
I suggest marking this WORKSFORME and let someone reopen if it happens for
FireFox 1.1.
As mentioned, elsewhere, the same thing happens with Firefox 1.0.1 source.

I suggest that you ask for help at forums
<http://forums.mozillazine.org/viewforum.php?f=42> instead of claiming that the
source is broken. Hundreds of people have built mozilla successfully (including
myself).

There may be a bug in build config, but then you need to come with detailed
description of the problem, not "That didn't work for me".

Marking WFM. If the same problem appears with 1.1, reopen, but do some research
and provide more details about the problem. And ask in forums first.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → WORKSFORME
> Hundreds of people have built mozilla successfully (including myself).

Millions of people fly on planes, but when they crash, the NTSB and others want 
to know why. 

> There may be a bug in build config, but then you need to come with detailed
> description of the problem, not "That didn't work for me".

I'm not sure to whom you were referring, but I repeated the original configure 
with 1.0.1 source and got the identical message. If you also want to know that 
it is GCC 3.4.3 and glibc 2.3.4 and make 3.80, fine. But this particular error 
appears to be related to either the distro, a link which is not built or a file 
which is not copied.

BTW, the GNOME build of firefox worked fine.

> Marking WFM. 

See above.

> If the same problem appears with 1.1, reopen, but do some research
> and provide more details about the problem. And ask in forums first.

Again, if you are speaking to me, I research this thoroughly, for a couple of 
days before adding my experiences with 1.0.1. I haven't tried 1.1 yet.
Sean, I wasn't talking to you, it was the "How does that ever work for you?"
phrase that got me. I shouldn't have posted that comment. Feel free to reopen if
it still doesn't work with more current sources. See also bug 271562.
(In reply to comment #6)
> Sean, I wasn't talking to you, it was the "How does that ever work for you?"
> phrase that got me. I shouldn't have posted that comment. Feel free to reopen if
> it still doesn't work with more current sources. See also bug 271562.

Sorry, I am not a native speaker. It was not meant to be offensive.

I should have written: "How is it supposed to work?".

I will try current sources, but it is not high on my priorities.

You need to log in before you can comment on or make changes to this bug.