549892 - libmozz.so is missing in the tarball

Status: RESOLVED WORKSFORME

(Thunderbird :: Build Config, defect)

Description

[Hideo Oshima]

Steps to reproduce:
1. Pull source code from comm-central
2. python clicent.py and make -f client
3. cd to object directory and make package
4. cd to working directory and untar tarball
5. Start thunderbird

Actual result:
Cannot start:
"thunderbird/thunderbird-bin: error while loading shared libraries: libmozz.so: cannot open shared object file: No such file or directory"

My .mozconfig:
ac_add_options --enable-application=mail
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/tb-opt
mk_add_options AUTOCONF=autoconf2.13
mk_add_options MOZ_MAKE_FLAGS="-j4"
ac_add_options --enable-static

Comment 1

[Hideo Oshima]

I copied libmozz.so from $(OBJDIR)/mozilla/dist/bin/libmozz.so
to untarred directory that is thunderbird, then it works for me.

Comment 2

[Mark Banner (:standard8)]

From what I can tell, the only way you'd get libmozz.so being generated separately is to have a shared build. The tinderboxes certainly are not generating it separately, and it is included in the packaging files for non-static builds.

Did you actually add --enable-static later, without removing the object directory in-between re-compiles? As that's about the only way I could think that something like this would happen.

Comment 3

[Hideo Oshima]

(In reply to comment #2)
> Did you actually add --enable-static later, without removing the object
> directory in-between re-compiles? As that's about the only way I could think
> that something like this would happen.

I deleted all files, pulled sources from comm-central and build again.
So Thunderbird starts without any problem.
Maybe you are wright.

Comment 4

[Mark Banner (:standard8)]

Ok, if it works from a clean build, that's what we generally support (switching options like static versus non-static in a build would be very hard to support).

Marking as Works for me, as it is obviously working for you now. Thanks for trying again.