[Debian-med-packaging] Bug#656755: Help with architecture not supporting SSE (Was: Bug#656755: libhmsbeagle FTBFS on everything except amd64)
Andreas Tille
andreas at an3as.eu
Wed Jan 25 07:23:26 UTC 2012
On Wed, Jan 25, 2012 at 01:37:59AM +0000, peter green wrote:
> Andreas Tille wrote:
> > Hi,
> >
> > I have to admit that I do not have any experience with SSE issues. Any
> > advise what to do in cases like this (see build logs linked below)?
> From looking at the build logs it looks like it is trying to build
> a "plain CPU plugin" and a "CPU with SSE plugin", presumablly the
> "plugins" are different peices of code that can be used to perform
> the core computations. It looks like you will need to modify the
> build system so that it is possible to disable building the "CPU
> with SSE plugin".
Yes, that's also what I guessed from the logs and the code.
> But thats only my gut feeling from looking at the build logs and
> package discriptions, this really needs to be confirmed by someone
> who actually knows the internals of the package in question.
Upstream was in CC in all these mails. I'm urgently hoping for some
answer.
> If you can't handle this then I don't think you are competant to be
> maintaining this package in debian. Knowing how the components of
> the software they are packaging fit together and how to fix the
> build systems to produce packages suitable for debian is IMO a
> pretty key part of a maintainers job.
While I really agree to this statement I think there is few chance that
somebody else will step in. We are just needing to maintain this as a
predependency for two important packages of the Debian Med team. As you
know RFP bugs are really rarely resolved and thus we try to drain the
competence to handle this from upstream which is IMHO the fallback for
maintainers in any case.
Kind regards
Andreas.
--
http://fam-tille.de
More information about the Debian-med-packaging
mailing list