Unable to Compile librsvg (seems to be rustc)

burningserenity · n00b Joined: 18 Jul 2022 Posts: 65

Hello again forum.

I am now unable to emerge the librsvg package due to rustc not being able to find the "std" crate.

here is my build log
here is the output of emerge --info
here is the output of emerge -pqv

Any idea why the Rust compiler can't find Rust libraries?

Hu · Administrator Joined: 06 Mar 2007 Posts: 21724

You enabled 32-bit librsvg. Do you need 32-bit support for this package? If yes, what is the output of emerge --pretend --verbose gnome-base/librsvg virtual/rust dev-lang/rust-bin? If no, you could work around this by disabling 32-bit support, so that you do not need a 32-bit rust compiler. As I read the ebuild, Portage should have handled this correctly even with 32-bit enabled.

burningserenity · n00b Joined: 18 Jul 2022 Posts: 65

How do I disable 32 bit support for the package? I tried changing my use flags, but that didn't work.

I don't understand why this is happening now and not when I first installed the package.

NeddySeagoon · Posted: Fri Sep 02, 2022 5:45 pm Post subject:

burningserenity,

From your build log you have

burningserenity · n00b Joined: 18 Jul 2022 Posts: 65

burningserenity · n00b Joined: 18 Jul 2022 Posts: 65

Okay, added 32-bit support to Rust. That fixes it. Thanks for helping this newbie out.

Hu · Administrator Joined: 06 Mar 2007 Posts: 21724

What exactly did you change? As I noted earlier, I would have expected Portage to have forced you to do the right thing before beginning, so it is strange to me that you managed to start a configuration that did not work.

burningserenity · n00b Joined: 18 Jul 2022 Posts: 65

I ran

Hu · Administrator Joined: 06 Mar 2007 Posts: 21724

Next time, please show what was changed, not what command generated the changes for you. This is why I used the phrasing What exactly did you change? If I ran the command you showed, it would make no changes, because my package.use settings are already consistent. If you instead showed what you changed, there would be no question what was updated, and future readers with the same problem could apply exactly your solution.
Did you mean to add librsvg and rust to your world file?
How did that command do anything? If there were changes to be made by autounmask-write, then Portage should not have let you run the build that started this thread until those changes were made.

burningserenity · n00b Joined: 18 Jul 2022 Posts: 65

Okay a little more explanation.

I ran the suggested grip command and saw some packages with 32 bit support, including a lot of packages for cross compiling to win32 that I wasn’t using, so I took them out. Next time, I’ll have the output of the grep command, and the contents of the package.use file I removed.

Then I noticed that the librsvg package had 32-bit support enabled for it, and that I needed it, so I ran the emerge —pretend command suggested that I should run if I needed 32-bit support, which showed that rust and rust-bin would get 32-bit use flags, so I ran autounmask-write to add those flags. After I did this, I was able to compile librsvg.