On Monday, December 12, 2016 4:13:43 PM CST John Paul Adrian Glaubitz wrote:
> Thanks. And I apologize for being a bit rough in the first report. Thanks
> for fixing despite all that :-).
I appreciate the sentiment. I know it's easy to be frustrated and forget the
person receiving the bug repor
On Sunday, December 11, 2016 8:57:09 PM CST John Paul Adrian Glaubitz wrote:
> On 12/11/2016 07:32 PM, John Paul Adrian Glaubitz wrote:
> > On 12/11/2016 07:20 PM, Steve M. Robbins wrote:
> >> Would someone with a machine be so kind as to run the build,
> >> then send
Hi,
The most recent upload of googletest is failing a test case on m68k (only).
The buildd pages have the build log, but unfortunately it doesn't contain
enough detail. Would someone with a machine be so kind as to run the build,
then send me the following file: obj-*/Testing/Temporary/LastTe
On September 11, 2013 06:16:58 PM Thorsten Glaser wrote:
> Steve M. Robbins dixit:
> >One simple answer: disable building Boost.Log.
>
> Indeed, but what if it becomes used in Debian?
Well, then you have to solve the problem :-) ... or do without the package
that uses it. FWI
On Mon, Sep 09, 2013 at 08:48:34AM +, Thorsten Glaser wrote:
> Please find the build log attached and advice what we can do
> to fix these issues.
> We???ll try to deal with the GCC ICE by
> ourselves alright, but there is not much we can do about the
> memory exhaustion ???
Is it possibl
Wouter,
Thanks very much for your help on this bug!
On Sat, Dec 31, 2005 at 05:58:10PM +0100, Wouter Verhelst wrote:
> My previous attempt wasn't of much help, I presume ;-)
No. :-)
But you did say there that the failure is there even compiling with
-O0. Is that correct?
Thanks,
-Steve
-
On Wed, Dec 07, 2005 at 11:04:44PM +0100, Richard Zidlicky wrote:
> On Mon, Dec 05, 2005 at 11:35:47PM -0500, Steve M. Robbins wrote:
> > The problem turns out to be a failing unit test on
> > m68k only, apparently due to a buggy compiler or libstdc++.
> >
> > I bui
severity 340563 normal
thanks
The problem turns out to be a failing unit test on
m68k only, apparently due to a buggy compiler or libstdc++.
I built cppunit on crest and ran the unit tests. The program
stops with SIGILL. Here's the backtrace from gdb and an
attempt to figure out what the illega
Hello 68k people,
Could I get some help with BTS 340563?
I uploaded a new version of cppunit that enabled unit tests and ---
wouldn't ya know it --- one failed with an "Illegal instruction"
message:
On Thu, Nov 24, 2005 at 09:08:25AM +0100, Christian T. Steigies wrote:
> Package: cppunit
> Vers
t: Re: mpfr 2.0.3: bugfix for test suite
To: "Steve M. Robbins" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Mail-followup-to: "Steve M. Robbins" <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Original-recipient: rfc822;[EMAIL PROTECTED]
Hi,
On 2004-10-26 21:14:40 -0400, S
Hello,
I'm the maintainer of gmp, but fairly ignorant of debian/m68k.
Would anyone here care to comment?
Thanks,
-Steve
- Forwarded message from Kevin Ryde <[EMAIL PROTECTED]> -
Date: Sun, 30 Mar 2003 07:46:00 +1000
From: Kevin Ryde <[EMAIL PROTECTED]>
Subject: Bug#186789: libgmp3: m68
Hello,
I've noticed that my most recent upload of "coin" failed to build on
the m68k autobuilder. Upon running "doxygen", the build failed with
"Error 139":
http://buildd.debian.org/fetch.php?&pkg=coin&ver=1.0.3-3&arch=m68k&stamp=1034361383&file=log&as=raw
I believe that indicates a signal 1
12 matches
Mail list logo
