Closed
Bug 87689
Opened 24 years ago
Closed 24 years ago
need ability to generate a statically linked build
Categories
(SeaMonkey :: Build Config, defect, P2)
Tracking
(Not tracked)
VERIFIED
INVALID
mozilla0.9.3
People
(Reporter: jdunn, Assigned: jdunn)
References
Details
Per the linux bug http://bugzilla.mozilla.org/show_bug.cgi?id=46775
we need to be able to mimic their work and so need to be able to
create static linked builds.
marking thiat this depends on 46775
Initial build of this fails on HP-UX
cvs co -r STATIC_BUILD_20010418_BRANCH mozilla/client.mk
cd mozilla
configure --enable-static --disable-shared
in xpcom/tools/registry in that it can't find sem_post and
other sem_<funcs> which are found in either libc_r or librt.
If we (HP) deside to link like this, then we have to setup
nspr-config --libs such that it returns -lpthread PLUS -lrt
(we can't use libc_r since this messes us up in the ldap
code with gethostbyname_r). When nspr is built on HP
libnspr4 is usually built with -lpthread and -lrt so we
have to make sure that nspr-config --libs when linking
staticly returneds -lrt also.
I am not sure how to do this... but will look.
Comment 2•24 years ago
|
||
NSPR must be excluded from the static linked build.
You should only link with NSPR shared libraries on
all platforms.
wtc, this not about making nspr build static. It's about making nspr-config
--libs return the proper hp-ux os_libs so that all symbols are resolved at link
time.
jdunn, I'm pretty sure al you need to do is set OS_LIBS to include the proper
libs in nsprpub/configure{,.in} . nspr-config should pick up those values and
use them in the --libs output.
Comment 4•24 years ago
|
||
Chris,
This is the HP-UX version of the problem you ran into when you
built Mozilla statically linked on Solaris and found that you
need to link with -lsocket -lnsl. On HP-UX, libnspr4.sl is implicitly
linked with -lrt and is the only caller of the sem_* functions in
Mozilla. Therefore, if Mozilla is linked with libnspr4.sl, it is
not necessary to link with -lrt explicitly.
wtc, you're right. My mistake. I didn't notice that jdunn is using the
extremely old static build branch.
jdunn, all of the static build work has landed on the trunk and is available
from the 0.9.2 branch (if you need something stable). At the very minimum, you
should use the STATIC_BUILD_20010612_BRANCH tag.
building from the trunk with --enable-static --disable-shared
works fine on HP. resolving this as invalid
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•