#BUG: rustc does not support recent CHOST change. (dev-lang/spidermonkey)

1 messages · Page 1 of 1 (latest)

ashen sandal
#

Update

This issue is still unfixed, unless you change your CHOST to something else other than musl, you're out of luck. The bugzilla report is still up, hopefully someone will look at it soon.

Hello you wonderful chaps,

I've recently installed musl/hardened Gentoo and it works perfectly, albeit with some USE flag fixes. I'm trying to install gnome-light, which requires dev-lang/spidermonkey.
I should also mention that I have went through the SELinux/Installation, SELinux is running in permissive mode and should not be causing any problems.

This package fails to build with the following error during configuration:

ERROR: Don't know how to translate x86_64-pc-linux-musl for rustc.

Since this issue seems to be related to rust, I compiled the rust package instead of using rust-bin, as the Musl usage guide notes that some packages on musl will fail to build if rust isn't installed from source. This did not fix the issue, behaviour remains the same.

Logs

build.log : https://bpa.st/EI3Q
config.log : https://bpa.st/QAVQ
Output of emerge --info: https://bpa.st/Q2XA
make.conf.: https://bpa.st/MXBA

Related bug (-s)

https://bugs.gentoo.org/show_bug.cgi?id=917396
https://bugs.gentoo.org/show_bug.cgi?id=929013 ( The bug described in this post )

#

Rustc does not have support for the gentoo musl target, even though it is generic. Why? Well I suspect its because the target was recently renamed to *-pc-* , previously used *-gentoo-* (which didn't make any sense since it was generic)

Even though these two CHOST targets should be the same, their named differently and so rustc fails.

Conflict.: x86_64-unknown-linux-musl IS NOT x86_64-pc-linux-musl (My current CHOST, came with the stage3 and 23.0 profile, I have not changed my CHOST.)

elder trench
#

whats your rust version?

#

usually with musl related things it gets fixed in the more up to date packages so I am always on ~amd64

#

one thing to keep in mind is if things fail to compile you can find patches in the alpine repositories apply them yourself and create a bug report on bugs.gentoo.org

ashen sandal
elder trench
#

also next time before showing logs use ansifilter

#

im on rustc 1.77.1

ashen sandal
#

That's because you're on ~amd64.

#

I would like to avoid using the unstable branch if possible.

elder trench
#

you should update rust

#

there is nothing "unstable" about unstable

ashen sandal
ashen sandal
#

Even after a few months it was a pain, doing a reinstall without it made my experience much better.

#

If you have no more Ideas I'll install rust-bin with the ~amd64 keyword. (Without doing so for my entire system).

elder trench
#

well I cant suggest anything other than updating rust or backporting a patch from the later versions. 1.75.0 was released at dec 28 before the gentoo chost change

#

specifically on musl there was a few problems with the chost a few months back which got fixed later

ashen sandal
#

I'm installing rust-bin now, I'll see if that fixes it.

elder trench
#

go for it

ashen sandal
#

It does not fix the issue, it finals with the exact same error.

#

Checking the build log does indeed show it checking the rustc version, 1.77.1

elder trench
#

I have rust-bin installed its for system bootsrapping the source dev-lang rust

ashen sandal
elder trench
# 
query d rust-bin
 * These packages depend on rust-bin:
dev-lang/rust-1.77.1 (system-bootstrap ? =dev-lang/rust-bin-1.76*)
                     (system-bootstrap ? =dev-lang/rust-bin-1.77*)
virtual/rust-1.77.1 (~dev-lang/rust-bin-1.77.1[profiler?,rustfmt?,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?])
www-client/firefox-124.0.2 (!elibc_glibc ? <dev-lang/rust-bin-1.73)
#

system-boostrap

ashen sandal
#

While I could try compiling a newer version of rust from source I don't see how that could fix the problem.

elder trench
#

let me compile your spidermonkey

ashen sandal
ashen sandal
elder trench
#

i have the same chost

ashen sandal
#

I'll try to look online a little more and see if anyone else has the same issue.

elder trench
#

the issue here is the chost not the processor

#

im just seeing if i get this exact error or not

ashen sandal
#

Oh sorry I read that wrong I thought you meant something else.

elder trench
#

oh its a bug

ashen sandal
#

On bugzilla?

elder trench
#

no it fails to compile for me to looks like this package doesn't understand the new chost gentoo uses

#

submit a bug on bugzillla

#

i dont think anyone else is able to compile it

ashen sandal
#

Run rustc --print target-list | grep -i musl and see if your target is there.

elder trench
#

a similar thing happened with firefox last year if you were using musl then

ashen sandal
elder trench
#

flatpak on musl?

ashen sandal
#

Well, yeah.

elder trench
#

yeah so rustc only has x86_64-unkown-linux-musl

#

doesn't have pc

ashen sandal
#

Makes sense.

#

BUG: rustc does not support recent CHOST change. (dev-lang/spidermonkey)

#

I'll look for a similar bug on bugzilla, if I can't find one, I'll submit one*

#

Looks like there is one bug with someone having an issue with rustc, specifically with spidermonkey but its not CHOST related. Guess I'll have to make one.

Peace 👋

ashen sandal
elder trench
#

yeah before the chost was -gentoo- which was fun times