34566 - Mozilla requires a dynamic libstdc++

Status: RESOLVED WONTFIX

(SeaMonkey :: Build Config, defect, P3)

Description

[allmaier hannes]

First, I tried to run the M14 binary downloaded at your webpage; however there 
was a link to the libstdc++-libc6.1-... that I don't have (I've got only a 
static libstdc++ 2.10 of my gcc 2.95.2) so the whole thing refused to work 
(failed selfregistering and such things).

As consequence I downloaded the M14 sources and compiled them with the standard 
settings; it compiled cleanly.

When starting mozilla the whole process seems to work correctly, but in the end 
I get only a segfault.

I'm using glibc 2.1.3 and don't have Internet access on my machine, not even a 
network - is it possible to run mozilla only to view html-files on my local 
machine? hope so.

however, due to system problems I cannot send you the logfile of the crash I 
created; send me an email adress where I can send it to.

THANX

hannes allmaier

Comment 1

[Alan S. Jones]

I think this is a dupe 
of bug 15976 wich is a dupe of bug 15970

But I don't know enough to say for sure.

Hannes or someone can you look at those two bugs?

If so we can mark it a dupe and go on.

Comment 2

[Akkana Peck]

I wouldn't mark it as a dup, since this is probably a different issue than the
ones so far brought up in 15970.  We may need a tree of bugs for the various
reasons it won't run on each specific distribution.

Comment 3

[allmaier hannes]

No it's definitely not a dup of bug 15976 or 15970. Yes I downloaded the binary
tarballs and they didn't start because of these 2 bugs (actually because of this
one bug - they're dupes).

As a consequence I downloaded the sources and compiled them on my machine. I've
no libstdc++-libc6.1... ;I've only the static 2.10 of the compiler itself, but
that's not the problem (I think).

Comment 4

[Doron Rosenberg (IBM)]

--> build config

Comment 5

[allmaier hannes]

Attachment: output of mozilla when started

Comment 6

[cls]

All I see in the attachment is garbage.

Comment 7

[cls]

Based upon the comments in Bug 13202, it sounds like you can't statically link
against libstdc++ (among other libs).  Pav? Leaf? Dmose? Do you know if this is
really the case?

Comment 8

[Dan Mosedale (:dmosedale, :dmose)]

I wouldn't be surprised.  What's probably happening is that non-PIC code from
libstdc++.a is getting pulled into a shared library, which is a no-no.  I've got
bug 35419 assigned to me, which, once fixed, will cause the compile to abort if
non-PIC code gets linked into a shared library, rather than incorrectly
succeeding.

So I suspect the answer is that you need to install the shared version of
libstdc++.

 

Comment 9

[Chris Yeh]

mass re-assign of all bugs where i was listed as the qa contact

Comment 10

[cls]

Changing the summary to be more descriptive of the problem.

dmose, your fix is solaris specific, right?  By default, the build does use
-shared to create shared libraries.  Would a libstdc++.a compiled entirely with
-fPIC (if possible) fix this problem?

Comment 11

[Dan Mosedale (:dmosedale, :dmose)]

Yes, my fix is Solaris only.  And I suspect you're right, that a libstdc++ built
entirely with -fPIC would be ok.  Though it would add bloat to the browser, and
perhaps a non-trivial amount.

Comment 12

[cls]

I was not able to get a static libstdc++ working with linux.  It keeps crashing
in libdl.  Marking WONTFIX.