Closed
Bug 1230738
Opened 10 years ago
Closed 10 years ago
Simple SeaMonkey build end with a Firefox
Categories
(SeaMonkey :: Build Config, defect)
SeaMonkey
Build Config
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1186863
People
(Reporter: nicolas.vanhaelewyn, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0 SeaMonkey/2.34a1
Build ID: 20141214123232
Steps to reproduce:
Following the doc "Simple SeaMonkey build". (https://developer.mozilla.org/en-US/docs/Simple_SeaMonkey_build)
Two hosts tried Ubuntu Linux and Debian Linux.
Use the comm-central repository : hg clone http://hg.mozilla.org/comm-central/
cd comm-central
python client.py checkout
echo 'ac_add_options --enable-application=suite' > .mozconfig
echo 'mk_add_options MOZ_OBJDIR=/my_path/to/comm-central/obj-sm-release' >> .mozconfig
make -f client.mk
Actual results:
you get a working Firefox inside the obj-sm-release/dist/bin directory.
Expected results:
you should get a working SeaMonkey inside the obj-sm-release/dist/bin directory.
At the very beginning of your build do you get a message about running mach mercurial-setup?
You can tell whether it has been run or not as it creates a .mozbuild directory within your home directory.
mach lives in the mozilla subdirectory of comm-central
Potentially creating the .mozbuild directory within your home directory should also fix the issue without having to run mach mercurial-setup
See bug 1186863
Flags: needinfo?(nicolas.vanhaelewyn)
| Reporter | ||
Comment 2•10 years ago
|
||
Thank you Ian,
I had the "mach ..." message at the beginning of my build. It was not ran, and the directory .mozbuild was not created.
First I created the .mozbuild directory.
Than I ran the mach mercurial-setup which failed. I did not record the error message.
Then I compiled and got a fresh new seamonkey (2.42a1).
It is indeed the same bug as the 1186863.
Flags: needinfo?(nicolas.vanhaelewyn)
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•