On 18.05.2016 16:32, Elan Ruusamäe wrote:
On 18.05.2016 14:33, Elan Ruusamäe wrote:
On 18.05.2016 14:18, arekm wrote:
commit ee4a0bb9cd9a8e7f552c9948963a69c61865845c
Author: Arkadiusz Miśkiewicz<ar...@maven.pl>
Date: Wed May 18 13:16:40 2016 +0200
- rel 4; more upstream git branch updates
any ideas how or why glibc update caused varnish compile failures (it
compiles it's .vcl files to .c -> .so)
# service varnish checkconfig
Checking Varnish HTTP accelerator
configuration...........................................................................................................................................................................................................[
FAIL ]
Command failed with error code 106
Message from C-compiler:
/usr/bin/ld:
/usr/lib64/gcc/x86_64-pld-linux/5.2.0/../../../../lib64/crti.o:
unrecognized relocation (0x2a) in section `.init'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Running C-compiler failed, exit 1
VCL compilation failed
Message from C-compiler:
/usr/bin/ld:
/usr/lib64/gcc/x86_64-pld-linux/5.2.0/../../../../lib64/crti.o:
unrecognized relocation (0x2a) in section `.init'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
Running C-compiler failed, exit 1
seems simple compilation fails now:
# echo 'int main() {}' > a.c
# gcc a.c -o test
/usr/bin/ld:
/usr/lib64/gcc/x86_64-pld-linux/4.9.3/../../../../lib64/crti.o:
unrecognized relocation (0x2a) in section `.init'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
happened after packages update:
Wed May 18 09:57:49 2016 tzdata-2016d-1.noarch
Wed May 18 09:59:02 2016 glibc-2.23-2.x86_64
Wed May 18 09:59:02 2016 glibc-devel-2.23-2.x86_64
Wed May 18 09:59:02 2016 glibc-devel-utils-2.23-2.x86_64
Wed May 18 09:59:02 2016 glibc-headers-2.23-2.x86_64
Wed May 18 09:59:02 2016 glibc-libcrypt-2.23-2.x86_64
Wed May 18 09:59:02 2016 glibc-misc-2.23-2.x86_64
Wed May 18 09:59:02 2016 iconv-2.23-2.x86_64
Wed May 18 09:59:02 2016 ldconfig-2.23-2.x86_64
other relevant packages:
# pkgbytime gcc
Mon Sep 14 17:48:10 2015 gcc-4.9.3-1.x86_64
Mon Sep 14 17:48:10 2015 libgcc-4.9.3-1.x86_64
# pkgbytime binutils
Mon Sep 14 17:48:10 2015 binutils-2.25.51.0.2-1.x86_64
Mon Sep 14 17:48:10 2015 binutils-libs-2.25.51.0.2-1.x86_64
previous glibc version was:
# rpm -q --blink glibc
glibc-2.23-2.x86_64
glibc-2.23-2.x86_64.rpm
<= glibc-2.23-1.x86_64.rpm
it's broken with glibc-2.23-4.x86_64.rpm as well, but not with
glibc-2.23-1.x86_64.rpm
maybe add conflicts: gcc < 6:5.0 to glibc package so such breakage won't
bring down another system.
but i'd like to know what caused this. it makes no sense.
--
glen
_______________________________________________
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
