Bug 638020

Summary:	sys-libs/glibc-2.25-r9 - ?
Product:	Gentoo Linux	Reporter:	rjgleits
Component:	Current packages	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED NEEDINFO
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge --info

Description rjgleits 2017-11-18 14:13:42 UTC

During the lib_check test in /usr/lib64/portage/pythonx.y/install-qa-check.d/80libraries, an error "QA Notice: Missing gen_usr_ldscript for libm-2.25" happens and the emerge is aborted. There is in fact an ldscript file in the image/usr/lib64 directory, but it is named libm.so. Since there is a libm-2.25.a static library, the lib_check function thinks that the ldscript file name should be libm-2.26.so. 
The reason I think that this problem is with glibc rather than portage is that none of the other library files in the image/usr/lib64 have this problem. 
Another possible cause may be that there is a link file in the 2.25-r8 /usr/lib64 directory named libm-2.25.so linking to /lib64/libm-2.25.so. This is missing in the r9 image and the QA error is not thrown if the test is applied to the installed files in /usr/lib64.
I am using the multilib option. but I don't recall that changing recently enough to cause this problem. I think I see how I can patch the ebuild so that it works correctly (assuming r8 was correct), which would be to add the link file that is missing. Since that is currently functioning without problem, I don't think it should cause a failure of the system. I didn't research why the link file disappeared between r8 and r9.

That's about it.

Best Wishes,

Bob Gleitsmann

Comment 1 Andreas K. Hüttel archtester

2017-11-18 14:27:32 UTC

Hi Bob, to be able do anything with this we need the full build log and the output of "emerge --info" ...

Comment 2 rjgleits 2017-11-18 18:21:30 UTC

Created attachment 504656 [details]
emerge --info

Comment 3 rjgleits 2017-11-18 19:05:48 UTC

Attachment of build.log is not working. I tried gzipping it, still not working.

Comment 4 Benda Xu gentoo-dev

2017-11-29 11:02:44 UTC

(In reply to rjgleits from comment #3)
> Attachment of build.log is not working. I tried gzipping it, still not
> working.

Could you please be more specific on "not working"?  Is it because the file is too large?  How large is it?