Closed
Bug 81083
Opened 25 years ago
Closed 25 years ago
rebuilding mozilla often fails with compile errors
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
People
(Reporter: rainerm, Assigned: cls)
Details
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.4 i686)
BuildID: 20010516
If I do a full-clean checkout from CVS and then build then everything is fine.
If I then do a rebuild a few days later (to get the latest changes) via 'make -f
client.mk', then the build usually fails with some compilation error.
I just looked through the build instructions and this is shown as the proper way
to rebuild. Is there a better way. I don't want to delete everything and
checkout everything every time. Also note that 'make -f client.mk clean' didn't
help.
Reproducible: Always
Steps to Reproduce:
1. checkout and build mozilla via 'make -f client.mk'
2. wait a few days or so
3. rebuild mozilla via 'make -f client.mk'
Actual Results: After lots of checkouts and building...
make[4]: Entering directory
`/opt/home/rmager/devel/External/mozilla/rdf/chrome/src'
nsChromeRegistry.cpp
c++ -o nsChromeRegistry.o -c -DOSTYPE=\"Linux2.4\" -DOSARCH=\"Linux\" -DOJI
-I../../../dist/include -I../../../
dist/include -I/opt/home/rmager/devel/External/mozilla/dist/include/nspr
-I/usr/X11R6/include -fPIC -I/us
r/X11R6/include -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith
-Wbad-function-cast -Wcast-align -Wo
verloaded-virtual -Wsynth -pedantic -Wno-long-long -pipe -pthread -O2 -DNDEBUG
-DTRIMMED -I/usr/X11R6/include -D
MOZILLA_CLIENT -include ../../../config-defs.h -Wp,-MD,.deps/nsChromeRegistry.pp
nsChromeRegistry.cpp
nsChromeRegistry.cpp: In function `PRBool DatasourceEnumerator(nsHashKey *, void
*, void *)':
nsChromeRegistry.cpp:269: warning: unused variable `nsresult rv'
nsChromeRegistry.cpp: In method `nsresult
nsChromeRegistry::CheckThemeVersion(const PRUnichar *, PRBool *)':
nsChromeRegistry.cpp:3263: `CheckProviderVersion' undeclared (first use this
function)
nsChromeRegistry.cpp:3263: (Each undeclared identifier is reported only once
nsChromeRegistry.cpp:3263: for each function it appears in.)
nsChromeRegistry.cpp:3264: warning: control reaches end of non-void function
`nsChromeRegistry::CheckThemeVersion
(const PRUnichar *, PRBool *)'
nsChromeRegistry.cpp: In method `nsresult
nsChromeRegistry::CheckLocaleVersion(const PRUnichar *, PRBool *)':
nsChromeRegistry.cpp:3272: warning: control reaches end of non-void function
`nsChromeRegistry::CheckLocaleVersio
n(const PRUnichar *, PRBool *)'
nsChromeRegistry.cpp: At top level:
nsChromeRegistry.cpp:3279: no `nsresult
nsChromeRegistry::CheckProviderVersion(const nsCString &, const PRUnichar
*, nsIRDFResource *, PRBool *)' member function declared in class
`nsChromeRegistry'
make[4]: *** [nsChromeRegistry.o] Error 1
make[4]: Leaving directory
`/opt/home/rmager/devel/External/mozilla/rdf/chrome/src'
make[3]: *** [install] Error 2
make[3]: Leaving directory `/opt/home/rmager/devel/External/mozilla/rdf/chrome'
make[2]: *** [install] Error 2
make[2]: Leaving directory `/opt/home/rmager/devel/External/mozilla/rdf'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/opt/home/rmager/devel/External/mozilla'
make: *** [build] Error 2
Expected Results: built happily
The compile error isn't always the same, day to day.
right now build crashes because of some error in checkins for bug 76512.
It was just backed out again so if you repull it will probably build.
Keep an eye on bonsai and tinderbox to see the current tree status and latest
checkins. If the tree is up in flames, it's not very likely your own build will
complete either.
Those are the dangers of doing a cvs pull from a constantly changing tree.
Unless you consult the tinderbox (
http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey ), there's a pretty
good chance that you could wind up with a potentially broken tree.
Marking this particular problem a dupe of 76512.
*** This bug has been marked as a duplicate of 76512 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•