Closed Bug 252942 Opened 16 years ago Closed 15 years ago

Bad Makefile generated upon a custom configuration of Firefox; build error

Categories

(Firefox Build System :: General, defect, blocker)

x86
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: philip, Assigned: bryner)

References

()

Details

I downloaded the source code for Firefox 0.9.2 in hopes of building my own
version to obtain a backtrace to debug another problem that I was going to
submit.  The compiler that I use is:
gcc (GCC) 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)

The build problem was fully logged and saved at the given URL.  However, here
are the last few lines in case someone searches for this bug in the future:

gmake[2]: Leaving directory `/home/pwhite/firefox-installer/xpcom/obsolete'
gmake[2]: Entering directory `/home/pwhite/firefox-installer/tools/trace-malloc/lib'
gmake[2]: *** No rule to make target `export'.  Stop.
gmake[2]: Leaving directory `/home/pwhite/firefox-installer/tools/trace-malloc/lib'
gmake[1]: *** [tier_2] Error 2
gmake[1]: Leaving directory `/home/pwhite/firefox-installer'
make: *** [default] Error 2

Once again, see the URL above for the full log of the problem, including the
commands I executed.
What is your .mozconfig ?

And please, follow build instructions you can find there :

http://www.mozilla.org/projects/firefox/build.html

Thanks.
mozjf@alussinan.org: please consider reading the log file before asking questions.

pwhite@wkst $ ./configure --prefix=/home/pwhite/firefox-custom --with-x
--with-system-jpeg --with-system-zlib --with-system-png --disable-mailnews
--enable-xft --enable-crypto --enable-xinerama --enable-single-profile
--disable-composer --enable-extensions --enable-svg --enable-leaky
--enable-trace-malloc

reporter: iirc i had to do a bit of hackery to get trace-malloc to build, but
unless someone told you to use it (and leaky), there's no reason and you're
better off just omitting them. if you want help getting it to work, please visit
irc.mozilla.org and ask for help.
Sorry for spamming but :

1) it would have been simpler to add log as an attachment
2 [details] [diff] [review]) I won't post anymore on this bug and shut up my f*ck*n* mouth.
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: 15 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.