Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 929013 - dev-lang/spidermonkey-115.9.1 ERROR: Don't know how to translate x86_64-pc-linux-musl for rustc
Summary: dev-lang/spidermonkey-115.9.1 ERROR: Don't know how to translate x86_64-pc-li...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Mozilla Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-09 16:52 UTC by John Doe
Modified: 2024-04-16 07:17 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Full build.log and output of emerge --info. (file_929013.txt,24.82 KB, text/plain)
2024-04-09 16:52 UTC, John Doe
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John Doe 2024-04-09 16:52:23 UTC
Created attachment 890075 [details]
Full build.log and output of emerge --info.

When trying to compile dev-lang/spidermonkey, it fails citing the following error (full log provided below) This is on the stable branch. 

```
ERROR: Don't know how to translate x86_64-pc-linux-musl for rustc.
```
Running `rustc --print target-list | grep -i musl` indeed shows that the most recent version of rust does not support the 23.0 profiles musl CHOST target, only notible mention being "x86_64-unknown-linux-musl" instead of the default gentoo "x86_64-pc-linux-musl". 

I have not tested if this is affecting packages other than dev-lang/spidermonkey and dev-lang/rustc. 

Building with rust-bin (1.77.1, 1.75.0) or the source (dev-lang/rust 1.75.0) versions also fail with the exact same behaviour. 

My personal system is running on musl/hardened/selinux, SELinux is running in permissive mode and should not be causing any problems.
Comment 1 Randy Barlow 2024-04-11 22:55:18 UTC
I'm not deeply familiar with what might be going on here, but the Rust docs also confirm that the target, in rust parlance, is x86_64-unknown-linux-musl (i.e., no pc):

https://doc.rust-lang.org/nightly/rustc/platform-support.html#tier-2-with-host-tools

Since this happens with rust-bin, do you think it might be reasonable to believe that the issue might lie in spidermonkey? Or do you suspect it's an issue in Rust itself?
Comment 2 Joonas Niilola gentoo-dev 2024-04-12 13:21:50 UTC
I guess I never synced the "fix" from #915651 to spidermonkey.

Yeah this situation is currently rather awkward with musl. Real fix needs more work (See #915651) but there is a bandaid that at least doesn't fail while compiling - but it will depend on source-built rust.
Comment 3 Larry the Git Cow gentoo-dev 2024-04-16 07:17:17 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f097074a001542ce0b10a3edd47d2c0c9e4b37db

commit f097074a001542ce0b10a3edd47d2c0c9e4b37db
Author:     Joonas Niilola <juippis@gentoo.org>
AuthorDate: 2024-04-16 07:15:53 +0000
Commit:     Joonas Niilola <juippis@gentoo.org>
CommitDate: 2024-04-16 07:17:14 +0000

    dev-lang/spidermonkey: add 115.10.0
    
     - enable llvm-18,
     - sync workarounds on musl from firefox-esr.
    
    Closes: https://bugs.gentoo.org/929013
    Closes: https://bugs.gentoo.org/829148
    Signed-off-by: Joonas Niilola <juippis@gentoo.org>

 dev-lang/spidermonkey/Manifest                     |   2 +
 dev-lang/spidermonkey/spidermonkey-115.10.0.ebuild | 504 +++++++++++++++++++++
 2 files changed, 506 insertions(+)