lamont__ | \sh: ?? what do you want to know? | 12:15 |
---|---|---|
Mithrandir | doko: I don't care, really. | 01:14 |
=== Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-toolchain | ||
=== doko [~doko___@dsl-082-082-206-179.arcor-ip.net] has joined #ubuntu-toolchain | ||
fabbione | hey doko | 07:15 |
fabbione | 13461 sparcbui 25 0 233m 231m 2304 R 82.2 46.3 12:56.52 ld | 07:17 |
fabbione | this is the call that makes gcc-4.0 build hangs forever :) | 07:17 |
fabbione | building libgcj 6 something | 07:17 |
infinity | That's no surprise. | 07:26 |
fabbione | hey infinity | 07:27 |
fabbione | infinity: i need your help to debug the kernel failure on i386 | 07:27 |
fabbione | because i cannot reproduce it here | 07:27 |
fabbione | or better... on concordia i386 | 07:28 |
fabbione | it just builds fine | 07:28 |
fabbione | infinity: would it be an option for you to bootstrap a buildd chroot (breezy), update it to death and rebuild? | 07:29 |
fabbione | i wonder if one of the build-deps (like binutils or so might be old) | 07:29 |
infinity | Hrm, same failure on two different buildds is suspicious though. | 07:29 |
fabbione | infinity: still doesn't explain why it's ok here, on concordia and zul machine | 07:30 |
infinity | Also, if you really need a versioned build-dep on specific toolchain packages, you should depend on them (but sbuild prints a header telling you whwt was used) | 07:30 |
fabbione | infinity: the point is that if it's a toolchain problem, i wasn't aware of it | 07:30 |
fabbione | i did bump the problem build-deps to my knowledge | 07:31 |
infinity | binutils_2.15-6ubuntu1 | 07:31 |
infinity | That's the latest. | 07:31 |
fabbione | Version: 2.15-6ubuntu1 | 07:32 |
fabbione | same on concordia | 07:32 |
infinity | I'll see if the chroots look goofy, but I can't immediately see why they would be (on two machines) | 07:32 |
fabbione | ok | 07:32 |
infinity | Given that this only happens in the -dbg build, I'd guess it's an obscure missing build-dep, not a bad version. | 07:32 |
infinity | (ie: something the kernel needs to build the debug stuff, but you didn't know it) | 07:32 |
fabbione | infinity: note that 386-dbg is built successfully before the failure (686-dbg) | 07:33 |
infinity | Oh, neat. Kay. | 07:33 |
fabbione | so the build deps are there | 07:33 |
infinity | Should I actually look at the ksyms and see HOW they're inconsistent? :) | 07:36 |
infinity | (Assuming the build dir hasn't been purged...) | 07:36 |
fabbione | infinity: that would be an option | 07:37 |
fabbione | my build on concordia is still all there | 07:37 |
fabbione | so we can actually compare the stuff | 07:37 |
infinity | Oh, which it has. lamont has sbuild configured to always purge. | 07:37 |
infinity | Meh. | 07:37 |
fabbione | infinity: well i guess it's time to do a manual build.. isn't it? | 07:38 |
infinity | Yeahp. This is why I wish REDO worked. :) | 07:38 |
infinity | Hrm. I wonder if ccache could be to blame. | 07:40 |
infinity | Did you use ccache in your local build? | 07:40 |
fabbione | yes | 07:40 |
infinity | Anyhow, copying a test chroot that should be identical to the one used for the failed build on terranova and will test a manual build in a sec. | 07:40 |
fabbione | great | 07:41 |
infinity | I'm really hoping the manual build fails. | 07:41 |
fabbione | so do i | 07:41 |
infinity | If it doesn't, I don't look forward to the debugging. | 07:41 |
infinity | I can find this problem on Google in the ARM build... Not very helpful. :) | 07:44 |
fabbione | nope :) | 07:45 |
infinity | Hrm, these chroots don't seem all thayt minimal to me... | 07:50 |
=== infinity puts that on his list of things to look at. | ||
lamont | infinity: REDO does work.. .but takes 3 args (3rd is component) | 07:57 |
lamont | and the chroots do occasionally wind up polluted since things don't like to purge... the new infrastructure throws the chroot away each time | 07:58 |
lamont | (and we always purge, because we don't like to run out of disk space... that's bad...) | 07:58 |
infinity | lamont : Ahh, you originally toldme REDO didn't work at all, I hadn't had a chance to look at how it was currently working. | 08:04 |
lamont | well, replying 'retry' doesn't work. manually saying 'echo foo_1.1 breezy universe >> build/REDO' does | 08:05 |
lamont | anyway - I should be in bed | 08:05 |
fabbione | lamont: good night :) | 08:09 |
infinity | 'Night. :) | 08:12 |
=== chmj [~d3vic3@dumbledore.hbd.com] has joined #ubuntu-toolchain | ||
=== doko [~doko___@dsl-084-059-046-215.arcor-ip.net] has joined #ubuntu-toolchain | ||
infinity | doko : Around? | 02:04 |
infinity | doko : Do I need to start removing some packages from Not-For-Us? | 02:04 |
doko | infinity: what is the current state of the list? | 02:08 |
doko | I updated frozenapps.txt yesterday | 02:09 |
infinity | Oh, fun. | 02:13 |
infinity | Any way to get a diff between the frozenapps of last week and this new one? :) | 02:13 |
infinity | (Maybe I have a copy somewhere... Lemme see) | 02:14 |
doko | infinity: sorry, don't have a diff/the old one | 02:21 |
elmo | infinity: just diff n-f-u vs the list? | 02:22 |
elmo | the only thing in n-f-u should be frozenapps | 02:22 |
infinity | Oh, good point. It doesn't actually get used normally, does it? :) | 02:31 |
infinity | elmo : If I --forget something, will cron.daily revive its correct status on the next run, asi expect it to? | 02:33 |
elmo | infinity: I imagine so, yes | 02:37 |
infinity | elmo : Can you process libccscript's NEW binaries? | 03:39 |
elmo | katie@jackass:~$ helena | 03:39 |
elmo | katie@jackass:~$ | 03:39 |
elmo | infinity: see my whining about ntp in #u-d | 03:40 |
infinity | Does thet helena output mean "I did it already", or "there were no NEW binaries, dumbass"? | 03:43 |
elmo | either, take your pick | 03:44 |
elmo | ;) | 03:44 |
elmo | (first, IIRC) | 03:46 |
infinity | Yeah, --forget and cron.daily get along just fine. Yay. The turnaround time for that trick is much faster than with Debian too, thank god. | 03:50 |
elmo | I can always tell when fabbione's packages are building | 04:04 |
elmo | 4 of the buildds start yellow-lining on nagios :-P | 04:04 |
\sh | starnge | 04:49 |
\sh | strange even | 04:49 |
\sh | on the buildds libccrtp fails at one point, but in my local breezy pbuilder it doesn't fail | 04:49 |
jbailey | elmo: Doesn't gcc and glibc give nagios the same heartburn? | 04:50 |
=== lamont__ [~lamont@15.238.5.47] has joined #ubuntu-toolchain | ||
elmo | jbailey: if they make -j as much as fabbione does, probably yeah | 04:54 |
elmo | it's a tiny tiny percentage of packages that do thi | 04:54 |
jbailey | Right now it only make -j's the number of CPUs. | 04:56 |
jbailey | I keep meaning to make it 2n +1 when the cpus > 1 | 04:56 |
=== Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-toolchain | ||
fabbione | elmo: ahhaha "fabbione: the nagios anal penetrator!" | 10:32 |
fabbione | ;) | 10:32 |
fabbione | good night guys | 10:35 |
fabbione | cya in few hours | 10:35 |
=== \sh [~shermann@server3.servereyes.de] has left #ubuntu-toolchain ["And] |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!