On Sat, Jul 06, 2019 at 06:06:12PM +0200, Riccardo G Corsi via blfs-support wrote: > Hello, I've tried to compile Firefox 67.0.4 (I have 66 running) on BLFS 8.4 > (some of components like ffmepg are upgraded), so I have GCC 8.1 not 9. > > Compilation stops on : > > 58:47.89 media/ffvpx/libavcodec/libmozavcodec.so > 58:48.12 /usr/bin/ld: x86/fft.o: warning: relocation against `ff_cos_512' in > read-only section `.text' > 58:48.12 /usr/bin/ld: x86/fft.o: relocation R_X86_64_PC32 against symbol > `ff_cos_32' can not be used when making a shared object; recompile with > -fPIC > > and then error with ld. >
I've not seen this error, but it looks like https://bugzilla.mozilla.org/show_bug.cgi?id=1502526 No details of the toolchain in that. Do you really mean gcc-8.1 ? Looking at my local copy of the 8.4 BLFS book, that was on 8.2. Please can you confirm your running versions of: binutils gcc rustc and, if you are using clang (I guess you are, I eventually discovered that firefox uses it unless CC=gcc etc are specified), which version ? All I've seen on BLFS lists and my own builds re vpx is that recent system libvpx is not usable (firefox is stuck on mozilla's internal fork an older version). How does your mozconfig differ from what is in the *current* svn book for 67.0.4 ? The 8.4 book had firefox-65.0.1, *so_many* of the details have changed since then. Meanwhile, firefox-68 is expected at the start of next week and needs newer rust. I updated the book to rustc-1.35.0 this week, the svn book is using system llvm but that requires LLVM-8: For updating old systems with earlier versions of LLVM, I'm building 1.35.0 using the shipped LLVM it comes with, same instructions as for 1.32.0 in the 8.4 book (tested with late 68beta version on a couple of older systems). In general, 68 will require newer icu (64.2), libpng (1.6.37), nss (3.44.1) with matching nspr (so, 4.21 is known to work) and sqlite (>=3.28.0) if using the system versions, and cbindgen (>=0.8.7). If patching for system graphite2 and harfbuzz, >=1.3.13 and >=2.4.0. > No big deal of course, I'll upgrade entire system at next release, but I > want to understand why -FPIC. May I try to modify some configuration in > compilation? I tried to modify media/ffvpx/ffvpxcommon.mozbuild adding -fPIC > in CFLAGS but link compilains: "bad value". > > Some ideas? > > Thanks > > Riccardo Generally, upgrading the common graphical browsers (or their engines: webkitgtk, qtwebengine) when new versions fix vulnerabilities is a good idea - I know that the development book is often broken, so best to review the blfs-dev recent posts (in the archive if not subscribed) but to check the instructions in that book. ĸen -- This is magic for grown-ups; it has to be hard because we know there's no such thing as a free goblin. -- Pratchett, Stewart & Cohen - The Science of Discworld II -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
