278253 - nightly source tarball contains .mozconfig

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, defect)

Description

[Vincent Lefevre]

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

I have "ac_add_options --enable-default-toolkit=gtk2" in my .mozconfig file and
I tried to build Mozilla with "make -f client.mk", but the configure script
complained:

[...]
checking for gtk-config... no
checking for GTK - version >= 1.2.0... no
*** The gtk-config script installed by GTK could not be found.
*** If GTK was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the GTK_CONFIG environment variable to the
*** full path to gtk-config.
*** GTK+ is available from ftp://ftp.gtk.org/pub/gtk
configure: error: Test for GTK failed.
*** Fix above errors and then restart with "make -f client.mk build"
make: *** [/home/lefevre/software/moz-source/mozilla/Makefile] Error 1

gtk-config is gtk1.2 stuff, so the configure script shouldn't require it when
building Mozilla with gtk2.

Reproducible: Always

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

are you sure mozilla finds your mozconfig? does it list its contents at the top
when running it?

Comment 2

[Vincent Lefevre]

This is the problem. I grabbed
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.8a6/source/mozilla-source-1.8a6.tar.bz2
but this tarball has a .mozconfig file (I think this is a bad idea), so that
mine wasn't taken into account.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

urg, indeed. that's bad... reopening bug.

> tar tjf mozilla-source-1.8a6.tar.bz2 |grep mozconf
mozilla/.mozconfig

Comment 4

[Christian :Biesinger (don't email me, ping me on IRC)]

so this .mozconfig does have the advantage that no further configure options are
needed to get a seamonkey build. it has the disadvantage that a ~/.mozconfig is
ignored.

Comment 5

[Benjamin Smedberg]

I heard that cmp was playing around with making the somewhat-nightly source
tarballs have all the sources necessary for suite/ff/tb/sunbird/xulrunner, in
which case we should not be shipping a .mozconfig.

Comment 6

[Chase Phillips]

If I understand the problem correctly, the immediate fix is to generate a source
tarball that doesn't have a .mozconfig in it.  I'll do this and update the FTP
site accordingly.  I've also updated the script that creates these source
tarballs so that the .mozconfig file is not left in the directory that gets tarred.

Comment 7

[Chase Phillips]

Resolving fixed.