severity 320425 grave
merge 320425 323506
thanks

On Thu, Aug 18, 2005 at 10:23:06PM +1000, Anibal Monsalve Salazar wrote:
> On Thu, Aug 18, 2005 at 07:12:08AM -0500, John Goerzen wrote:
> >On Thu, Aug 18, 2005 at 02:52:04PM +1000, Anibal Monsalve Salazar wrote:
> >>On Tue, Aug 16, 2005 at 10:40:10PM -0500, John Goerzen wrote:
> >>>collect2: ld returned 1 exit status

> >>Please see bug #323500.

> >Did you perhaps mean 320425?

> Sorry, it's my mistake. Yes, I meant 320425. I'm still waiting for
> a patch from upstream (or anybody else for that matter).

> >I looked at it, and it looked similar, but I couldn't tell for sure if
> >it was the same problem.  I don't really understand what's going on
> >here, and in any case, there's no solution noted in that bug.

> It's the same bug. And there is no patch yet.

The bug in question is that, in spite of trying to pass
--disable-optimized to ./configure, upstream's build scripts still set
OPTIMIZE_I386 which prevents enabling the C version of these functions,
and the source package appears to not have a build-dependency on an
assembler suitable for building the optimized x86 version.

Adding --with-arch=generic to the configure options when building on
i386 looks like it should be enough to fix this problem.

Please don't forget to change the package name for the C++ transition
when uploading, as libbeecrypt6 does export C++ interfaces.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to