Arch Linux User Repository

The following key is used to sign release commits:

40481E7B8FCF9CEC

Import it into your keyring however you want.

https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key

@WorMzy - built fine using pkgctl... wonder what/where the difference is.

Built fine using the latest python2 package, in seven minutes on my system. If you're sure it's not your system resources, then the only other thing I can suggest is using a clean chroot (if you aren't already). I build using pkgctl build -I ../python2/python2-2.7.18-11-x86_64.pkg.tar.zst

Hm, I'm using an older version -- 2.7.18-8. I'll see if I can reproduce with the latest.

I'm not sure what you mean by "your python2 package" btw, I don't maintain a python package.

@WorMzy - when I switch to your python2 package, I get other errors:

Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
ImportError: No module named site
==> ERROR: A failure occurred in build().
    Aborting...

So I've switched back to 2.7.18-11. Need suggestions.

@WorMzy - what version of python2 did you use for the build? I'm using 2.7.18-11. I should also add that since python2 is being deprecated, many of my python2 packages have, over time, been lost to attrition. Is there anything lto-specific you can think of that my environment might be missing?

WorMzy: my quad-core system has 16gb of RAM and almost 6tb of disk space, with 32gb of swap - I doubt resources are my issue. This build was the only thing running other than KDE/Plasma and never showed more than 8gb of RAM usage. I had already gone ahead and found your 33.7 binary and used the 33.6 PKGBUILD, modified, to create a v33.7 palemoon release, but I've always preferred doing the build myself, which has rarely, if ever, failed. However, a google search on "ld: fatal error: lto-wrapper failed" turns up a ton of complaints, including the most recent comment for palemoon-gtk3. Perhaps this is an lto issue...

jghodd: I can't reproduce that here. Since it happens late on, my suspicion is that your memory is full (check journalctl for OOM events). Did the build really take four and a half hours to reach that point? Maybe consider using the -bin package instead, if that's an option.

Getting a build error on 33.7. It's occurring right at the end of the build, so it's incredibly annoying to reproduce:

269:01.34 lto1: internal compiler error: Segmentation fault
269:01.34 0x1e42a6a internal_error(char const*, ...)
269:01.34       ???:0
269:01.34 0xac6583 stream_read_tree_ref(lto_input_block*, data_in*)
269:01.34       ???:0
269:01.34 0xf2151c streamer_read_tree_body(lto_input_block*, data_in*, tree_node*)
269:01.34       ???:0
269:01.34 0xaca435 lto_input_tree_1(lto_input_block*, data_in*, LTO_tags, unsigned int)
269:01.34       ???:0
269:01.34 0xacaa7e lto_input_scc(lto_input_block*, data_in*, unsigned int*, unsigned int*, bool)
269:01.34       ???:0
269:01.34 0x725c2d read_cgraph_and_symbols(unsigned int, char const**)
269:01.35       ???:0
269:01.35 0x72754b lto_main()
269:01.35       ???:0
269:01.35 Please submit a full bug report, with preprocessed source (by using -freport-bug).
269:01.35 Please include the complete backtrace with any bug report.
269:01.35 See <https://gitlab.archlinux.org/archlinux/packaging/packages/gcc/-/issues> for instructions.
269:01.35 make[6]: *** [/tmp/cczvhC79.mk:188: /tmp/ccQOLpo3.ltrans62.ltrans.o] Error 1
269:01.35 make[6]: *** Waiting for unfinished jobs....
269:01.35 lto-wrapper: fatal error: make returned 2 exit status
269:01.35 compilation terminated.
269:01.35 ../../build/unix/gold/ld: fatal error: lto-wrapper failed
269:01.35 collect2: error: ld returned 1 exit status
269:01.35 make[5]: *** [/bslx/repository/palemoon/tmp/palemoon/src/Pale-Moon/platform/config/rules.mk:770: libxul.so] Error 1
269:01.35 make[4]: *** [/bslx/repository/palemoon/tmp/palemoon/src/Pale-Moon/platform/config/recurse.mk:71: toolkit/library/target] Error 2
269:01.35 make[3]: *** [/bslx/repository/palemoon/tmp/palemoon/src/Pale-Moon/platform/config/recurse.mk:33: compile] Error 2
269:01.35 make[2]: *** [/bslx/repository/palemoon/tmp/palemoon/src/Pale-Moon/platform/config/rules.mk:497: default] Error 2
269:01.35 make[1]: *** [/bslx/repository/palemoon/tmp/palemoon/src/Pale-Moon/client.mk:406: realbuild] Error 2
269:01.35 make: *** [client.mk:164: build] Error 2
269:01.36 0 compiler warnings present.
269:05.51 Failed to parse ccache stats output: Cacheable calls:    6640 / 6663 (99.65%)
==> ERROR: A failure occurred in build().
    Aborting...

@maid: that's unfortunate, but it doesn't mean the software can be built without it.

If you need assistance with the build failure, perhaps open a thread on the support channels for your distro and provide details. Alternatively, there is a python2-bin package which you can use as an alternative to compiling python yourself. To that end, there are also -bin packages for palemoon in the AUR which you can use as an alternative to compiling the browser yourself.

WorMzy, my attempt to build python2 was failed.