Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Problem compiling Seamonkey 2.18
15 views
Skip to first unread message
Iacopo Benesperi
May 17, 2013, 8:10:26 AM5/17/13
to
Hi,
following Jens suggestion, I've downloaded the revision tagged with
RELEASE_21_END from comm-release and the one tagged FIREFOX_21_0_RELEASE
from mozilla-release (extracted inside comm-release and renamed the
folder as mozilla) to compile Seamonkey 2.18 on my own.
I've used a customised .mozconfig, that I've used for years now without
any problems. Found it attached.
This time, however, the configure process fails. The first time I launch
the make command (make -f client.mk build MOZ_CURRENT_PROJECT=suite)
configuration stops saying that the venkman extension is unrecognised
and to fix the issue. If I launch the make again, without modifying
anything, the error about venkman disappears but another one arise
regarding ldap. Again, both error are attached to this message.
Can anybody help me? I've compiled Seamonkey for more than two years no
following always the same procedure without particular problems and I'm
at a loss right now.
thanks,
Iacopo
following Jens suggestion, I've downloaded the revision tagged with
RELEASE_21_END from comm-release and the one tagged FIREFOX_21_0_RELEASE
from mozilla-release (extracted inside comm-release and renamed the
folder as mozilla) to compile Seamonkey 2.18 on my own.
I've used a customised .mozconfig, that I've used for years now without
any problems. Found it attached.
This time, however, the configure process fails. The first time I launch
the make command (make -f client.mk build MOZ_CURRENT_PROJECT=suite)
configuration stops saying that the venkman extension is unrecognised
and to fix the issue. If I launch the make again, without modifying
anything, the error about venkman disappears but another one arise
regarding ldap. Again, both error are attached to this message.
Can anybody help me? I've compiled Seamonkey for more than two years no
following always the same procedure without particular problems and I'm
at a loss right now.
thanks,
Iacopo
Iacopo Benesperi
May 17, 2013, 8:14:08 AM5/17/13
to
Hi,
following Jens suggestion, I've downloaded the revision tagged with
RELEASE_21_END from comm-release and the one tagged FIREFOX_21_0_RELEASE
from mozilla-release (extracted inside comm-release and renamed the
folder as mozilla) to compile Seamonkey 2.18 on my own.
I've used a customised .mozconfig, that I've used for years now without
any problems: http://pastebin.com/htJiFCLP
following Jens suggestion, I've downloaded the revision tagged with
RELEASE_21_END from comm-release and the one tagged FIREFOX_21_0_RELEASE
from mozilla-release (extracted inside comm-release and renamed the
folder as mozilla) to compile Seamonkey 2.18 on my own.
I've used a customised .mozconfig, that I've used for years now without
This time, however, the configure process fails. The first time I launch
the make command (make -f client.mk build MOZ_CURRENT_PROJECT=suite)
configuration stops saying that the venkman extension is unrecognised
and to fix the issue. If I launch the make again, without modifying
anything, the error about venkman disappears but another one arise
Neil
May 17, 2013, 12:05:07 PM5/17/13
to
want to use --skip-comm and --skip-mozilla as you have already
downloaded the correct versions of those.
--
Warning: May contain traces of nuts.
Jens Hatlak
May 17, 2013, 12:18:25 PM5/17/13
to
Iacopo Benesperi wrote:
> following Jens suggestion, I've downloaded the revision tagged with
> RELEASE_21_END from comm-release and the one tagged FIREFOX_21_0_RELEASE
> from mozilla-release (extracted inside comm-release and renamed the
> folder as mozilla) to compile Seamonkey 2.18 on my own.
As Neil said, using client.py is recommended. The reason why your build
> following Jens suggestion, I've downloaded the revision tagged with
> RELEASE_21_END from comm-release and the one tagged FIREFOX_21_0_RELEASE
> from mozilla-release (extracted inside comm-release and renamed the
> folder as mozilla) to compile Seamonkey 2.18 on my own.
fails is that pulling from c-c and m-c is not enough. client.py takes
care of the rest, namely the repositories chatzilla, venkman, and
dom-inspector, plus ldap-sdks. For URLs and revisions, see
<http://hg.mozilla.org/releases/comm-release/file/bec3f98770d1/client.py> starting
at line 18 (destinations start at line 387).
HTH
Jens
--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
0 new messages