SeaMonkey 2.x should run |make check| on Linux64 optimized build, like Firefox; (SM 2.1 fails due to "libstdc++.so.6: version 'GLIBCXX_3.4.9' not found")

VERIFIED FIXED in seamonkey2.1b2

Status

SeaMonkey
Release Engineering
--
enhancement
VERIFIED FIXED
7 years ago
7 years ago

People

(Reporter: sgautherie, Assigned: Robert Kaiser)

Tracking

Trunk
seamonkey2.1b2
x86_64
Linux
Dependency tree / graph
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [WontFix for SM 2.0])

(Reporter)

Description

7 years ago
It was briefly enabled on SM 2.1 but the js-tests part was failing...
We should solve that.

It should be tried on SM 2.0 too, like Firefox 3.5.
Flags: in-testsuite-
(Assignee)

Comment 1

7 years ago
CANTFIX as it fails.
Component: Testing Infrastructure → Release Engineering
QA Contact: testing-infrastructure → release
(Reporter)

Comment 2

7 years ago
This bug is to investigate that...

It seemed to be a build environment issue.
Could you copy the error here?
(Assignee)

Comment 3

7 years ago
gmake[3]: Entering directory `/builds/slave/comm-central-trunk-linux64/build/objdir/mozilla/js/src/jsapi-tests'
../../../dist/bin/run-mozilla.sh ../../../dist/bin/jsapi-tests
../../../dist/bin/jsapi-tests: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by ../../../dist/bin/jsapi-tests)
NEXT ERROR gmake[3]: *** [check] Error 1
gmake[3]: Leaving directory `/builds/slave/comm-central-trunk-linux64/build/objdir/mozilla/js/src/jsapi-tests'
gmake[2]: *** [check] Error 2

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1270053004.1270054567.16602.gz
(Reporter)

Comment 4

7 years ago
First link I found:
http://www.linuxquestions.org/questions/linux-newbie-8/usr-lib-libstdc-so-6-version-%60glibcxx_3-4-9-not-found-required-example1-604625/
This would seem to confirm that maybe our Linux64 box(es) libstdc++.so.6 is not up-to-date.
Could that be possible?

And in case that applies:
https://wiki.mozilla.org/ReferencePlatforms/Linux-CentOS-5.0_64-bit
(Reporter)

Comment 5

7 years ago
And fwiw: bug 526868 and bug 554854.
(Assignee)

Comment 6

7 years ago
(In reply to comment #4)
> First link I found:
> http://www.linuxquestions.org/questions/linux-newbie-8/usr-lib-libstdc-so-6-version-%60glibcxx_3-4-9-not-found-required-example1-604625/
> This would seem to confirm that maybe our Linux64 box(es) libstdc++.so.6 is not
> up-to-date.
> Could that be possible?

Everthing's possible, but I've set that box up following the refplatform docs.

> And in case that applies:
> https://wiki.mozilla.org/ReferencePlatforms/Linux-CentOS-5.0_64-bit

That's exactly what I was following when I set this up - has there recently been some change that updates LD_LIBRARY_PATH or so?

(In reply to comment #5)
> And fwiw: bug 526868 and bug 554854.

Those don't change anything wrt to build machines (yet).
(Reporter)

Updated

7 years ago
Depends on: 554854
(Reporter)

Comment 7

7 years ago
(In reply to comment #0)

> It was briefly enabled on SM 2.1 but the js-tests part was failing...

Jason, jsapi-tests pass with FF 3.7:
could it be a "static vs libxul" related issue?

> It should be tried on SM 2.0 too, like Firefox 3.5.

Robert, SM 2.0 "should" pass, as jsapi-tests don't exist there...
Blocks: 505798
Summary: SeaMonkey 2.x should run |make check| on Linux64 optimized build, like Firefox → SeaMonkey 2.x should run |make check| on Linux64 optimized build, like Firefox: failing due to "libstdc++.so.6: version 'GLIBCXX_3.4.9' not found"
(Reporter)

Updated

7 years ago
Summary: SeaMonkey 2.x should run |make check| on Linux64 optimized build, like Firefox: failing due to "libstdc++.so.6: version 'GLIBCXX_3.4.9' not found" → SeaMonkey 2.x should run |make check| on Linux64 optimized build, like Firefox; (SM 2.1 fails due to "libstdc++.so.6: version 'GLIBCXX_3.4.9' not found")
(Assignee)

Comment 8

7 years ago
(In reply to comment #7)
> Robert, SM 2.0 "should" pass, as jsapi-tests don't exist there...

I won't change anything on what we execute on the SeaMonkey 2.0 tree, we're going with completely different test execution, etc. there, and it's a stable tree, it's only for maintenance and not for trying "new" stuff.
(In reply to comment #7)
> > It was briefly enabled on SM 2.1 but the js-tests part was failing...
> 
> Jason, jsapi-tests pass with FF 3.7:
> could it be a "static vs libxul" related issue?

I doubt it. jsapi-tests doesn't link against libxul. At least, I don't think it does -- the build system isn't my strong suit.

According to js/src/jsapi-tests/Makefile.in, it links against NSPR and libjs_static.a.

jsapi-tests uses std::string. I don't think we have any other code using it. Most likely this bug is a combination of that and something weird in the build environment. If you'd like to fix it by changing the code to stop using std::string, I have no objection. It looks like its use is limited to js/src/jsapi-tests/tests.{h,cpp}. Also note that you could #include "jsvector.h" and use js::Vector<char> as a substitute.
(Reporter)

Comment 10

7 years ago
CC'ed Benjamin to get help, per
https://developer.mozilla.org/en/Supported_build_configurations
"Tier-2 platforms
Linux/x86-64 — maintained by Benjamin Smedberg"
Tinderbox just sporadically hit this same issue (matching the error text in comment 3) for a mozilla-central build.
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1271791419.1271796208.27060.gz
Linux x86-64 mozilla-central build on 2010/04/20 12:23:39
s: moz2-linux64-slave05
(Reporter)

Comment 12

7 years ago
(In reply to comment #11)
> Tinderbox just sporadically hit this same issue (matching the error text in
> comment 3) for a mozilla-central build.

That's "good" to know, but you should file a (blocking) bug, as this one is about SeaMonkey |make check|.
(Assignee)

Comment 13

7 years ago
Actually, this bug is about turning |make check| on for SeaMonkey at all for Linux64, the failures should get their own bug though, no matter for what app :)
Ah, my apologies for the mis-post. :) It initially looked like this bug was sort of on both issues (i.e. fixing the library issue first, so that |make check| *can* be turned on for Seamonkey).

Anyway, I filed Bug 560894 on the failures.
(Assignee)

Updated

7 years ago
Depends on: 560894
(Assignee)

Comment 15

7 years ago
Right now, even investigation of |make check| doesn't make sense due to bug 563643 :(
Depends on: 563643
(Reporter)

Updated

7 years ago
Depends on: 563491
No longer depends on: 563643
(Assignee)

Comment 16

7 years ago
Tried again for trunk only with http://hg.mozilla.org/build/buildbot-configs/rev/72d8f2ab16d2
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Reporter)

Comment 17

7 years ago
V.Fixed, per
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1291996082.1291997845.32699.gz
Linux x86-64 comm-central-trunk build on 2010/12/10 07:48:02
{
check: 1098/0
}
Assignee: nobody → kairo
Status: RESOLVED → VERIFIED
Whiteboard: [WontFix for SM 2.0]
Target Milestone: --- → seamonkey2.1b2
(Reporter)

Updated

7 years ago
OS: All → Linux
Hardware: All → x86_64
You need to log in before you can comment on or make changes to this bug.