[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libtasn1 ./configure gets capabilities mixed up of cc and ld

From: John Scott
Subject: libtasn1 ./configure gets capabilities mixed up of cc and ld
Date: Fri, 10 Jul 2020 10:32:40 -0400


I'm not able to build libtasn1 with the Tiny C Compiler
(git://, and I suspect the configure script is to blame.

When just building libtasn1 normally with it, it recognizes tcc is not gcc but 
checking for non-GNU ld... /bin/ld
checking if the linker (/bin/ld) is GNU ld... yes
checking whether the /home/john/tiny-tcc-crypto/prefix/bin/tcc linker (/bin/ld 
-m elf_x86_64) supports shared libraries... yes
checking if LD -Wl,--version-script works... no

So it noticed that --version-script doesn't work, but at build-time ld isn't 
invoked at all but instead tcc is used, which still doesn't support -version-
script with a single hyphen:

libtool: link:  /home/john/tiny-tcc-crypto/prefix/bin/tcc -shared  -fPIC -DPIC  
.libs/ASN1.o .libs/coding.o .libs/decoding.o .libs/element.o .libs/errors.o 
.libs/gstr.o .libs/parser_aux.o .libs/structure.o .libs/version.o  -Wl,--
whole-archive gl/.libs/libgnu.a -Wl,--no-whole-archive  -lc  -g   -Wl,-soname 
-Wl, -Wl,-version-script -Wl,.libs/libtasn1.ver -o .libs/
tcc: error: unsupported linker option '-version-script'

It also seems like a bad assumption that the /bin/ld it found was the same 
linker that would be invoked by the C compiler. ./configure --help doesn't show 
any ways I can override this. Even with --without-gnu-ld the configure script 
still finds that there is a GNU ld and nothing changes.

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]