Bug 750003

Summary:	g++ not finding proper libraries after an update
Product:	[Fedora] Fedora	Reporter:	Trever Adams <trever>
Component:	gcc	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	jakub, mohan43u
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-30 04:40:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Trever Adams 2011-10-29 20:16:36 UTC

Description of problem:
After updating to the gcc-4.6.2-1 and gcc-c++-4.6.2.-1 I get the following whenever g++ is used:
g++: error: /usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/crti.o: No such file or directory
g++: error: /usr/lib/gcc/x86_64-redhat-linux/4.6.1/crtbeginS.o: No such file or directory
g++: error: /usr/lib/gcc/x86_64-redhat-linux/4.6.1/crtendS.o: No such file or directory
g++: error: /usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/crtn.o: No such file or directory

I imagine something either wasn't compiled correctly, or there is a setting somewhere that is pointing thing to the wrong directory!

Version-Release number of selected component (if applicable):
gcc-4.6.2-1.fc16.x86_64
libgcc-4.6.2-1.fc16.x86_64
gcc-c++-4.6.2-1.fc16.x86_64

Comment 1 Jakub Jelinek 2011-10-29 20:45:57 UTC

Are you sure you have gcc-g++-4.6.2-1.fc16 installed and that g++ is /usr/bin/g++?
That binary definitely doesn't have the 4.6.1 string anywhere, wouldn't be looking for anything in /usr/lib/gcc/x86_64-redhat-linux/4.6.1 based paths
but /usr/lib/gcc/x86_64-redhat-linux/4.6.2 based ones.

Comment 2 Trever Adams 2011-10-29 22:19:47 UTC

# which g++
/usr/bin/g++
# rpm -q gcc-c++
gcc-c++-4.6.2-1.fc16.x86_64

I just removed it and I am going to try and reinstall it. See if something went south in the upgrade.

Comment 3 Trever Adams 2011-10-29 22:36:42 UTC

It appears it may have been something strange in the configure script in question. I did a clean restart of the code base and it seems to be working. I am sorry for the false report.

Comment 4 Mohan R 2011-10-30 04:40:50 UTC

Closing This bug. Thanks for reporting.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers