Jeremy Huntwork wrote: > There is a bug open to remove this feature from gcc. But, it is a year > old now and still open. > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19353
Not exactly. That bug report is about startfile_prefix_spec being a faulty spec. It coincidentally highlighted the fact that GCC devs want it removed. > I would at this time like to open this up to comments or suggestions > before I apply the changes to trunk. If there is a major reason why we > *shouldn't* use this feature of GCC, it should be brought up now. It's there in the current stable book and doing the job. Putting it back in unstable now would definitely be better than what you currently have. Personally, I don't believe in it and will never use it because: - the spec is faulty. It doesn't work when placed into an external file for use by "gcc -specs=..." (luckily LFS is not using it externally). Every other spec I've tried works properly when placed externally. (maybe someone can fix this bug in gcc.c ?) - the spec has been slated for removal by GCC devs. When that will happen (if ever) is anyone's guess. - nobody else in the entire world uses this spec. Google for it and see. - the way it's currently used by LFS is an abuse. This thing is for *startfiles*, yet LFS uses it to find libs also. Why do you think the extra libgcc_s.so symlink became necessary? - I do not buy into the argument that it should be used because CLFS uses it. Quite frankly, IMHO CLFS is bizarre.. All the sane cross toolchain build recipes available today do not resort to such hackery. The sane ones all use `--with-sysroot'. But I'm getting off-topic now so I'll save this for another forum/discussion. > We'll also create a hard link to its counterpart in Believe it or not, I've had reports from folks who place /tools on a separate partition. It'd be more robust if you used a symlink instead. 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
