Bug 58882

Summary:	glibc linking inconsistancy from build stage to installation
Product:	Gentoo Linux	Reporter:	augury@vampares.org <Augury>
Component:	[OLD] Unspecified	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED NEEDINFO
Severity:	trivial
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description augury@vampares.org 2004-07-30 04:20:53 UTC

when libc of glibc-2.3.4 is built staticly as well as dynamicly or in pic the standard modules is built as libc.so with a link to it libc.so.6.
the standard and rational practice is to point to the module version with the modules default base name, rather than arbitrarily convene on one.
the libc.so is designated specifically when being compiled against.
the versionless libc.so is used as a config file by gcc for static or shared instances.
the layover assumes traversal of the link and requires the manual implimentation as the real libc is clobbered if does make the career move and a funny link is left in its place.

Reproducible: Couldn't Reproduce
Steps to Reproduce:
1.
2.
3.

Actual Results:  
 

Expected Results:

Comment 1 Travis Tilley (RETIRED) gentoo-dev

2004-08-17 20:49:05 UTC

ayanami xorg-x11 # file /lib64/libc.so.6
/lib64/libc.so.6: symbolic link to `libc-2.3.4.so'

i cant tell what you're trying to say.