Ryan Oliver wrote:
> LFS not affected in regards to the fact we can set any of
> md_startfile_prefix{,_1} or startfile_prefix_spec in the specs file and
> have it work because we DO use a standard specs file in the appropriate
> place.
I'll restate in clear terms. You're modifying/creating files under /tools
whilst inside the chroot. i.e. you have no clean separation.
> some unfair fud about the use of startfile_prefix_spec)
Fud? The *facts* haven't changed in years:
- it's undocumented in the GCC literature
- some GCC devs have expressed a desire to get rid of it
- it's affected by the -specs= bug
- hardly anyone on the planet outside *LFS derived projects actually use
it. In fact, its use in *LFS has actually _encouraged_ some folks to
use it. Ughh.
The only recent reference by a senior GCC dev I can find is here:
http://gcc.gnu.org/ml/gcc-patches/2008-06/msg00842.html
which confirms what we already know i.e. it was a prior attempt at solving
multilib issues that should have been removed when MULTILIB_OSDIRNAMES was
implemented.
> In your case wanting to keep using -specs you are probably better off
> setting
Sorry dude. You can't just blow back in here years after being MIA and
expect folks to listen to your idle speculation. Folks will take notice
when you have something concrete to offer i.e. well thought out, tested
and published for all to see.
Regards
Greg
--
http://www.diy-linux.org/
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
