Planning for Cross-LFS/Multi-Architecture 7.x Release

Ryan.Oliver at pha.com.au Ryan.Oliver at pha.com.au
Tue Apr 19 20:59:07 PDT 2005






TheOldFellow wrote:
<SNIP>
>
>This separation means that there is no need to edit the specfiles or
>interfere with the normal operation of the linker (as is done in the
>current Pure-LFS derived LFS).

This is not entirely correct, we still need to edit the specs in
what was ch6 during the "lock-in"

Currently the scripts (in svn) look to see if a specs file is present
in the usual location, if not, they create one (to the standard
location) and edit it.

If a specs file exists in the standard location, it automatically gets
used, overriding the builtin specs.
This fixes the gcc4 issue without resorting to extra gcc switches.

If you have to go back due to a stuff up, it is as simple as
rm `${TARGET}-gcc --print-file-name specs`

 Regards
[R]




More information about the lfs-dev mailing list