Bug#363692: libgmp3-dev: Private header files are unusable.
Hello, * Steve M. Robbins [Thu, Apr 20, 2006 at 09:30:01PM -0400]: > Excellent news! I'm inclined to simply remove them again in order to > avoid more surprises like disappearing __gmp_rand(). Sounds reasonable to me. Laurent. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363692: libgmp3-dev: Private header files are unusable.
Hi Laurent, On Thu, Apr 20, 2006 at 02:45:19PM +0200, Laurent Fousse wrote: > I don't know about other packages who do or would like to use these > headers; mpfr don't need them anymore so you're free to deal with them > as you like from my point of view: either remove them altogether, or > add with the lacking files. Excellent news! I'm inclined to simply remove them again in order to avoid more surprises like disappearing __gmp_rand(). -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#363692: libgmp3-dev: Private header files are unusable.
Package: libgmp3-dev Version: 4.2.dfsg-1 Severity: minor Hello, I noticed from some mpfr build log[1] that the private header files for GMP installed in /usr/lib/gmp are not usable: we miss fib_table.h and mp_bases.h, for example (see gmp-impl.h). I know I've asked for those internal headers to be available for mpfr in the past, but I've talked with mpfr's developers again on this issue and the conclusion is that the speed benefit we can gain from having these headers in the build process is minor, and we can therefore do without (and it is cleaner anyway). I don't know about other packages who do or would like to use these headers; mpfr don't need them anymore so you're free to deal with them as you like from my point of view: either remove them altogether, or add with the lacking files. Regards, Laurent. [1] see e.g. http://buildd.debian.org/fetch.php?&pkg=mpfr&ver=2.2.0.dfsg.1-6&arch=arm&stamp=1145382420&file=log&as=raw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
