Ryan Oliver wrote: > STARTFILE_PREFIX_SPEC is unpalatable to some for whatever reason, yet it > still exists in the gcc code to provide the only mechanism to override > the search path used for finding startfiles when cross-compiling (see > gcc.c line 6332, read the code and comments) > > You should however be able to use/override > STANDARD_STARTFILE_PREFIX_1=/tools/lib (continue nullifying > STANDARD_STARTFILE_PREFIX_2) instead if you are doing a native build > (which you are) and find STARTFILE_PREFIX_SPEC objectionable (for > whatever reason). > > Note: startfile_prefix_spec and standard_startfile_prefix* ARE expanded > by the multilib spec out of the box. > Strike that... you'd have to override that when adjusting the toolchain with either *startfile_prefix_spec or *md_startfile_prefix anyway...
If STARTFILE_PREFIX_SPEC is objectionable for a native compiler, use MD_STARTFILE_PREFIX instead for overriding STANDARD_STARTFILE_PREFIX. [R] -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
