I completely agree with you, in my shell, I was using “export LD=gcc”
Do you think that caused the problem?
On Dec 30, 2022 17:02 +0900, Bruno Haible <bruno@clisp.org>, wrote:
vikas sharma wrote:
Thank you for your quick response. Here is the output.
Comparing your output with mine, here are the most worrisome
differences:
@@ -370,5 +367,5 @@
# Whether we are building with GNU ld or not.
-with_gnu_ld="yes"
+with_gnu_ld="no"
# Flag that allows shared libraries with undefined symbols to be built.
If libtool determines that you are not using GNU ld, something is seriously
wrong.
@@ -306,5 +306,5 @@
# The linker used to build libraries.
-LD="/usr/bin/ld -m elf_x86_64"
+LD="gcc -m elf_x86_64"
# How to create reloadable object files.
Now this is completely bogus, since gcc does not support this option:
$ gcc -m elf_x86_64 hello.c
gcc: error: unrecognized command-line option ‘-m’
To me it looks like you specified a linker named 'gcc' (either through
some command-line variable, environment variable, or option). That cannot
work and caused the other problem.
Bruno