On Tue, Jul 29, 2014 at 6:39 PM, Richard Henderson <r...@redhat.com> wrote: > On 07/29/2014 06:11 AM, Uros Bizjak wrote: >> Perhaps even better solution for mainline would be to detect a recent >> enough linker and skip the workaround in that case? I guess that 2.25 >> will have this issue fixed? > > Certainly 2.25 will have this fixed. If you want to add a check for binutils > version number, I'm ok with that.
Unfortunately, checking for host tools version won't work, since host_makefile_frag is substituted earlier that substitution for host CC (and LD). I propose to add a ??? comment to the configure, such as: -- cut here -- Index: configure =================================================================== --- configure (revision 213081) +++ configure (working copy) @@ -3879,6 +3879,7 @@ host_makefile_frag="config/mh-mingw" ;; alpha*-*-linux*) + # ??? Remove for GNU ld version 2.25 and higher. host_makefile_frag="config/mh-alpha-linux" ;; hppa*-hp-hpux10*) Index: configure.ac =================================================================== --- configure.ac (revision 213081) +++ configure.ac (working copy) @@ -1178,6 +1178,7 @@ host_makefile_frag="config/mh-mingw" ;; alpha*-*-linux*) + # ??? Remove for GNU ld version 2.25 and higher. host_makefile_frag="config/mh-alpha-linux" ;; hppa*-hp-hpux10*) -- cut here -- and remove this fragment after binutils 2.25 is released. After the release, we can comment out referred line in configure, document the requirement for binutils >= 2.25 in install.texi and document the workaround, which will be to un-comment the relevant line in configure file. Uros.