From: Philippe W. <phi...@sk...> - 2024-12-23 09:53:21
|
On Sun, 2024-12-22 at 21:46 +0100, Mark Wielaard wrote: > Hi Philippe, > > On Sun, Dec 22, 2024 at 12:29:34PM +0100, Philippe Waroquiers via Valgrind-developers wrote: > > The below change causes a build failure on the gcc110 compile farm > > > > valgrind revision: valgrind-3.25.0.GIT-544d41e525-20241221 > > C compiler: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44) > > GDB: GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7 > > Assembler: GNU assembler version 2.27-44.base.el7_9.1 > > C library: GNU C Library (GNU libc) stable release version 2.17 > > uname -mrs: Linux 3.10.0-1160.105.1.el7.ppc64 ppc64 > > Vendor version: CentOS Linux 7 (AltArch) > > [...] > > /usr/bin/ld: unrecognized option '--no-warn-execstack' > > I saw Paul already added a configure check to see if the linker > supports --no-warn-execstack. Thanks Paul. > > But this is a really old system. Do we really want to keep supporting > gcc 4.8 and binutils 2.27? Both are 9 years old. CentOS7 and CentOS8 > stopped doing updates earlier this year. It would seem reasonable to upgrade gcc110 but I do not know what is the upgrade policy of the compile farm. If we stop testing on gcc110, do we have another powerpc where to do the nightly builds ? Thanks Philippe |