Re: [packages/glibc] - rel 4; more upstream git branch updates
On 18.05.2016 14:33, Elan Ruusamäe wrote:
On 18.05.2016 14:18, arekm wrote:
commit ee4a0bb9cd9a8e7f552c9948963a69c61865845c
Author: Arkadiusz Miśkiewicz
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
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/glibc] - rel 4; more upstream git branch updates
On Wednesday 18 of May 2016, Jacek Konieczny wrote: > Or full upstream patches, with their commit messages. The > 'glibc-git.patch' with 'updated from upstream' logs is not much more > useful than a random binary blob. Actually glibc-git.patch contains very detailed change log inside of it. But I understand what you mean. > Jacek -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/glibc] - rel 4; more upstream git branch updates
On 2016-05-18 14:35, Elan Ruusamäe wrote: On 18.05.2016 14:54, Arkadiusz Miśkiewicz wrote: On Wednesday 18 of May 2016, Elan Ruusamäe wrote: On 18.05.2016 14:18, arekm wrote: commit ee4a0bb9cd9a8e7f552c9948963a69c61865845c Author: Arkadiusz Miśkiewicz Date: Wed May 18 13:16:40 2016 +0200 - rel 4; more upstream git branch updates glibc-git.patch | 60944 -- glibc.spec | 3 +- why keep this git.patch in our git, why not upload to distfiles? it's not like it's diff of .patch is something useful to look at. Maybe not for you but I was ofter doing git diff and git log on patch files like this to see what has changed etc. "log" seems to be mostly just "updated from upstream". https://github.com/pld-linux/glibc/commits/master/glibc-git.patch I hate those 'git patches' and 'updated from upstream' logs. That gives no version information. I would prefer to see some snapshot / upstream revision number, which I could use to check actual changes upstream. Or full upstream patches, with their commit messages. The 'glibc-git.patch' with 'updated from upstream' logs is not much more useful than a random binary blob. Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/glibc] - rel 4; more upstream git branch updates
On Wednesday 18 of May 2016, Elan Ruusamäe wrote: > On 18.05.2016 14:54, Arkadiusz Miśkiewicz wrote: > > On Wednesday 18 of May 2016, Elan Ruusamäe wrote: > >> On 18.05.2016 14:18, arekm wrote: > >>> commit ee4a0bb9cd9a8e7f552c9948963a69c61865845c > >>> Author: Arkadiusz Miśkiewicz > >>> Date: Wed May 18 13:16:40 2016 +0200 > >>> > >>> - rel 4; more upstream git branch updates > >>> > >>>glibc-git.patch | 60944 > >>>-- glibc.spec > >>> > >>>| 3 +- > >> > >> why keep this git.patch in our git, why not upload to distfiles? > >> it's not like it's diff of .patch is something useful to look at. > > > > Maybe not for you but I was ofter doing git diff and git log on patch > > files like this to see what has changed etc. > > "log" seems to be mostly just "updated from upstream". > > https://github.com/pld-linux/glibc/commits/master/glibc-git.patch use "log -p" -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/glibc] - rel 4; more upstream git branch updates
On 18.05.2016 14:54, Arkadiusz Miśkiewicz wrote: On Wednesday 18 of May 2016, Elan Ruusamäe wrote: On 18.05.2016 14:18, arekm wrote: commit ee4a0bb9cd9a8e7f552c9948963a69c61865845c Author: Arkadiusz Miśkiewicz Date: Wed May 18 13:16:40 2016 +0200 - rel 4; more upstream git branch updates glibc-git.patch | 60944 -- glibc.spec | 3 +- why keep this git.patch in our git, why not upload to distfiles? it's not like it's diff of .patch is something useful to look at. Maybe not for you but I was ofter doing git diff and git log on patch files like this to see what has changed etc. "log" seems to be mostly just "updated from upstream". https://github.com/pld-linux/glibc/commits/master/glibc-git.patch -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/glibc] - rel 4; more upstream git branch updates
On Wednesday 18 of May 2016, Elan Ruusamäe wrote: > On 18.05.2016 14:18, arekm wrote: > > commit ee4a0bb9cd9a8e7f552c9948963a69c61865845c > > Author: Arkadiusz Miśkiewicz > > Date: Wed May 18 13:16:40 2016 +0200 > > > > - rel 4; more upstream git branch updates > > > > glibc-git.patch | 60944 > > -- glibc.spec > > | 3 +- > > why keep this git.patch in our git, why not upload to distfiles? > it's not like it's diff of .patch is something useful to look at. Maybe not for you but I was ofter doing git diff and git log on patch files like this to see what has changed etc. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: [packages/glibc] - rel 4; more upstream git branch updates
On 18.05.2016 14:18, arekm wrote: commit ee4a0bb9cd9a8e7f552c9948963a69c61865845c Author: Arkadiusz Miśkiewicz Date: Wed May 18 13:16:40 2016 +0200 - rel 4; more upstream git branch updates glibc-git.patch | 60944 -- glibc.spec | 3 +- why keep this git.patch in our git, why not upload to distfiles? it's not like it's diff of .patch is something useful to look at. -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
