Hi,
On Tue, Mar 21, 2023 at 1:03 PM Jessica Clarke <jrt...@debian.org> wrote: > > On 21 Mar 2023, at 04:49, Bo YU <tsu.y...@gmail.com> wrote: > > > > Source: firefox > > Followup-For: Bug #1012218 > > > > Hi, > > > > Now the firefox 111 can be built with patch attached on qemu > > But unfortunately, it is still not able to build real riscv64 > > hardware(Unmatched board) due to running out of resources at > > ld pharse. > > Is it doing LTO or something? 16 GiB is a lot of memory for the linker Oh, you hit me here. I checked the ld flags(runtime, hang of ld phrase) again: ``` -plugin /usr/lib/gcc/riscv64-linux-gnu/12/liblto_plugin.so -plugin-opt=/usr/lib/gcc/riscv64-linux-gnu/12/lto-wrapper ``` https://paste.debian.net/1274601/ (please note here the ld is bfd I try). So I think LTO is enabled? I will do some tests with explicitly configuring it with ``` export DEB_BUILD_MAINT_OPTIONS=optimize=-lto ``` from [0]. > to exhaust, especially for a non-debug build, even accounting for GNU > ld’s inefficiency compared with other linkers. Though presumably it > should build just fine if you add a swap partition, Yeah, I have added swap partition here. >or reduce parallelism if the problem is linking multiple large binaries at the > same time? hmm, This is a possible direction to try also. Do we have flags to enable it for Debian here？ Many thanks. BR, Bo [0]: https://wiki.debian.org/ToolChain/LTO
