problems building iceweasel 4 beta 5
Csillag Kristof
csillag.kristof at gmail.com
Wed Sep 8 19:24:29 UTC 2010
At 2010-09-08 13:36, Mike Hommey wrote:
> On Wed, Sep 08, 2010 at 01:00:14PM +0200, Csillag Kristof wrote:
>
>> Dear Debian Mozilla (& friends) package developers,
>>
>> I have tried building the Iceweasel 4.0 beta 5 packages, available here:
>>
>> http://mozilla.debian.net/packages/
>>
>> on my lenny/squeeze/sid hybrid AMD64 debian box, and I would like to
>> share my experiences with you.
>>
>> The exact version I was using is "4.0~b5-0.
>>
>> 1. I have found two build dependency problems.
>>
>> In both cases, the current version from testing/unstable is needed
>> (otherwise the build fails), but this is not explicitly declared
>> as build-dependencies:
>>
>> make: 3.81-8 is required
>> libevent-dev: 1.4.13-stable-1 is required
>>
> At what point does the build fail without these ?
>
See the attached "failing_build_w_old_make.log.gz"
for the failing build log with old (3.81-5) make.
See the attached "failing_build_w_old_libevent.log.gz"
for the failing build log with new (3.81-8) make
and old (1.3e-3) libevent-dev.
All the logs were generated after running
fakeroot debian/rules clean
, with
fakeroot debian/rules binary 2>&1
, after exporting
DEB_BUILD_OPTIONS=nocheck
>
>> 2. After waiting for a long time (several minutes, not exactly sure
>> how many), I had to kill xpcshell, while waiting for the following test
>> cases
>> (since I have already seen test cases failing, I thought that killing
>> some stalled ones would not cause any fatal problems with the build;
>> I was wrong.):
>>
>> - test_doSetAndLoadFaviconForPage_failures.js
>> - test_AddonRepository_cache.js
>> - test_bootstrap.js (I have lost my patience around here, and started
>> killing it whenever it got stalled for longer than say 30 seconds.)
>> - test_bug521905.js
>> - test_update.js
>>
>> (how long are these supposed to take, anyway?)
>>
>> When the (remaining) tests finished; the build failed, since there were
>> 12 failed
>> cases. (I have killed 5 cases; I hoped the rest were depending on these.)
>>
>> So I have restarted the build, this waiting for more than half an hour
>> (or so)
>> before of killing each stalled test cases. (Or in some cases, several
>> hours.)
>>
>> However, all the above listed test cases stalled again, even with my
>> increased timeout margin.
>>
>> Thus, I got this again:
>>
>> xpcshell-tests> INFO | Result summary:
>> xpcshell-tests> INFO | Passed: 794
>> xpcshell-tests> INFO | Failed: 12
>>
>> ... and so, the build failed.
>>
>> What do these test cases need to succeed?
>> Or, better yet, is there a way to build the packages
>> without running all these tests?
>>
> DEB_BUILD_OPTIONS=nocheck
>
Thank you, that helped.
Now I could build the packages successfully.
> I haven't tried to make them all pass yet. But the build shouldn't fail
> if you kill the right processes (the make -C build-* * ones)
>
Obviously, I killed the wrong process. (xpcshell or something like that.)
Thank you for your help, again:
Kristof Csillag
-------------- next part --------------
A non-text attachment was scrubbed...
Name: failing_build_w_old_make.log.gz
Type: application/x-gzip
Size: 50501 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/attachments/20100908/1c4808d4/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: failing_build_w_old_libevent.log.gz
Type: application/x-gzip
Size: 130104 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/attachments/20100908/1c4808d4/attachment-0003.bin>
More information about the pkg-mozilla-maintainers
mailing list