Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 518650 - sys-libs/glibc-2.19-r1: static linking breaks getaddrinfo
Summary: sys-libs/glibc-2.19-r1: static linking breaks getaddrinfo
Status: RESOLVED DUPLICATE of bug 509748
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-31 09:18 UTC by kipeta
Modified: 2014-08-10 12:36 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
test app (getaddrinfo.c,561 bytes, text/x-csrc)
2014-08-10 04:22 UTC, SpanKY
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kipeta 2014-07-31 09:18:35 UTC
After I upgraded glibc to the latest stable on my x86_64 (AMD64) system and re-compiled the latest stable busybox (1.21.0), the busybox apps like ping, wget, etc... started to fail on DNS lookup.



Reproducible: Always

Steps to Reproduce:
1. upgrade glibc to 2.19-r1
2. re-compile sys-apps/busybox-1.21.0
3. ping some host
Actual Results:  
ping: bad address 'hp'

Expected Results:  
PING hp (10.0.1.100): 56 data bytes
64 bytes from 10.0.1.100: seq=0 ttl=64 time=0.149 ms
...

The problem didn't happen before the busybox was re-compiled against glibc-2.19-r1. I managed to revert glibc back to 2.17, re-compiled busybox and everything was OK.
Comment 1 SpanKY gentoo-dev 2014-08-10 04:22:21 UTC
Created attachment 382614 [details]
test app

$ gcc -static getaddrinfo.c && ./a.out gentoo.org
/tmp/ccN7FeZG.o: In function `main':
.../resolv.c:22: warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
bad address 'gentoo.org'

glibc-2.17 & glibc-2.18 seem to behave correctly
Comment 2 SpanKY gentoo-dev 2014-08-10 12:36:33 UTC
same underlying problem as bug 509748 afaict

*** This bug has been marked as a duplicate of bug 509748 ***