Le mardi 13 mars 2012 13:15:38, vous avez écrit : > Package: tcc > Version: 0.9.26~git20120104.83d57c0-4 > Severity: wishlist > Tags: upstream patch > > tcc should support the -rpath option, as it is generated by libtool > (e.g. to be able to build the MPFR tests with shared libraries > enabled). The attached patch does that (please review it, as I am > not familiar with the tcc code). I don't understand. How can libtool generate -rpath when even gcc doesn't support it? It's a linker option, not a compiler option. Although tcc can link files itself, it is not advertised as a linker.
There is support for -Wl,-rpath so the code is clearly implemented. If -rpath option does not exist it must be for a good reason. > > The patch itself seems to work on my x86_64 machine (though running > the test is another problem...). At least its behavior is equivalent > to -Wl,-rpath. > > Note that it does not free the memory explicitly when the program > ends. I don't think this is a problem in practice, except when > testing with tools like valgrind. You can free just after tcc_set_linker as tcc_set_linker does not reuse the string.
signature.asc
Description: This is a digitally signed message part.
