Closed
Bug 1439423
Opened 7 years ago
Closed 7 years ago
Firefox 58.0.2 fails to build with rust 1.24
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: heirecka, Unassigned)
Details
Attachments
(1 file)
758.04 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20180130223149
Steps to reproduce:
Trying to build Firefox with rust 1.24
Actual results:
It fails to build, the log is attached.
Expected results:
Should build successfully.
Updated•7 years ago
|
Attachment #8952223 -
Attachment mime type: application/octet-stream → text/plain
Comment 1•7 years ago
|
||
Relevant part of the log:
/var/tmp/paludis/build/net-www-firefox-58.0.2/work/build/dist/include/mozilla/Compiler.h:49:12: fatal error: 'cstddef' file not found
thread '<unnamed>' panicked at 'Failed to generate bindings, (...)'
This kind of rings a bell. Nathan, weren't you involved in something similar?
Flags: needinfo?(nfroyd)
![]() |
||
Comment 2•7 years ago
|
||
I was, but the usual platform where we saw this was Mac, and I think the build log is from Linux (Gentoo?).
Is there anything peculiar about where Gentoo stores its libstdc++ (libc++?) headers, and would the clang in use (presumably /usr/bin/clang, as returned by /usr/bin/llvm-config) normally have trouble finding those?
Flags: needinfo?(nfroyd)
![]() |
||
Comment 3•7 years ago
|
||
Also, this is the second or third report we've had about Rust 1.24 doing weird things (see bug 1439278), so:
1) How does Gentoo build Rust? and
2) Does the problem reproduce on Gentoo if you use upstream's build of Rust instead of Gentoo's build?
Flags: needinfo?(heiko)
Updated•7 years ago
|
Product: Core → Firefox Build System
![]() |
||
Comment 4•7 years ago
|
||
It looks like this was a problem specific to Rust 1.24 and the way distributions built it.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(heiko)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•