Bug 222438

Summary:	"gcc -print-file-name" doesn't print an error for a bad library name
Product:	[Fedora] Fedora	Reporter:	Robert P. J. Day <rpjday>
Component:	gcc4	Assignee:	Jakub Jelinek <jakub>
Status:	CLOSED CANTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	6
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-01-13 07:38:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Robert P. J. Day 2007-01-12 15:30:12 UTC

$ gcc -print-file-name=<name>

where <name> is not a valid library name simply echoes the name back, rather
than printing an appropriate diagnostic:

$ gcc -print-file-name=libc.so
/usr/lib/gcc/i386-redhat-linux/4.1.1/../../../libc.so
$ gcc -print-file-name=libm.so
/usr/lib/gcc/i386-redhat-linux/4.1.1/../../../libm.so
$ gcc -print-file-name=jakub
jakub

That last response is less than truly informative.

Comment 1 Jakub Jelinek 2007-01-13 07:38:06 UTC

That's the standard behavior of that switch for more than a decade, changing
it would break many scripts.