A quick question about -no-canonical-prefixes...

By default, gcc calls realpath() on prefixes generated relative to
argv[0] in the gcc driver.  If gcc is held as a "symlink farm" the
realpath() makes it fail (absent a lot of messy -B, -L, -isytem and so
on).  It complains about not finding cc1 or cc1plus in libexec.

-no-canonical-prefixes turns off realpath() to make gcc work cleanly
when stored this way.

Does anyone know a reason why -no-canonical-prefixes could not become
the gcc default?  Are there gcc configurations that must have the
realpath()?  The flag is benign on normally laid out gcc
installations.

If it did become the default case, would adding a symmetrical
-canonical-prefixes to turn realpath() back on be worthwhile?

Thanks.

-- 
Google UK Limited | Registered Office: Belgrave House, 76 Buckingham
Palace Road, London SW1W 9TQ | Registered in England Number: 3977902

Reply via email to