/srv/irclogs.ubuntu.com/2005/11/26/#ubuntu-toolchain.txt

jbailey<stdin>: Assembler messages:12:02
jbailey<stdin>:4: Warning: Empty argument of .endp12:02
jbailey<stdin>:4: Warning: `__syscall_error_4' should be an operand to this .endp12:02
jbaileyI wonder if that's new (for ia64)12:02
fabbionedoko:05:52
fabbionechecking LIBART_LIBS... -lart_lgpl_2  05:52
fabbionechecking for XTestQueryExtension in -lXtst... no05:52
fabbioneconfigure: error: libXtst not found, required by java.awt.Robot05:52
fabbionegcc-snapshot on sparc ^^05:52
fabbione_20051118-0ubuntu105:52
fabbionedoko: sparc is building gcc-4 and gcc-3.. if they are not FTBFS you are good go ;)05:58
fabbionelater05:58
=== rtcm [n=jman@81.84.150.197] has joined #ubuntu-toolchain
=== infinity [n=adconrad@loki.0c3.net] has joined #ubuntu-toolchain
=== Riddell [i=jr@kde/jriddell] has joined #ubuntu-toolchain
infinitydoko : On ia64 and powerpc, gcc-4.0 gets this:07:34
infinitychecking for X... no07:34
infinity*** xlib peers requested but no X library available07:34
infinitymake[3] : *** [configure-target-libjava]  Error 107:34
=== chmj [n=chmj@wbs-146-146-43.telkomadsl.co.za] has joined #ubuntu-toolchain
dokoinfinity: nice, do you know why?09:23
dokoinfinity: on i386 and amd64 as well?09:25
infinitydoko : No, i386 and amd64 built fine, just ppc and ia64 choked.  I'll rety them in a bit to see if it was a transient build-dep issue.12:35
infinityOh, wait.12:37
infinityDid I need a specific newer version of something that might be stuck in the chroots?12:37
infinityNevermind, the chroots are up to date anyway.12:38
=== infinity respins powerpc and ia64 to see what happens.
dokoit's strange, that the generice test for X fails. please keep the build, so you have a look at the config.log file12:41
infinityMeh.  Too late to keep the build, already started it.12:41
infinity(sbuild on our buildds is configured to remove failed trees, so we don't eat disk insanely)12:42
infinityBut if it fails again, I'll muck with it again and keep the tree.12:42
Riddelldoko: so libstdc++ transition has happened?02:47
dokoRiddell: no, no powerpc packages yet02:48
Riddelldoko: so I shouldn't start uploading?02:49
dokono02:57
jbaileydoko: What's blocking PPC?02:59
dokoa strange build failure, no X found. infinity is currently rebuilding03:06
jbaileyFeh, I hope it's not some part of the X transition.03:09
jbaileyI have ppc and amd64 building.  i386 and ia64 fail for glibc right now.03:09
jbaileyI'll be back to hacking on that in an hour or so, I think.03:09
dokoX transition?03:15
jbaileyTo modular X, blocked by glibc.03:26
infinitydoko : Around?03:39
infinitydoko : conftest.c:23:27: error: X11/Intrinsic.h: No such file or directory03:42
dokothat's in libxt-dev? 03:47
infinityIn theory.03:47
dokostrange that his breaks on only two architectures03:48
fabbioneit might as well be that the other 2 chroots are dirty :)03:48
infinityThey're not.03:49
infinityI already checked that.03:49
dokofabbione: but then, my own chroots are dirty as well03:49
infinityI wonder if another -dev lib used to depend on libxt-dev, and your upload happened at just the right time to catch that changing.03:49
fabbionedoko: we all know you like "dirty" stuff :P03:50
fabbioneis that only on gcc-4.?03:50
fabbioneor also 3.4?03:50
dokono, 3.4 doesn't build java03:51
fabbionei saw that error yesterday on -snapshot03:51
fabbione(pasted the log here)03:51
fabbioneon sparc03:51
infinityI blame GTK.03:51
infinityAnyhow.03:52
infinitydoko : Your configure test explicitely includes that header (it's not pulled in through a transient dep in another header), so you may as well just build-dep on libxt-dev and call it a day.03:52
jbaileyI like how even GCC can say "Iz gtk bug" and possibly be right.03:53
doko:)03:53
dokoinfinity: that configure test comes directly from autoconf ...03:53
infinitydoko : And autoconf is wrong, because it assume a monolithic X, but whatever.  One battle at a time. :)03:54
infinityI believe changes are going into autoconf upstream to make the X tests more correctly modular.03:54
dokook, thanks for figuring that out ...03:55
infinityCan you upload ASAP, or should I just pre-seed the chroots with xt-dev and rebuild?03:56
dokouploading now ...03:58
fabbionedoko: you also want to reupload gcc-snapshot03:59
fabbionefor the same reason03:59
dokofabbione: not now ...03:59
infinityIt's hardly urgent.03:59
fabbionefabbione doko:03:59
fabbionefabbione checking LIBART_LIBS... -lart_lgpl_2  03:59
fabbionefabbione checking for XTestQueryExtension in -lXtst... no03:59
fabbionefabbione configure: error: libXtst not found, required by java.awt.Robot03:59
fabbionefabbione gcc-snapshot on sparc ^^03:59
fabbionefabbione _20051118-0ubuntu103:59
fabbionefabbione doko: sparc is building gcc-4 and gcc-3.. if they are not FTBFS you are good go ;)03:59
fabbioneno03:59
fabbionejust FYI03:59
infinityxtst-dev != xt-dev03:59
=== fabbione smells more borkage
infinityIf Java really needs xtst-dev too, you just found another build-dep. :)03:59
dokono, that's something else. xtst-dev is needed for something called JavaRobot04:00
dokobut it's interesting, that the build did succeed on i386 and amd6404:03
infinityOh, cock.04:04
infinitydoko : Do you disable logwatch on ubuntu, or is it just breaking?04:04
infinitydoko : gcc-3.4 on ia64 timed out in the testsuite.04:05
dokono, it was never enabled on ia6404:05
infinityAhh.  I assumed it was enabled on all arches.04:06
infinitySilly me.04:06
infinityMaybe if it was, the odd bugs with it occasionally hanging would have been found sooner. :)04:07
infinity(I still need to look into that some day... I had to kill logwatch on kullervo the other day for gcc-3.4... And lamont had to kill it on hppa, I think)04:07
lamont-awayinfinity: this time I just had to kill of an expect from 3.404:09
lamont-awayinteresting... said find started after findutils sbuild started.04:09
infinityAhh.04:09
infinityARGH.04:10
infinitybuildd-watcher on floe is racing AGAIN.04:10
infinityWhy just floe?  Have you hand-hacked something there?  <stafre>04:10
infinitys/starfe/stare/04:10
lamont-awaynot to the best of my knowledge...04:10
infinitySame buildd-watcher as on hooker...04:11
infinity<sigh>04:11
infinityI'm going to shut down the buildd on floe for now, and look into it tomorrow when my plate's not so full.04:12
infinityHaving several buildds running and competing with each other for chroots is kinda.  Uhm.  Bad.04:12
infinity(Yes, that happened earlier today)04:13
infinityThough right now, we only seem to have one buildd/sbuild, thankfully.  Many buildd-watchers, though.04:13
lamont-awaybuildd-watcher backs up sometimes, yes.04:13
lamont-awaythere might be a window where it assumes that it's find (build-tree cleaning/reporting, etc) will finish before another buildd-watcher starts.04:14
lamont-awaythis is not always the case...04:14
fabbionehey lamont-away 04:14
infinityOddly enough, this never seems to happen on m68k, despite my running buildd-watcher several times per hour and having really, really, really slow I/O.04:15
infinityI guess I should check your diffs against Ryan's tree.04:15
infinitydoko : I see you're getting pressure from vorlon for the system compiler split.04:17
infinity(or, at least splitting java out)04:17
infinitydoko : You really should have put it in big blinking letters in your toolchain roadmap so you could do it on paid time.  It's totally justifiable for Ubuntu as well.04:18
dokoinfinity: it should be in JavaRoadmap04:21
elmoinfinity: our insane number of distros doesn't help, most m68k buildds only have one chroot to traverse04:24
elmoat least, whenever I look at a buildd they tend to sit their in io wait for a rather pointless find over the chroots04:24
infinityelmo : Well, 6.04:24
infinityBut yeah, we have more than 6.04:25
jbaileyWhat's happening with a core compiler split?04:26
elmo?04:27
dokogcc-4.0 sucks in the whole archive as b-d's while completing libgcj  ...04:28
dokojbailey: and even in ubuntu it would be nice to get rid of the x dependencies, as you can see04:28
fabbionejbailey: i think it all goes back to modular gcc...04:29
fabbionethat i did propose not too long ago to $icantrememberwhoinhere04:29
infinityAh-ha.04:29
infinitylamont : I'll fix the "buildd-watcher takes too effin' long" bug tomorrow when I have time to test it.04:30
dokofabbione: I can't remember, did you?04:30
infinityBut it's pretty obvious.04:30
infinityOriginal code:04:30
fabbionedoko: i don't think it was to you actually04:30
infinity        next if $file =~ m#^build/chroot-[^/] +$#;04:30
fabbionedoko: more likely jbailey 04:30
infinityOurs kinda.  Uhm.  Doesn't do that.04:30
elmohahaha04:30
=== infinity claps.
elmomore to the point ours doesn't match 'build/'04:30
infinityStupid build-* split.04:30
infinityelmo : Yes, we explicitely name all the build-$DIST targets in ours... Then don't exclude the chroots.04:31
infinityI'd blame lamont, but this is a public channel, and I'm a nice person.04:31
infinityOops, gthat was my out loud voice. :)04:31
infinitys/gthat/that/04:31
fabbioneahaha04:31
lamont-awayinfinity: oops. :)04:32
lamont-awayinfinity: sigh04:32
infinityI'll fix it tomorrow.04:33
lamont-awaywas that in our original base, or just merged in from upstream?04:33
infinityFor bonus points, I'll actually run a full watcher run, with no report-ed-old-files cache and actually clean everything up, so I can stop ignoring cron's whining.04:33
=== lamont-away added an -xdev to the find, which got rid of the ccache search.. :-)
lamont-awayok04:34
infinityHeh, but if chroot is properly ignored (and ~/ccache as well), that's a non issue.04:34
infinityelmo : floe should stop setting off alarms for you.04:34
infinityThough I'm curious why floe is the only one that races this badly.  Either it has one mother of a huge chroot somewhere (that should be removed and rebuilt), or something's desperately wrong with that box.04:35
infinityI'm going to assume the former, cause it seems well behaved otherwise.04:36
lamont-awayfwiw, pitti picks really ugly version numbers04:36
lamont-awayinkscape_0.42-1build1ubuntu0.1 is now in breezy-security04:37
infinityfoo_1.2.3-1ubuntu05.10?04:37
infinityOh, eww.04:37
lamont-away'zactly04:37
infinitySomeone should point out to him that 'u' is higher than 'b'.04:38
elmodid you guys get my mail about b-backports btw?04:38
elmo[nb: I'm not chasing, I don't care when it's done, just checking] 04:38
lamont-awayelmo: when did you send it?04:38
infinityelmo : Yes, and I'll enable it tomorrow, if the world doesn't come to an end first. :)04:38
lamont-awaythere it is04:39
elmoinfinity: kthx04:39
infinityUnless lamont feels the urge.04:39
fabbionecan't we forget about -backports by ... let say.. mistake?04:39
=== infinity coughs.
fabbionei mean04:40
fabbionethat would comply with the specs04:40
lamont-awayinfinity: I'll go ahead and create the chroots - that's the easy part.04:40
lamont-awaythen it should autostart when the nightly chroot update runs04:41
fabbionequoting: https://wiki.ubuntu.com/BackportsPromotion04:41
infinitySuch faith you have in your automated tools.  I like it.04:41
fabbione"Make people more aware of backports, and make the backport request process LESS transparent"04:41
lamont-awayadare is now launchpad, yes?04:42
fabbionei can't see anything more hidden than not creating the chroots ;)04:42
infinitylamont-away : In theory.  Not sure it's being used as such, but it's definitely not hooked into w-b either.04:42
infinityfabbione : Hah.  Nice thinko.04:42
fabbioneinfinity: when i read that at UBZ i was >< this close to approve the specs :D04:43
infinitySadist.04:43
fabbioneoh yeah04:43
fabbioneI LOVE TO SEE PEOPLE SUFFER IN ENDLESS PAIN04:44
=== infinity goes back to work, after briefly wondering WHY he's working at 2:44am.
infinityWhat I wouldn't give for a nasty case of narcolepsy in my old age.04:44
=== lamont-away is building the chroots, then I get to go work on septic systems. sigh
infinityMan, HP really makes you start at the bottom of the ladder when you're a new hire again, don't they? :)04:45
lamont-awayelmo: chroots are created everywhere04:58
lamont-awayinfinity: nah - this is house work... and the more I procrastinate, the deeper the sludge in the tank.  Hence, todya04:58
lamont-awaythe damage was discovered friday when the nice people pumped the tank for me.04:59
lamont-awaybut I fear I shall be buying hip-waders before the day is out.04:59
infinityAnd throwing them out tomorrow.05:00
lamont-awaynah - you just put trash bags on them first. :-)05:00
=== jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has left #ubuntu-toolchain ["Leaving"]
Riddellinfinity: are you going to upload subversion with new libdb ?06:53
dokoRiddell: he has to ... it's not buildable otherwise06:58
Riddelland neither is large chunks of KDE06:59
=== chmj [n=chmj@wbs-146-146-43.telkomadsl.co.za] has joined #ubuntu-toolchain
=== doko_ [n=doko@dslb-084-059-107-096.pools.arcor-ip.net] has joined #ubuntu-toolchain
lamont-awaychecking for XTestQueryExtension in -lXtst... no09:34
lamont-awayconfigure: error: libXtst not found, required by java.awt.Robot09:34
=== lamont-away kicks doko
lamont-awayinterestingly, libxt-dev is in build-depends09:34
doko_lamont-away: which architecture?09:45
lamont-awaythat was -2 on ppc10:04
lamont-awayis -3 the end of it?10:05
fabbionei told ya that we needed more :)10:43
fabbionegcc-snapshot rules!10:43
fabbionedoko: still around?10:45
dokofabbione: yes10:59
fabbionedoko: ok-- gcc-4.0 is going to build in 10/15 minutes of sparc10:59
fabbione3.4 is up10:59
fabbionedo we need gcj before we start the transition?11:00
dokono11:00
dokohmm, but gettext depends on it ...11:00
fabbioneis gettext a pkg that needs transition?11:00
fabbionewell i guess it's going to stall the others11:03
fabbionewe will see tomorrow11:04
fabbionedoko: thanks for the info11:04
fabbionei am off to sleep11:04
dokono, it doesn't need a transition, but a working libgcj11:04
fabbioneok11:04
lamontgcc-4.0 (-3) will start building on hppa momentarily11:06
dokonote that I did separate the build of the gcj packages into a separate source package, so you need to build that as well. that's currently stuck in NEW11:08
lamontcan we get that unstuck please?11:09
lamontor does that not need to happen before the transition starts?11:09
lamontavg-pkg-build-time gcc-4.011:09
lamontgcc-4.0:                06:31:36 (3 entries, sigma 00:46:59)11:09
dokothe build time will drop, it doesn't build java anymore11:11

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!