Package: g++-3.3
Version: 1:3.3.2-4
Severity: normal
Hi there! Thank you so much for the Debian toolchain!
I use Crypto++ v5.0 [1], and I've noticed that the "generate a random
RSA key pair" function either seg faults or goes into an infinite loop.
I've learned that turning optimization off wit
LAST_UPDATED: Sun Nov 16 11:24:54 UTC 2003
Native configuration is arm-unknown-linux-gnu
=== libffi tests ===
Running target unix
FAIL: libffi.call/closure_fn0.c (test for excess errors)
WARNING: libffi.call/closure_fn0.c compilation failed to produce executable
FAIL: libffi.cal
On Tue, Nov 18, 2003 at 09:42:24AM -0500, Clint Adams wrote:
> On Mon, Nov 17, 2003 at 08:56:05PM +0100, Matthias Klose wrote:
> > why is it annoying? it just works.
>
> It just works the opposite of the way I want it to work.
> It also confuses the hell out of users who just want to compile
> som
On Mon, Nov 17, 2003 at 08:56:05PM +0100, Matthias Klose wrote:
> why is it annoying? it just works.
It just works the opposite of the way I want it to work.
It also confuses the hell out of users who just want to compile
something.
> Yes, but sparc32-jailing builds is both non-obvious, tedious a
You'll be happy to know that the critical failures are fixed in
gcc-snapshot on ia64. We still have a very few minor threshhold
errors, as on every platform. But ia64 is in the same category as the
other arches for gcc-3.4, it appears.
Will try arm and m68k. Be prepared to wait
Take care,
Hello
On Sun, Nov 16, 2003 at 12:54:00PM +0100, Matthias Klose wrote:
> Daniel Bayer writes:
> > I get a SIGBUS when I try to profile something:
> > | [EMAIL PROTECTED]:~ $ cat a.c
> > | void a() { }
> > | int main() { a(); }
> > | [EMAIL PROTECTED]:~ $ gcc-3.3 -m32 -p -pg -o a a.c
> > | [EMAIL PR
6 matches
Mail list logo
