All users were logged out of Bugzilla on October 13th, 2018
Please direct this to the best person: The FreeBSD binary in the M12 release area can not be run, because it is linked to some libraries that aren't in the distribution or on most systems (libintl.so). If it isn't presumptuous to think other people probably can't get it to work either because of this, in the url is a package that works fine on all of my systems. If there is a special way to package releases, let me know (or fix this or however). I will attach some build and install hints as well if someone might find them useful.
I did the binary build here on my 3.2 release box. Which ran fine on two other 3.3 release boxes. In fact yesterday i ran it on a freshly installed 3.3 box with no mozilla sources just gtk and glib. When things stablize a little more these packages will improve and we will hopefully get a port up and running to build from source. Because as it stands right now there is one patch i am using to build the source on 3.x versions to work around the dll loader prob. Thanks for all the feedback and help. pete (a fellow freebsder)
It's dependent on installing the info files distribution for some reason though. Kinda goofy.
*** Bug 25542 has been marked as a duplicate of this bug. ***
mass re-assign of all bugs where i was listed as the qa contact
QA Contact: cyeh → chofmann
Is this still an issue? Or can this bug be closed as a non-issue?
It's still a problem as of the M15 release. The binary is dependant on installing the optional and unrelated info files distribution.
Works for me: FreeBSD-current nightly source tarballs and CVS pulls
This bug is really old, shouldn't it get cleared out because it really isn't useful? (sorry for spam)
May be marked FIXED as there're now recent (0.9.4) binary FreeBSD releases. However, similar "recent" bugs exist: see bug 92400.
reporter: are you still seeing this with a recent version of mozilla?
ldd mozilla-bin shows it doesn't link to libintl. and recent freebsd binaries work fine. maybe this dated bug could be closed.
resolving (pete, feel free to spank me if I'm out of line)
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.