Package Details: firefox-esr-i18n-dsb 128.4.0-1

Git Clone URL: https://aur.archlinux.org/firefox-esr.git (read-only, click to copy)
Package Base: firefox-esr
Description: Standalone web browser from mozilla.org, Extended Support Release
Upstream URL: https://www.mozilla.org/en-US/firefox/enterprise/
Keywords: browser gecko web
Licenses: GPL, MPL, LGPL
Submitter: figue
Maintainer: dudemanguy
Last Packager: dudemanguy
Votes: 48
Popularity: 0.23
First Submitted: 2015-05-28 23:15 (UTC)
Last Updated: 2024-10-29 17:36 (UTC)

Dependencies (56)

Required by (0)

Sources (100)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 21 Next › Last »

GI_Jack commented on 2020-05-06 13:51 (UTC)

Please change

provides=(firefox)

to

provides=(firefox=${pkgver})

This way it works with packages that version check FX

figue commented on 2019-12-14 11:56 (UTC) (edited on 2019-12-14 12:06 (UTC) by figue)

New prebuilt binaries in my own openSUSE Build Service account:

[home_ffigue_Arch]
Server = http://download.opensuse.org/repositories/home:/ffigue/Arch/$arch

To verify signature, you can do like this:

$ wget -O- http://download.opensuse.org/repositories/home:/ffigue/Arch/x86_64/home_ffigue_Arch.key | sudo gpg --homedir /etc/pacman.d/gnupg --import -
$ sudo pacman-key --lsign-key F5AAC5A5424ED5CA

figue commented on 2019-12-06 21:45 (UTC)

@sp1d3rmxn thanks. Compilation with disable-elf-hack seems ok. Please test.

sp1d3rmxn commented on 2019-12-06 14:27 (UTC)

@figue

Ok the PKGBUILD change I added per the bug report has proven to also be successful with this.

Again like Icecat but, slightly different (no modifications to march/mtune either just like the Icecat build):

In the "prepare()" section under the heading "#Features" add this line:

ac_add_options --disable-elf-hack

It looks like this for me:

Features

ac_add_options --enable-alsa

ac_add_options --enable-jack

ac_add_options --enable-startup-notification

ac_add_options --enable-crashreporter

ac_add_options --disable-gconf

ac_add_options --disable-updater

ac_add_options --disable-elf-hack <---- ADD THIS LINE END

Again no further changes necessary and able to use CPU tuning as expected (no generics at all).

Hope this helps anyone going through the same headache.

figue commented on 2019-12-05 18:54 (UTC)

@sp1d3rmxn thank you, I reply you in IceCat AUR package. I have to compile FF ESR the same way. Seems that something is wrong when you tune CFLAGS...

sp1d3rmxn commented on 2019-12-05 16:36 (UTC)

This bullshit has been going on for awhile. It seems as though specifying your CPU arch is now an issue. Guess the new amateur hour devs are to <fill in the blank> to realize "x86-64" for generic purposes is weak sauce if you don't know that your CPU has specific instruction sets that can get you more bang for the buck. Anyways here's the report: https://bugs.llvm.org/show_bug.cgi?id=43659

sp1d3rmxn commented on 2019-11-22 13:43 (UTC)

@figue - Yes and no answer to your question, yes for the last 4 years we have run linux-hardened, been through many of these upgrades and no because these are stock and installed as such. The only compilation is due to packages being in AUR. We use distcc occasionally if there are a ton to upgrade but, that compiler was eliminated in these test runs.

The issues when new versions of libraries get released seems to be a decades old problem for linux devs to keep their shit straight. The comment section here is proof of the constant issues that shouldn't exist with something called "extended support ...". I did find several others who have had to downgrade to clang/llvm/rust to previous versions or others have changed the compilation back to GCC instead of the shitty clang like here: https://www.linuxquestions.org/questions/slackware-14/llvm-9-0-0-clang-segfault-firefox-build-4175661799/ or this about waterfox (another mozilla based product experiencing similar bullshit to this): https://aur.archlinux.org/packages/waterfox-classic-git/#comment-716172

I have even more links but, I think you get the idea. Doesn't seem to matter to much about the customization as much as it seems in tracking down patches due to devs not being thorough because others are experiencing identical issues and they aren't even using Arch.

I suspect others may not have gone through this because having 500 machines to manage as I do tends to show issues like this quickly.

figue commented on 2019-11-21 22:52 (UTC)

@sp1d3rmxn that's weird... Do you use stock kernel? Any other custom configuration?

sp1d3rmxn commented on 2019-11-21 15:13 (UTC) (edited on 2019-11-21 18:50 (UTC) by sp1d3rmxn)

This occurs in a fresh install with a fresh chroot environment (tried on 3 different machines that are brand new):

48:29.54 clang-9: error: unable to execute command: Segmentation fault (core dumped)

48:29.54 clang-9: error: clang frontend command failed due to signal (use -v to see invocation)

48:29.54 clang version 9.0.0 (tags/RELEASE_900/final)

48:29.54 Target: x86_64-pc-linux-gnu

48:29.54 Thread model: posix

48:29.54 InstalledDir: /usr/bin

48:29.54 clang-9: note: diagnostic msg: PLEASE submit a bug report to and include the crash backtrace, preprocessed source, and associated run script.

48:29.54 clang-9: error: unable to execute command: Segmentation fault (core dumped)

48:29.54 clang-9: error: clang frontend command failed due to signal (use -v to see invocation)

48:29.54 clang version 9.0.0 (tags/RELEASE_900/final)

48:29.54 Target: x86_64-pc-linux-gnu

48:29.54 Thread model: posix

