Re: [buildd] Action plan to get buildds getting online again

Hi, There seems to be a problem with your archive key: elgar:~# apt-get update Hit http://ftp.de.debian.org unstable InRelease Get:1 http://www.freewrt.org cross InRelease [13.2 kB] Hit http://ftp.debian-ports.org unstable InRelease Hit http://ftp.debian-ports.org unreleased InRelease Hit http:

Re: SEGV (was Re: Internal compiler error on m68k for gcc-4.6)

Thorsten, I surely hope notâ•œ this looks more like a hardware issue, possibly faulty RAM, to me. (Never saw the ╲The bug is not reproducible╡ blurb beforeâ•œ) I've seen that one before - it's been there pretty much since the stone ages. gcc does exercise memory more thoroughly than anyt

Re: SEGV (was Re: Internal compiler error on m68k for gcc-4.6)

Ingo J�rgensmann dixit: >Well, as I said: I can run some memory testing tomorrow. This, of >course, doesn't guarantee that the memory is without any faults, if >nothing pops up. Only if something is found, then it's sure that the >memory is faulty. But what if the test won't show memory issues? I'

Re: SEGV (was Re: Internal compiler error on m68k for gcc-4.6)

Am 02.12.2012 um 00:48 schrieb Thorsten Glaser: > I surely hope notâ•œ this looks more like a hardware issue, > possibly faulty RAM, to me. (Never saw the ╲The bug is not > reproducible╡ blurb beforeâ•œ) Well, as I said: I can run some memory testing tomorrow. This, of course, doesn't guara

SEGV (was Re: Internal compiler error on m68k for gcc-4.6)

Ingo J�rgensmann dixit: >For me, it seems as if we have a toolchain problem, maybe caused by >building the toolchain on emulated CPUs for a long term. But that's >only a quick and simplified guess. >../../src/gcc/basic-block.h:927:1: internal compiler error: Segmentation fault >Please submit a fu

Internal compiler error on m68k for gcc-4.6

Hi all! For me, it seems as if we have a toolchain problem, maybe caused by building the toolchain on emulated CPUs for a long term. But that's only a quick and simplified guess. I experienced in Unstable some glibc double free problems, like when running schroot or apt-transport-https. So I

Current Open Position : ID / (Z453BGGXL4G9070675251)...

Dear! I have found your summary on Careerbuilder website and treat you as a future employee. Your wages is $4500 per month + bonus (%6.69 to %9.83) Basic Conditions: - opportunity to work 24-48 hours per week; - US patrials strictly with clear background report; - virtuous organizational

Re: Porting src:openjdk-6 to m68k (II)

Matthias Klose dixit: >If you want a reply from the OpenJDK packagers, please feel free to send email >to them, or at least CC me. I thought debian-java reached them? I was told to use it… >If you submit a patch for 6, please always send one for 7 as well. Don't patch >the upstream source direct

Re: About gcc builtin atomics

Mikael Pettersson dixit: >> All of them have been applied in trunk? > >Yes, they are revisions 187181, 187234, and 187714 from gcc trunk svn. OK, nice to know, then there’s no reason not to always apply all three. By the way: down from several (six or so) hours: -rwxr-xr-x 1 pbuilder 1234 63319

Re: About gcc builtin atomics

On Sat, 1 Dec 2012 14:39:32 + (UTC), Thorsten Glaser wrote: > >Sure, you can find three attrtab speedup patches I've backported from > >gcc-4.8/trunk to gcc-4.6.3 in: > >. > > Oh, you're great, thanks! > > All of the

Re: About gcc builtin atomics

On Sat, 1 Dec 2012 12:33:06 + (UTC), Thorsten Glaser wrote: > Mikael Pettersson dixit: > > >and with two patches to reduce 'genattrtab' overheads; with all > > I think I asked already, but again, pretty please, care to share? ;-) Sure, you can find three attrtab speedup patches I've backpor

Re: About gcc builtin atomics

Ingo Jürgensmann dixit: > True. I'm building gcc-4.6 right now and this genmapthingie really lasted > long. > I think I started the build yesterday evening and today around noon it was > done > with that genmapthingie. It’s doing that thrice, of course, as the Debian package does a full bootstr

Re: About gcc builtin atomics

On 2012-12-01 15:39, Thorsten Glaser wrote: Two are generic, one is m68k-specific. The m68k-specific one makes a huge difference, even when building a cross-compiler on a fast x86_64. OK, wonderful. I noticed genattrtab taking most of a day since 4.4 or so… True. I'm building gcc-4.6 right

Re: About gcc builtin atomics

Mikael Pettersson dixit: >Sure, you can find three attrtab speedup patches I've backported from >gcc-4.8/trunk to gcc-4.6.3 in: >. Oh, you’re great, thanks! All of them have been applied in trunk? >Two are generic, one i

Re: About gcc builtin atomics

Mikael Pettersson dixit: >and with two patches to reduce 'genattrtab' overheads; with all I think I asked already, but again, pretty please, care to share? ;-) bye, //mirabilos -- 13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good guy. But he's always right! In every fsckin

Re: [buildd] Action plan to get buildds getting online again

On 2012-12-01 12:15, Thorsten Glaser wrote: Maybe you should first update to etch-m68k and from that to unstable and […] I think it's doable. Not officially, really; most of our packages are recent enough to not support upgrading from anything older than squeeze. I think, debootstrapping a ch

Re: [buildd] Action plan to get buildds getting online again

Ingo Jürgensmann dixit: > Maybe you should first update to etch-m68k and from that to unstable and […] > I think it's doable. Not officially, really; most of our packages are recent enough to not support upgrading from anything older than squeeze. I think, debootstrapping a chroot, moving stuff

Re: [buildd] Action plan to get buildds getting online again

On 2012-12-01 02:09, Michael Schmitz wrote: Honestly - I did try to follow Thorsten's notes on adding his repo and bootstrapping a chroot, but it failed mysteriously at step one. Did I mention my base system is still at version sarge? Maybe you should first update to etch-m68k and from that to