Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-11-22 Thread Andreas Schwab
Where is the error? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-10-30 Thread Mikael Pettersson
Thorsten Glaser writes: > Steve M. Robbins dixit: > > >Interesting, but this is an entirely different bug. Also, this new bug is > >in > >gcc, not boost. > > Sorry, right. I’m just amazed that the boost compilation is > still continuing, and replied to the mail “thread” we already > h

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-10-30 Thread Thorsten Glaser
Mikael Pettersson dixit: >The GCC ICE bug is now fixed on GCC trunk by r204224, see >. >That patch backports trivially to gcc-4.8.2 and fixes the ICE >there too. Cool, thanks! >I'll try to get it into the gcc-4.8.3 release, but that's about >

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-09-11 Thread Steve M. Robbins
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. FWIW, Boost.Log is fa

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-09-11 Thread Mikael Pettersson
On Sun, 8 Sep 2013 07:21:40 + (UTC), Thorsten Glaser wrote: > Steve M. Robbins dixit: > > >Interesting, but this is an entirely different bug. Also, this new bug is= > in=20 > >gcc, not boost. > > Sorry, right. I=E2=80=99m just amazed that the boost compilation is > still continuing, and r

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-09-11 Thread John Paul Adrian Glaubitz
Hi! On 09/11/2013 08:16 PM, Thorsten Glaser wrote: > Steve M. Robbins dixit: > >> Is it possible to get a machine with more virtual memory? > > Possible but incredibly difficult: 768 MiB physical RAM are about > the maximum (and even then only possible on the VM buildd, not on > the bare-metal o

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-09-11 Thread John Paul Adrian Glaubitz
On 09/11/2013 08:43 PM, John Paul Adrian Glaubitz wrote: > I have seen Amigas with more than 1GB of memory. Ingo has posted a > screenshot of such an Amiga once. It definitely works. While it > probably won't work with Aranym, maybe there is a chance to get > a 68k machine with 4GB RAM emulated on

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-09-11 Thread Steve M. Robbins
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

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-09-11 Thread Thorsten Glaser
Steve M. Robbins dixit: >Is it possible to get a machine with more virtual memory? Possible but incredibly difficult: 768 MiB physical RAM are about the maximum (and even then only possible on the VM buildd, not on the bare-metal ones, although some Amigas might be bumped up to roughly 256 or eve

Bug#719484: Info received ([pkg-boost-devel] Bug#719484: boost1.54: FTBFS)

2013-09-08 Thread Debian Bug Tracking System
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will rep

Re: [pkg-boost-devel] Bug#719484: boost1.54: FTBFS

2013-09-08 Thread Thorsten Glaser
Steve M. Robbins dixit: >Interesting, but this is an entirely different bug. Also, this new bug is in >gcc, not boost. Sorry, right. I’m just amazed that the boost compilation is still continuing, and replied to the mail “thread” we already had so we have the information in one place. I’ll fol