=== vsx_gaby [~kvirc@ACayenne-103-1-3-18.w81-248.abo.wanadoo.fr] has joined #ubuntu-toolchain [03:53] lamont: Are you power building universe with the older gcc? =) [05:35] jbailey: 3.4 [05:53] Nice. How caught up are you? [06:02] morning [07:39] good morning [07:39] hey doko [07:39] doko: OO2 is FTBFS on sparc :) [07:39] the error message is quite strange tho [07:40] which one, 108 or 113? [07:40] 113 [07:41] /build/sparcbuildd/openoffice.org2-1.9.113/ooo-build/build/src680-m113/bridges/source/cpp_uno/gcc3_linux_sparc/cpp2uno.cxx: In function 'void::cpp_vtable_call()': [07:41] /build/sparcbuildd/openoffice.org2-1.9.113/ooo-build/build/src680-m113/bridges/source/cpp_uno/gcc3_linux_sparc/cpp2uno.cxx:423: error: memory input 0 is not directly addressable [07:41] i will put the log online somewhere.. it's quite big atm [07:42] but it's not high priority for me [07:42] i would be more happy to get the gcc ice fixed [07:43] and to understand what's wrong with the mail i just forwarded to you [07:50] doko: the build log is online on people.u.c/~fabbione/ [07:51] hmm, the gnome-games one is about a symbol in two libc files. [07:53] where is jbailey when i need to objectifing him a bit [07:56] he smells the trouble, pretending "switching machines." ;) === chmj [~chmj@196.36.161.235] has joined #ubuntu-toolchain [11:54] fabbione: where can I find the file.i for the unionfs ICE, where the command line args? === jbailey [~jbailey@modemcable086.134-131-66.mc.videotron.ca] has joined #ubuntu-toolchain [03:06] jbailey: gcc-4.0 had a bug that caused us an archive event... doko has uploaded the fix, but I the default hasn't been switched back in the chroots yet [03:08] Right, but I remember that you said that you wanted to build as much of universe as possible, first. [03:09] jbailey: I said I was racing doko [03:15] *lol* [03:15] Right, and I'm sure there were 12 buildds participating in the racing. [03:17] exp.c:75: warning: conflicting types for built-in function 'exp2' [03:17] three cheers for csh! === doko [~doko___@dsl-084-059-087-240.arcor-ip.net] has joined #ubuntu-toolchain [03:30] jbailey: hi [03:30] jbailey: we need the multiarch stuff for gcc, libstdc++ header files aren't correct for biarch's [03:30] Heya Matthias [03:31] Right then. Today is uvf, right? I'd like to get a new udev in and then I can focus on that with you. === lamont wonders if his lkh stuff is going to make it... [03:32] lamont: Yes, I don't consider it version-freeze material. [03:41] doko: eta on a gcc-3.4_3.4.4-3ubuntu2 (or later) upload? [03:41] brb === lamont [~lamont@mix.mmjgroup.com] has joined #ubuntu-toolchain [03:43] lamont: did I forget something? [03:43] 3ubuntu1 was ftbfs on hppa [03:44] bad multiarch patch [03:46] ?? [03:46] ahh, yes [03:46] (I think that was the issue. [03:46] yeah - died in build-hppa64 [03:46] back in a few [03:48] months? [03:51] Wow 590kB/s off of archive.ubuntu.com. I do like this new ISP. [03:52] My last one was like 30kB/sec [04:08] doko: sigh... I might upload it if it's gonna be months.. [04:09] i think he was completing your sentence... === jbailey tweaks lamont's humour filter. [04:09] jbailey: feh! [04:10] Right, you don't have one of those. Bloody americans. /me tries again on the humor filter this time... [04:10] doko: also, it'd be _WAY_COOL_ if we could deliver say java as a separate source package, and get the build-deps for gcc back down to something sane (e.g., not requiring X to build a compiler..) [04:10] jbailey: hehe [04:10] lamont: yes, I know ... please submit a bug report to bugzilla ... [04:11] ok [04:11] uh - for which? [04:11] gcc-4.0 ? [04:11] ok. [04:11] (was multiarch gcc-3.4 bug vs X build-dep) [04:12] that I was asking, that is [04:13] was uploaded while you were taking your nap ;) [04:16] huh? [04:16] I think we may be talking about 3 issues here: [04:16] sorry, s/taking your nap/away/ [04:16] 1) gcc-3.4 has a multiarch bug that you will upload sometime [04:17] 2) /me to file a bug about gcc-4.0's insane build-deps [04:17] 3) gcc-4.0 currently not building on hppa because xorg isn't installable, see 2 [04:18] 1) done [04:19] disable java until 3) is fixed [04:19] 12444, assigned to doko [04:19] well, X might be installable [04:19] it tripped over 4) archive updates aren't atomic, so apt-get update fails randomly in a transient manner [04:20] 1) way cool [04:21] I thought archive updates were made atomic by uploading debs first, then updating package files then deleting old debs? [04:21] 3) modifying the source isn't really a solution for me, since I can't upload the resultant binaries to the archive [04:21] jbailey: yeah [04:21] I'll disable java for the next 4.0 upload [04:21] but tell me how they get all the Packages, Sources, Release and Release.gpg files in with an atomic op, and I'll give you a dollar [04:21] doko: shouldn't be needed [04:22] ok [04:22] doko: lets leave it enabled, and I'll just have to get through the rest of my issues.. [04:22] lamont: lockd? === jbailey hides. [04:22] hrm... how much lead shot is a dollar's worth..... [04:22] =) [04:23] doko: and I have gcc-defaults on no-auto-build until I have the newer gcc-4.0 in the archive, so you're welcome to upload 1.26 with the switch to gcc-4.0 [04:28] ok === jbailey [~jbailey@modemcable086.134-131-66.mc.videotron.ca] has joined #ubuntu-toolchain === chmj [~chmj@196.36.161.235] has joined #ubuntu-toolchain === lamont [~lamont@15.238.5.49] has joined #ubuntu-toolchain === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-toolchain === Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-toolchain [10:29] jbailey: /usr/include/sys/ucontext.h:49: error: array bound is not an integer constant [10:30] hppa? [10:31] Hmm. [10:31] That's not an arch specific file [10:31] unsigned int vrregs[32] [4] ; [10:35] hppa [10:35] typedef struct fpregset [10:35] { [10:35] double fp_dregs[32] ; [10:35] } fpregset_t; [10:35] line 49 is the "typedef struct fpregset" [10:36] This is breezy? [10:36] hrmpf. one for me to investigate later. yes breezy [10:37] er... [10:39] feh [10:39] ia64, sid [10:40] unsigned long _pad[_SC_GR0_OFFSET/8] ; [10:40] clearly I was looking at too many logfiles in rapid succession