mitmproxy won't build

leyvi · Tux's lil' helper Joined: 08 Sep 2023 Posts: 134

Been trying to emerge net-proxy/mitmproxy, but net-proxy/mitmproxy-rs always fails with the "ld: file format not recognized" error, see the log here. Anyone know how I can fix this? I have a bunch of other packages that fail with the same error, so maybe whatever solves this will solve those, too.

pingtoo · Posted: Tue Jan 14, 2025 4:11 pm Post subject:

You post build.log is for net-proxy/mitmproxy-rs.

sam_ · Developer Joined: 14 Aug 2020 Posts: 2144

You can't use Rust LTO unless you build with Clang.

leyvi · Tux's lil' helper Joined: 08 Sep 2023 Posts: 134

sam_, I'm not building it with LTO. pingtoo, yes, I'll correct that.

sam_ · Developer Joined: 14 Aug 2020 Posts: 2144

The log has '-C linker-plugin-lto' (and later -C lto) but it might be being forced by the upstream project if you're not doing that.

leyvi · Tux's lil' helper Joined: 08 Sep 2023 Posts: 134

OK, so should I try forcing clang to be the C compiler, just for this build?

sam_ · Developer Joined: 14 Aug 2020 Posts: 2144

Yes, please give it a go. But please file a bug at bugs.gentoo.org with the build.log and emerge --info.

leyvi · Tux's lil' helper Joined: 08 Sep 2023 Posts: 134

I tried forcing clang, and there was a slightly different error message: "lto can only be run for executables, cdylibs and static library outputs". Pretty sure it's an upstream problem.

leyvi · Tux's lil' helper Joined: 08 Sep 2023 Posts: 134

I tried filling a bug report, they were impatient and wouldn't even let me finish describing my bug to them before they closed the report. Now what?

Hu · Administrator Joined: 06 Mar 2007 Posts: 23101

How did they cut you off while you were writing the initial report? They shouldn't even know a report is coming until you finish writing the initial report. Could you link to where this was done, so we can see what was said?

sam_ · Developer Joined: 14 Aug 2020 Posts: 2144

Presumably you mean bug 948146 where you were not "cut off" at all and we're still waiting for you to come back with fixed configuration.

leyvi · Tux's lil' helper Joined: 08 Sep 2023 Posts: 134

It seems like my bug was forgotten about, or that whoever was assigned to it got frustrated.
I still can't build it. I have no idea why. Maybe the problem is a corrupted library that needs to be rebuilt?
Or maybe, since I use both GCC and Clang on my system, there's a linker compatibility issue?
Whatever the problem might be, any help would be greatly appreciated. I've been looking forward to using this for a while.

leyvi · Tux's lil' helper Joined: 08 Sep 2023 Posts: 134

I've found something that may be the cause:
The `ld.bfd` linker is getting used, even though LLVM has been used for everything else. Also, LD="lld" (in both my config _and_ in the environment from the failed build), so this shouldn't be happening.
See this build log for more details:
https://0x0.st/8Pk_.log
Is this perhaps caused by portage itself? I didn't see it in the ebuild, but there's a lot of eclasses used by it...

leyvi · Tux's lil' helper Joined: 08 Sep 2023 Posts: 134

I fixed it!
Here's what I did to my build environment:
-LD="lld"
+LD="ld.lld"
+LDFLAGS="-Wl,-O2 -Wl,--as-needed -fuse-ld=lld"
If you can't tell, I'm using LLVM for this package.
I found the solution on the wiki, under the "Troubleshooting" section of the "Clang" page.