The default bug view has changed. See this FAQ.

Display which GLIBCXX symbols cause an error

RESOLVED FIXED in mozilla6



Build Config
6 years ago
6 years ago


(Reporter: glandium, Assigned: glandium)



Firefox Tracking Flags

(Not tracked)



(2 attachments)



6 years ago
Created attachment 529446 [details] [diff] [review]
Display which GLIBCXX symbols cause an error

In bug 643690, I added an error displaying GLIBCXX versions we don't want to link against. It would be more useful to also list which symbols correspond to these versions.

(Note that I used > /dev/null instead of grep -q because I don't know if we can rely on grep providing the -q option)
Attachment #529446 - Flags: review?(ted.mielczarek)

Comment 1

6 years ago
While at it, "Error" in the message doesn't seem to trigger anything on tinderbox logs :-/

Does it need to be on stderr or something?


6 years ago
Blocks: 643690

Comment 3

6 years ago
Does that mean we need TinderboxPrint *and* Error to be displayed on tbpl?
No. TinderboxPrint is what makes things show up in the build column on The error parser controls what shows up in the summary of the short log:

Comment 5

6 years ago
So, we need to abuse one of these:

Or should we add a generic type of error there ?
I'd just print TEST-UNEXPECTED-FAIL, honestly, since this is in "make check". I think we don't match "Error:" because we get too many false positives from tests that have expected JS Errors or print that string in the test text, etc.

Comment 7

6 years ago
fair enough, though it's not in make check, but in plain make.
Assignee: nobody → mh+mozilla
Comment on attachment 529446 [details] [diff] [review]
Display which GLIBCXX symbols cause an error

Review of attachment 529446 [details] [diff] [review]:

r=me with the output fixed to match the tinderbox error parser.
Attachment #529446 - Flags: review?(ted.mielczarek) → review+

Comment 9

6 years ago
Created attachment 530985 [details] [diff] [review]
Display which GLIBCXX symbols cause an error.

Comment 10

6 years ago

(the new attachment was the patch as landed)
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla6
You need to log in before you can comment on or make changes to this bug.