On 19 November 2006 16:07, Gerald Pfeifer wrote: > On Wed, 4 Oct 2006, Daniel Jacobowitz wrote: >>>> "This file can be found in the same directory that >>>> contains cc1 (run gcc -print-prog-name=cc1 to find it)." >>> I think that indicates someone trying to be overly clever when they >>> configured your gcc package. Normally libdir and libexecdir point to the >>> same dir. What output do you see from "gcc -v"? >> Not any more. The default changed some time ago. Some distributors >> configure them to the same location. >> >> Jeff, for background, up until a few releases ago cc1 and specs would >> always be in the same directory. > > Daniel, Dave, if one of you could have a look at > http://gcc.gnu.org/faq.html#rpath > and update that, that would be great! If you prefer, just provide any > edits/changes to me, and I'll take care of updating that web page, markup > and committing. > > Thanks, > > Gerald
I'm not quite sure how we tell people where to find the right default directory for it anymore. Did libgcc move to libdir from libexecdir as well? Otherwise I can't think of any file that's guaranteed to be there to look for with -print-file-name. Modulo that minor difficulty, here's a proposed re-wording: <p>However, if you feel you really need such an option to be passed automatically to the linker, you can create a GCC specs file and add it there. The <a href="http://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html#Spec-Files"specs</a> file is the mechanism used by gcc to control which options are passed to which of the sub-stages of compiling, assembling and linking; GCC normally operates according to a built-in set of specs, but these defaults can be overridden by providing an external specs file. This file can either be passed to the compiler by supplying the <code>--specs=</code> option, or can be placed in the same directory that contains ???????????????? (run gcc -print-file-name=??????????????? to find it), where gcc will locate and use it automatically every time it runs. You can then add linker flags such as -R or -rpath, depending on platform and linker, to the *link or *lib specs. cheers, DaveK -- Can't think of a witty .sigline today....
