Closed Bug 86562 Opened 23 years ago Closed 23 years ago

Linux build fails with "cannot find -lmozpng"

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 86699

People

(Reporter: ssmith, Assigned: cls)

Details

After an update circa 06/18 20:44 tbox time I've started getting a
error in the final link in xpfe/bootstrap 

  /usr/bin/ld: cannot find -lmozpng

This update would have picked up cls' partial static build landing.

.mozconfig:

  ac_add_options --disable-pedantic
  ac_add_options --disable-debug
  ac_add_options --disable-mailnews
  ac_add_options --disable-logging
  ac_add_options --disable-tests
  ac_add_options --enable-crypto
  ac_add_options --enable-svg

This is on Debian woody.
More info:

libmozpng.a exists in modules/libimg/png/.  Copying it to dist/lib/ will allow
the compile to complete.  However, on startup it fails with "libjsdom.so: cannot
open shared object file".  Copying this to dist/lib/ doesn't help, but putting
it in dist/bin/ does.

Have build/run library paths changed recently?
I cannot confirm your -lmozpng problem on a recent CVS clobber on RedHat 6.2,
but i see your libjsdom.so problem. As the summary of this bug refers to the
first problem, I filed bug 86601 for the second.
.
Assignee: asa → cls
Component: Browser-General → Build Config

*** This bug has been marked as a duplicate of 86699 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.