48:29.54 InstalledDir: /usr/bin

48:29.54 clang-9: note: diagnostic msg: PLEASE submit a bug report to and include the crash backtrace, preprocessed source, and associated run script.

48:29.58 clang-9: note: diagnostic msg:

48:29.58 ****

48:29.58 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:

48:29.58 Preprocessed source(s) and associated run script(s) are located at:

48:29.58 clang-9: note: diagnostic msg: /tmp/test-ctors-36d1f3.c

48:29.58 clang-9: note: diagnostic msg: /tmp/test-ctors-36d1f3.sh

48:29.58 clang-9: note: diagnostic msg:

48:29.58 ****

48:29.58 make[4]: *** [/build/firefox-esr/src/firefox-68.2.0/config/rules.mk:755: test-ctors.o] Error 254

48:29.58 make[4]: *** Waiting for unfinished jobs....

48:29.58 clang-9: note: diagnostic msg:

48:29.58 ****

48:29.58 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:

48:29.58 Preprocessed source(s) and associated run script(s) are located at:

48:29.58 clang-9: note: diagnostic msg: /tmp/test-array-aae6dc.c

48:29.58 clang-9: note: diagnostic msg: /tmp/test-array-aae6dc.sh

48:29.58 clang-9: note: diagnostic msg:

48:29.58 ****

48:29.59 make[4]: *** [/build/firefox-esr/src/firefox-68.2.0/config/rules.mk:755: test-array.o] Error 254

48:29.59 make[3]: *** [/build/firefox-esr/src/firefox-68.2.0/config/recurse.mk:101: build/unix/elfhack/libs] Error 2

48:29.59 make[2]: *** [/build/firefox-esr/src/firefox-68.2.0/config/recurse.mk:34: libs] Error 2

48:29.59 make[1]: *** [/build/firefox-esr/src/firefox-68.2.0/config/rules.mk:413: default] Error 2

48:29.59 make: *** [client.mk:125: build] Error 2

48:29.61 159 compiler warnings present.

48:29.66 Notification center failed: Install notify-send (usually part of the libnotify package) to get a notification when the build finishes.

==> ERROR: A failure occurred in build().

Aborting...

Same exact thing outside of chroot:

52:44.67 clang-9clang-9: : error: unable to execute command: Segmentation fault (core dumped)error 52:44.67 : unable to execute command: Segmentation fault (core dumped) 52:44.67 clang-9clang-9: : error: error: clang frontend command failed due to signal (use -v to see invocation) 52:44.67 clang frontend command failed due to signal (use -v to see invocation) 52:44.67 clang version 9.0.0 (/home/sp1d3y/.cache/asp 424e7455481f941ec2259cc4c491238007cdf3d3) 52:44.67 Target: clang version 9.0.0 (/home/sp1d3y/.cache/asp 424e7455481f941ec2259cc4c491238007cdf3d3)x86_64-pc-linux-gnu 52:44.67 Thread model: Target: posixx86_64-pc-linux-gnu 52:44.67 InstalledDir: 52:44.67 /usr/binThread model: 52:44.67 posix 52:44.67 clang-9: InstalledDir: /usr/binnote 52:44.67 : diagnostic msg: PLEASE submit a bug report to and include the crash backtrace, preprocessed source, and associated run script.clang-9: 52:44.67 note: diagnostic msg: PLEASE submit a bug report to and include the crash backtrace, preprocessed source, and associated run script. 52:44.71 clang-9: note: diagnostic msg: 52:44.72 **** 52:44.72 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: 52:44.72 Preprocessed source(s) and associated run script(s) are located at: 52:44.72 clang-9: note: diagnostic msg: /tmp/test-array-7c38e4.c 52:44.72 clang-9: note: diagnostic msg: /tmp/test-array-7c38e4.sh 52:44.72 clang-9: note: diagnostic msg: 52:44.72 *** 52:44.72 clang-9: note: diagnostic msg: 52:44.72 ** 52:44.72 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: 52:44.72 Preprocessed source(s) and associated run script(s) are located at: 52:44.72 clang-9: note: diagnostic msg: /tmp/test-ctors-2a586c.c 52:44.72 clang-9: note: diagnostic msg: /tmp/test-ctors-2a586c.sh 52:44.72 clang-9: note: diagnostic msg: 52:44.72 ** 52:44.72 make[4]: [/home/sp1d3y/software/testing/firefox-esr/src/firefox-68.2.0/config/rules.mk:755: test-array.o] Error 254 52:44.72 make[4]: Waiting for unfinished jobs.... 52:44.72 make[4]: [/home/sp1d3y/software/testing/firefox-esr/src/firefox-68.2.0/config/rules.mk:755: test-ctors.o] Error 254 52:44.72 make[3]: [/home/sp1d3y/software/testing/firefox-esr/src/firefox-68.2.0/config/recurse.mk:101: build/unix/elfhack/libs] Error 2 52:44.72 make[2]: [/home/sp1d3y/software/testing/firefox-esr/src/firefox-68.2.0/config/recurse.mk:34: libs] Error 2 52:44.72 make[1]: [/home/sp1d3y/software/testing/firefox-esr/src/firefox-68.2.0/config/rules.mk:413: default] Error 2 52:44.72 make: [client.mk:125: build] Error 2 52:44.74 159 compiler warnings present. 52:44.83 /usr/bin/notify-send --app-name=Mozilla Build System Mozilla Build System Build failed ==> ERROR: A failure occurred in build(). Aborting...

clang has been recompiled and stock version used in both tests with both producing exactly the same results.

figue commented on 2019-11-19 23:56 (UTC)

@AndyRTR indeed. Thank you!

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 21 Next › Last »