Closed
Bug 194127
Opened 22 years ago
Closed 21 years ago
V 1.3beta pre-compiled binary doesn't run on Solaris 2.8
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mleisher, Assigned: asa)
Details
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1) Gecko/20020827
Build Identifier: rv:1.3beta
Running 1.3beta on Solaris 2.8 with the most recent recommended patches produces:
./run-mozilla.sh -g ./mozilla-bin
MOZILLA_FIVE_HOME=.
LD_LIBRARY_PATH=.:./plugins:/usr/local/lib/mre/mre-1.3b
DISPLAY=helion:0.0
FONTCONFIG_PATH=/etc/fonts:./res/Xft
DYLD_LIBRARY_PATH=.:/usr/local/lib/mre/mre-1.3b
LIBRARY_PATH=.:./components:/usr/local/lib/mre/mre-1.3b
SHLIB_PATH=.:/usr/local/lib/mre/mre-1.3b
LIBPATH=.:/usr/local/lib/mre/mre-1.3b
ADDON_PATH=.
MOZ_PROGRAM=./mozilla-bin
MOZ_TOOLKIT=
moz_debug=1
moz_debugger=
/usr/local/bin/gdb ./mozilla-bin -x /tmp/mozargs28639
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.8"...
(no debugging symbols found)...
(gdb) r
Starting program: /usr/local/mozilla-1.3b/mozilla-bin
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New LWP 1]
[New LWP 2]
[New LWP 3]
(no debugging symbols found)...warning: Lowest section in /usr/lib/libw.so.1 is
.hash at 00000074
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New LWP 4]
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...
Program exited with code 01.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Sun-compiled GTK libraries not installed.
Reporter | ||
Updated•22 years ago
|
Summary: V 1.3beta doesn't run on Solaris 2.8 → V 1.3beta pre-compiled binary doesn't run on Solaris 2.8
Comment 1•22 years ago
|
||
Roland: Is that your build ?
You are aware of the Release notes / bug 88205?
Did you compile your own Gtk libraries?
Reporter | ||
Comment 3•22 years ago
|
||
Yes. I compiled GTK 1.2.10 and all required patches have been applied.
Comment 4•22 years ago
|
||
Mark Leisher wrote:
> Yes. I compiled GTK 1.2.10 and all required patches have been applied.
Did you installed the Recommended&security patches for Solaris before using
Mozilla (at least the Xsun and libCstd patches are _mandatory_) ?
OS: SunOS → Solaris
Reporter | ||
Comment 5•22 years ago
|
||
The 8_Recommended and security patches currently on our systems were downloaded
and applied February 1.
Comment 6•22 years ago
|
||
Mark Leisher:
Did you compile the GDK/GTK+ libraries with gcc ?
gcc-compiled shared libraries may be incompatible with binaries build using Sun
Workshop, only shared libraries build with Sun Workshop will work with both gcc
and Sun Workshop binaries... ;-(
Reporter | ||
Comment 7•22 years ago
|
||
Our GDK/GTK+ were compiled with gcc. I suspected this was the problem. We don't
use Sun Workshop and probably never will. I hope this dependency will be going
away soon. I'll just build Mozilla here in the meantime.
Vielen Dank, Roland.
Comment 8•22 years ago
|
||
Mark Leisher wrote:
> Our GDK/GTK+ were compiled with gcc. I suspected this was the problem. We
> don't use Sun Workshop and probably never will.
> I hope this dependency will be going
> away soon.
That's unlikely since this is a bug in gcc, not in Sun Workshop or Mozilla.
Maybe gcc 3.x is fixed - or not. I did not had the time to investigate that (nor
does it make much sense - even Mozillas compiled with gcc3.x are slower than
those build with Sun Workshop... ;-/ ).
BTW: The sourceforge compilefarm has Solaris 8 machines with Sun Workshop
installed; alternatively you may try the GDK/GTK+ packages from
http://www.sunfreeware.com/ ... :)
Reporter | ||
Comment 9•22 years ago
|
||
Ok. I wasn't aware of the gcc problem. I just installed gcc 3.2.2. I'll see if
that works properly.
Comment 10•22 years ago
|
||
Mark Leisher wrote:
> Ok. I wasn't aware of the gcc problem.
Maybe we should add that part to the release notes... :)
And IMHO it would be nice if someone files a bug that mozilla.org should put
some "known to be good/working" versions of libGDK/libGTK/libGLIB/etc. on
ftp.mozilla.org to cure this mess (feel free to assign it to me :) ...
Keywords: relnote
Reporter | ||
Comment 11•22 years ago
|
||
Ok. The problem compiling GLIB/GTK 1.2.10 with gcc still exists in version 3.2.2.
Comment 12•21 years ago
|
||
Is this still a problem with new builds?
pi
Comment 13•21 years ago
|
||
No response, closing.
pi
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Comment 14•21 years ago
|
||
Boris 'pi' Piwinger wrote:
> Is this still a problem with new builds?
Yes since this is a problem caused by a bug in gcc. I added a HUGE warning in
the Solaris-specific release notes and since then the number of new bugs about
this issue dropped a lot.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•