[Debian-med-packaging] Bug#656755: libhmsbeagle FTBFS on everything except amd64

[Andreas Tille]

Hi Peter,

On Sat, Jan 21, 2012 at 03:00:25PM +0000, peter green wrote:
> Note: i'm not an expert on this package, just someone looking at
> build failures and filing bugs.

That's a really valuable job - thanks for doing so!
 
> It seems things are a little more complex than they first  appeared.
> In particular it seems libhmsbeagle has a specific "sse2 plugin"
> which can only be built with sse2 enabled and that is built even if
> --enable-sse=no is passed (which seems like a bug in the upstream
> build system to me). Therefore disabling -msse2 has caused the
> package to FTBFS everywhere except amd64.
> 
> For non pc architectures I would think the sse2 plugin should simply
> be disabled.

Do you have any hint how I could find this plugin which should be
disabled.  The problem is that I do not have any idea about this
library either.  I just need it as a dependency for other packages
(Debian package mrbayes needs to be build against the -dev package
and the Java library will be needed by the package in preparation
beast-mcmc).

Are you talking about libhmsbeagle/plugin/*.

A failed build log would probably be helpful.  I also have included
upstream whether they might be able to give any hint about this issue:

> For i386 the descision on what to do there requires knowlege of the
> internals of the software. If the software is capable of making
> sensible descisions about whether to use the sse2 plugin at runtime
> then the sse2 plugin (but NOT the rest of the package) should be
> built with -msse2 (this will probablly require adding an option to
> the buildscripts along the lines of "--enable-sse=ssepluginonly").
> If the software is NOT capable of making sensible descisions about
> whether to use the sse2 plugin at runtime then either it should
> simply be disabled on i386 or the ability to make sensible descsions
> about whether to use it at runtime should be added to the code.

Considering the fact that Tim (in CC) decided to not install the plugin
at all it might be a simple workaround to simply prevent building of the
plugin at all.

Moreover I just noticed that the -dev package is lacking static
libraries.  Hmmm, any hint how to tweak autoconf stuff to build these
as well (or should I ask on debian-mentors at l.d.o)?

Kind regards

       Andreas. 

-- 
http://fam-tille.de