Closed Bug 251535 Opened 20 years ago Closed 19 years ago

could not compile firefox on debian woody

Categories

(Firefox Build System :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: ml, Assigned: bryner)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040630 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040630 Firefox/0.9.1

At university we use debian woody for the machines an I want to install a
firefox. Since the prebuild version doesn't start because of a segfault I tried
to compile it on myself. This works with firefox-0.8, but with the newer
Versions no chance. :(
It complains in nsTextFormatter.cpp about undefined va_copy. This could be fixed
by changing it  to __va_copy in the earlier define.
But then the errors continue on another place:

nsRDFContentSink.cpp:150: warning: ISO C++ forbids declaration of `typeof' with
   no type
nsRDFContentSink.cpp:150: typedef `typeof' is initialized (use __typeof__
   instead)
nsRDFContentSink.cpp:150: syntax error before `;' token
nsRDFContentSink.cpp:156: syntax error before `;' token
nsRDFContentSink.cpp:210: 'nsContainerTestFn' is used as a type, but is not
   defined as a type.
nsRDFContentSink.cpp:211: 'nsMakeContainerFn' is used as a type, but is not
   defined as a type.
nsRDFContentSink.cpp: In member function `virtual nsresult
   nsIRDFContainerUtils::RDFContentSinkImpl::FlushPendingNotifications()':
nsRDFContentSink.cpp:175: syntax error before `;' token
[...]
nsRDFContentSink.cpp:744: confused by earlier errors, bailing out
gmake[4]: *** [nsRDFContentSink.o] Error 1


Reproducible: Always
Steps to Reproduce:
1.try to compile firefox > 0.8 on debian woody
2../configure options doesnt change this...
3.

Actual Results:  
see above

Expected Results:  
should compile correctly
using build and patch from
http://www.backports.org/debian/dists/stable/mozilla-firefox/source
the build works with:
dpkg-buildpackage -rfakeroot
make install
in the unpacked mozilla-firefox_0.9.1.orig.tar.gz dir.

Leaving as unconfirmed waiting for developer statement.
correction:

it compiles, but there are several gdk-warnings and when I try to edit the
preferences of a extension, the firefox crashes.

*** This bug has been marked as a duplicate of 248506 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → UNCONFIRMED
Depends on: 203137
Resolution: DUPLICATE → ---
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago19 years ago
Resolution: --- → EXPIRED
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in before you can comment on or make changes to this bug.