diff options
| author | 卜部昌平 <shyouhei@ruby-lang.org> | 2020-08-21 16:01:46 +0900 |
|---|---|---|
| committer | 卜部昌平 <shyouhei@ruby-lang.org> | 2020-08-21 16:01:46 +0900 |
| commit | 3eb76e747e33d1a4439d2e83c53b538b6c536ec3 (patch) | |
| tree | 5d86c4f235cb816f0977a156432d96d5ef55b4bf | |
| parent | 73b6bc579063fb03bd566cbac5ac76d18e481dc6 (diff) | |
configure.ac: try GCC-provided ld
In case of cross-compilation, GCC might provide its own linker. Its
behaviour seems slightly different from that of gcc(1). This is not a
big deal for normal situations, but the difference can cause libtool to
go mad.
We ship bundled libffi for windows users, and libffi uses libtool. If
we use cross-compiler version of gcc instead of its ld conterpart, we
fail to compile fiddle. That should not be what we want.
| -rw-r--r-- | configure.ac | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/configure.ac b/configure.ac index 9531ac99d1..484849599d 100644 --- a/configure.ac +++ b/configure.ac @@ -135,7 +135,7 @@ AS_CASE(["/${rb_CC} "], ], [*gcc*], [ # Dito for GCC. - : ${LD:="${CC}"} + AC_CHECK_TOOL([LD], [`echo "${rb_CC}" | sed s/gcc/ld/`]) AC_CHECK_TOOL([AR], [`echo "${rb_CC}" | sed s/gcc/gcc-ar/`]) AC_CHECK_TOOL([CXX], [`echo "${rb_CC}" | sed s/gcc/g++/`]) AC_CHECK_TOOL([NM], [`echo "${rb_CC}" | sed s/gcc/gcc-nm/`]) |