On 2015-05-22 07:52:38 +0300, Sergey Korshunoff wrote:
I wonder whether something can be improved on the tcc side
The problem is that the MPFR library used at run time is not
../src/.libs/libmpfr.so but the one installed on the system.
What the difference between gcc and tcc in this case?
On 2015-05-22 10:51:47 +0200, Vincent Lefevre wrote:
With gcc, the run path is used with:
-Wl,-rpath -Wl,/home/vlefevre/software/mpfr/src/.libs
So, I assume that this is only a libtool bug, as libtool should generate
that too (this seems to work when I add that manually).
I've submitted
I wonder whether something can be improved on the tcc side
The problem is that the MPFR library used at run time is not
../src/.libs/libmpfr.so but the one installed on the system.
What the difference between gcc and tcc in this case? Why exe produced
by gcc use ./src/.libs/libmpfr.so and exe
I've reported the following problem for libtool 2.4.6:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20622
but I wonder whether something can be improved on the tcc side
(except by using static linking, which works).
When I build GNU MPFR with CC=tcc LD=tcc and do make check,
I get things
