=== ajmitch [~ajmitch@port162-209.ubs.maxnet.co.nz] has joined #ubuntu-toolchain [05:05] morning [05:11] fabbione: Still not sleeping well? [05:13] jbailey: no.. not really [05:13] there was too much light in the bed room [05:13] and i woke up [05:13] oh well i need to fix that problem asap [05:13] otherwise i will get stupid [05:14] at 4am? [05:14] Too much light? [05:14] sick. [05:15] when it's summer in dk, the sun goes up at 3am and down at 00am :/ [05:15] it's like 20 hours of light [05:15] in winter is the other way around [05:15] The further north I've lived was 49 [05:16] I think we're at like 45 now. [05:16] i can't remember how much we are now [05:17] it's +56 (almost) here === chmj [~d3vic3@dumbledore.hbd.com] has joined #ubuntu-toolchain [10:39] doko, ping === Seveas [~seveas@ksl403-uva-148.wireless.uva.nl] has joined #ubuntu-toolchain [11:38] jbailey, ping [12:31] chmj: pong [12:34] doko: fix gcc-3.4. kthxbye === doko_ [~doko___@dsl-084-059-038-218.arcor-ip.net] has joined #ubuntu-toolchain [12:34] doko: fix gcc-3.4. kthxbye [12:35] fabbione: waiting for elmo to approve binutils 2.16 before. kthxbye [12:36] doko_: the kernel is FTBFS due to the i486-linux-gnu-gcc-wtf-gth symlinks [12:36] fabbione, and it doesn't help you without i486-linux-gnu-ld symlinks. be patient [12:40] doko, can you have a look at http://people.ubuntu.com/~charles/glibc_232.debdiff please [12:41] that should fix binutils FTBFS === chmj lunch [12:41] doko_: do i have any other option? ;) === fabbione -> food [12:47] chmj: I'm waiting for jbailey, if that's still necessary with binutils 2.16 ... [12:48] doko_, ok [01:52] doko: Eh? [01:54] jbailey: chmj's patch ... [01:54] jbailey, hi [01:54] jbailey ---> http://people.ubuntu.com/~charles/glibc_232.debdiff [01:56] Right, this is for gdb compiling on ppc, yes? [01:57] binutils [01:57] 2.15 or 2.16? [01:57] chmj: I'm a bit confused, because the patch is against the version in Hoary. [01:58] http://people.ubuntu.com/~lamont/buildLogs/b/binutils/2.15-5ubuntu3/ [01:59] oh, doko uploaded a new version [02:01] But in general, the glibc patch you made is against the version in Hoary. =) [02:01] doko: I hadn't realised binutils wasn't being updated as well, I'll do the new glibc upload right away then. [02:02] Oh, not in the new version. === jbailey is a bit confused, but it's morning. =) [02:02] jbailey, erm, just disregard it [02:02] jbailey: 'morning' and 'confused' are redundant [02:03] Well, the patch is one that I need in 2.3.5 anyway, so thanks. If you're hacking on glibc in the future, we have a template.dpatch file in the patches subdir that we usually use for the top so that we have the comments in a prefered format. [02:03] Just makes it a bit easier. =) [02:03] daniels: =) [02:03] jbailey, sweet [02:04] chmj: Are you looking to dive in more to toolchain stuff? [02:04] jbailey: he is 0wn3d by the kernel team! put your hands off [02:04] sure [02:04] heheh [02:04] ehhehe [02:05] jbailey, oh btw, cdbs2 and kernel build ? [02:05] fabbione: I'll mud wresstle you for 'im! [02:05] jbailey: any time :) [02:05] chmj: Sounds lovely. =) The module doesn't exist yet. Got hack time? === fabbione wears his sumo underwear [02:05] jbailey, I remember we discussed doing that [02:05] Right. If you have hack time, I suspect that it's doable now. [02:06] jbailey, ok [02:06] Probably the best thing to do would be to do a proof-of-concept and then bribe Fabio. [02:06] jbailey, as it looks like, the patch is still needed for powerpc, and now ..., so I point fabbione to you for the non-working toolchain ;-P [02:07] toolchain is broken = i can't build the kernel [02:07] fix it [02:07] kthxbye [02:08] Erm, that doesn't make sense. [02:08] Your kernel shouldn't be using glibc to build it, dude. =) [02:08] no but it needs gcc-3.4 [02:08] heh [02:08] that is actually broken [02:08] and still part of "toolchain" [02:09] fabbione, you're still annoying, I thought you got some food ... ;) [02:09] hey, if the toolchain is broken, then I can't build xorg, either [02:10] fabbione: What part is broken? We built gcc-3.4 with breezy recently for the ppc64 stuff, so it built then. [02:11] jbailey: the borkage is introduced by the new dpkg [02:11] missing i486-linux-gnu-gcc-ld-wtf-gth-fym symlinks :) [02:11] doko: that's only because i love you :) [02:12] doko: Sounds like you just need to push a new gcc-3.4 so that it builds as i486-linux instead of i386-linux... [02:12] daniels: nah, no excuse for you, you're not using the symlinks ;-P [02:13] jbailey: yes, depending on the new binutils, which do have this change as well, failing on powerpc, because of a glibc bug ... [02:13] remember, it's c-h-a-i-n in toolchain :) [02:14] like in nuclear C-H-A-I-N reaction? [02:14] doko: hah, I'll start using the symlinks if it gives me an excuse :P [02:15] anyway i am off for a nap [02:15] later guys [02:15] fabbione: More like a c-h-a-i-n gang, where we all shovel coal. [02:15] night fabbione [03:25] jbailey: one more glibc change: please add an /usr/hppa64-linux/gnu symlink [03:25] Eh? I thought that was in there already.. [03:26] no /usr/hppa64-linux/include, but not /usr/hppa64-linux-gnu/include [03:27] Oh, I see. [03:27] So have two symlinks, or just change it? [03:27] two would be ok for some time until all compilers are rebuilt [03:27] 'k [03:28] so, need this in unstable as well ... [03:39] fabbione: ping? [04:15] jbailey uploads glibc: [04:16] * Drop support for Neanderthal Sparc systems (fabbione, it was a nice time, kthxbye) === zul [~chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-toolchain === lamont__ [~lamont@15.238.7.25] has joined #ubuntu-toolchain [04:57] lamont__: Confirm okay to disable glibc testsuite for hppa to make it just build for you? [04:58] jbailey: works for me... [04:59] of course, we'll want to work towards being able to enable it again, eh? [04:59] Yes, dear. [05:00] I have an idea what the problem is, but ENOTIME [05:03] heh === lamont__ finds that the first half of that sometimes applies, but the 2nd half almost always does [05:04] in my case, that is. [05:53] doko: [05:53] ln -sf /usr/include debian/$(curpass)/usr/hppa64-linux/include [05:53] ln -sf /usr/include debian/$(curpass)/usr/hppa64-linux-gnu/include [05:53] yes? [05:57] yes, the former should already exist [05:58] jbailey: pong [05:58] Yup [05:58] fabbione: Two things. [05:59] jbailey: yes? [06:00] 1) I'd like to do some of the sparc magic, but I didn't have time for a test round this weekend. Is there any way you tell the buildd not to auto-sign glibc so I can look at the log before it gets pushed? [06:00] (I don't type that fast, dude. *g*) [06:00] 2) What am I looking for in the ppc kernel build? [06:01] 1) i can blacklist it and build it manually.. yes [06:01] 2) a possible FTBFS at the end of the process [06:01] 2) if it works is a davis issue [06:03] 1) Please. I expect it to work, but I don't actually know. If you'd rather I can delay it and do a testing round later. [06:05] jbailey: i had say that you upload it, i build it, but not upload the binaries. we install them in a chroot and play a bit [06:05] Sounds gt [06:25] jbailey: ok.. glibc is blacklisted [06:25] upload anytime you want :) [06:25] I've just started the amd64 and i386 test builds. [06:25] ppc testbuild started. [06:26] ia64 is just updating its chroot. [06:26] jbailey: how is the kernel build going? [06:26] It's in drivers/sata [06:26] err. drivers/scsi/sata [06:26] of what flavour? :) [06:26] How do I tell? [06:27] jbailey: the old fashion way ;) [06:27] cd debian/build && for i in `ls`; do du -sk $i; done [06:27] Guess and hope noone notices if you're wrong? [06:27] you will see by the size :) [06:28] Ah. =) With glibc, we keep a local log file for each one, so I just look to see which one is growing. =) [06:29] jbailey: Manoj accepted both our patches [06:29] and that's perfect [06:29] iirc there is only one inliner left :) [06:29] and i need to go off [06:30] time to prepare dinner [06:30] cya tomorrow guys [06:30] 423952 build-powerpc64-smp [06:30] Is the one getting bigger atm. [06:30] linux-* doesn't get bigger [06:30] only the build-* [06:30] so you should have almost done [06:30] but the failure happens after all the build-* are done [06:31] anyway thanks a lot [06:31] cya later [06:33] fabbione: glad to help =) [06:35] ia64 build started. [06:35] doko: These four should finish about when I get back from lunch. Assuming success, I'll push it up. [06:39] fine [07:19] http://gcc.gnu.org/ml/gcc/2005-06/msg00420.html === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-toolchain === BenM_ [~builder@130.57.22.69] has joined #ubuntu-toolchain [08:57] doko, ? [08:58] tseng sent me to you [08:58] I am a mono dev, and am having trouble on gcc 4.0 === BenM [~benm@130.57.22.69] has joined #ubuntu-toolchain [09:40] Tests fine on my 4 systems, uploading. === zul [~chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-toolchain [09:57] glibc_2.3.5-1ubuntu5_source.changes ACCEPTED [11:18] jbailey: do you want to know that the ppc build of glibc failed? [11:33] lamont__: I hadn't checked up on it yet. Did you see why it failed? [11:33] jbailey: no - just got the mailer daemon notification for over-size mail === lamont__ looks [11:33] np, dl'ing [11:34] wtf? [11:34] install_root=/build/buildd/glibc-2.3.5/debian/tmp-ppc64 install [11:34] make[1] : Entering directory `/build/buildd/glibc-2.3.5/build-tree/powerpc-ppc64' [11:34] make[1] : *** No rule to make target `install'. Stop. [11:34] make[1] : Leaving directory `/build/buildd/glibc-2.3.5/build-tree/powerpc-ppc64' === lamont__ giggles [11:36] checking for forced unwind support... no [11:36] configure: error: forced unwind support is required [11:36] That's the real failure. [11:36] ah, ok === lamont__ [~lamont@15.238.7.25] has joined #ubuntu-toolchain