Il 20/11/2013 09:47, Torbjorn Granlund ha scritto:
> Christian Rössel writes:
>
> assuming that you are using libtool, just configure twice, with
> --enable-static --disable-shared' and '--disable-static
> --enable-shared' respectively. Maybe this is not the solution you are
> looking for
Torbjörn,
On 11/13/2013 06:45 PM, Torbjorn Granlund wrote:
We in the GMP project would like to have "make check" run through our
testsuite for both the static and shared libs (when both are built).
We haven't been able to achive this. Please help.
assuming that you are using libtool, just co
Christian Rössel writes:
assuming that you are using libtool, just configure twice, with
--enable-static --disable-shared' and '--disable-static
--enable-shared' respectively. Maybe this is not the solution you are
looking for, but it is an easy workaround that is trivial to automate;
a
Thien-Thi Nguyen writes:
() Torbjorn Granlund
() Wed, 13 Nov 2013 18:45:30 +0100
We in the GMP project would like to have "make check" run through our
testsuite for both the static and shared libs (when both are built).
This is only necessary if there are significant differ
() Torbjorn Granlund
() Wed, 13 Nov 2013 18:45:30 +0100
We in the GMP project would like to have "make check" run through our
testsuite for both the static and shared libs (when both are built).
This is only necessary if there are significant differences (in
user-visible behavior) between
We in the GMP project would like to have "make check" run through our
testsuite for both the static and shared libs (when both are built).
We haven't been able to achive this. Please help.
Torbjörn
