Bug#310226: [Pkg-octave-devel] Bug#310226: octave2.9: FTBFS: linking a shared lib to a static lib fails.

2005-06-09 Thread Kurt Roeckx
On Thu, Jun 09, 2005 at 07:52:02PM +0200, Falk Hueffner wrote: > > As README.Debian explains, glpk is not reentrant, so there cannot be a > shared library. So one could either try to fix that (which is probably > difficult), or build a nonshared PIC library. Is that also possible > with libtool?

Bug#310226: [Pkg-octave-devel] Bug#310226: octave2.9: FTBFS: linking a shared lib to a static lib fails.

2005-06-09 Thread Falk Hueffner
Rafael Laboissiere <[EMAIL PROTECTED]> writes: > * Kurt Roeckx <[EMAIL PROTECTED]> [2005-05-22 16:23]: > >> Your package is failing to build on a few arches (atleast hppa >> and amd64) because when you're creating the shared lib you're >> linking to a static version. > > This is actually an upstre

Bug#310226: [Pkg-octave-devel] Bug#310226: octave2.9: FTBFS: linking a shared lib to a static lib fails.

2005-05-24 Thread Rafael Laboissiere
[ This is a reply to a bug report filled against the octave2.9 Debian package, which depends on glpk. For further information, please see http://bugs.debian.org/310226 ] * Kurt Roeckx <[EMAIL PROTECTED]> [2005-05-22 16:23]: > Package: octave2.9 > Version: 2.9.2-2 > Severity: serious > > Hi,

Bug#310226: octave2.9: FTBFS: linking a shared lib to a static lib fails.

2005-05-22 Thread Kurt Roeckx
Package: octave2.9 Version: 2.9.2-2 Severity: serious Hi, Your package is failing to build on a few arches (atleast hppa and amd64) because when you're creating the shared lib you're linking to a static version. Static version should be compiled without -fPIC while shared version must be compile