http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52122
tim.vanholder at anubex dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tim.vanholder at anubex dot
| |com
--- Comment #6 from tim.vanholder at anubex dot com 2012-08-08 21:10:24 UTC ---
Daniel, your patch modifies the configure scripts, which are generated files -
so the effect would be temporary at best.
I don't have a gcc checkout handy (nor high-speed internet), so I can't check
this myself right now, but:
- If the configure.ac scripts use autoconf's own AC_LN_S macro, then a bug
report should be submitted to the autoconf maintainers, and a GCC_LN_S macro
would probably have to be created with the fix in place (to avoid depending
on an upstream fix). Of course if autoconf uses all this internally, an
upstream fix may be the only avenue.
- If a gcc-specific macro is already being used (grep for "ln" or "cp -p" in
the top-level "config" subdir (*.m4) to get an idea), then just put the
fix(es) there
Based on the variables seen in your patch it's probably going to be both
(as_ln_s is an autoshell (part of autoconf) variable, gcc_cv_prog_LN_S sounds
like a GCC-specific one).
Once the macros are added/fixed, whatever script/command regenerates all the
gcc configure scripts will propagate those changes automatically (and they will
stay present even if a user regenerates a configure script).
Note: I think I see an LN="cp -p" remain untouched in your patch - surely if
the "ln -s" replacement needs to support directories, so does the one for plain
ln?
