=== doko_ [n=doko@dslb-088-073-066-174.pools.arcor-ip.net] has joined #ubuntu-toolchain === Keybuk [n=scott@217.205.109.249] has joined #ubuntu-toolchain [10:40] doko_: ping? [10:41] fabbione: pong [10:41] doko_: what gcc do you expect for feisty? [10:41] i have glibc-2.5 almost done [10:44] currently 4.1; 4.2 is not released, and probably will take longer. [10:44] doko_: so the same gcc we have now in edgy? [10:44] so we have to backport the relevant binutils changes [10:44] or are you adding extra patches and stuff like that? [10:44] we will need a very new binutils to get hppa back in the game [10:44] AFAIK Jeff is looking at it [10:44] fabbione: no, extra patches, long double 64->128 bit ABI change on powerpc and sparc [10:44] doko_: ok, can you please let me have a source to build before monday? [10:44] fabbione: unreleased? an alternative might be the HJ Lu binutils for feisty [10:44] or if you have it done.. now [10:44] doko_: yes unreleased.. [10:44] dunno.. i hate binutils from the bottom of my heart [10:44] it freaks me out... [10:44] it's not my toy package either [10:45] eheh [10:45] what i am done up till now is to merge all the packaging bits for glibc. i will need help from Jeff to review debian/patches [10:45] I'll prepare gcc either over the weekend or today [10:45] and that's basically done [10:46] but i want to simulate a bootstrap over all my machines [10:46] build gcc with old gcc [10:46] build gcc [10:46] build kernel (that i know is going to suck) [10:46] rebuild glibc and gcc and kernel again for fun and profit [10:46] that would be lovely.. thanks [10:47] if we can have at least part of the toolchain ready before we open feisty that will be great === mlpug [n=user@a84-231-238-186.elisa-laajakaista.fi] has joined #ubuntu-toolchain === Dvalin [i=hawkeye@195.0.160.130] has joined #ubuntu-toolchain === rodarvus [n=rodarvus@ubuntu/member/rodarvus] has joined #ubuntu-toolchain === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-toolchain [03:46] fabbione: Yeah, what you said. [03:46] =) [03:46] ehe [03:47] i was saying that my target now is to 2.5 out for opening [03:47] then we can cleanup as much as we want [03:47] Yup. [03:47] afaict the only thing missing now for an upload is debian/patches/ubuntu from 2.4 to 2.5 [03:47] I need to merge in ports stuff for hppa/ [03:47] And get the TLS patches in for binutils. [03:47] and decide if we want NPTL or LT for hppa... [03:47] The nice part is that I now feel comfortable enough with BFD to do that. [03:48] No LT. [03:48] ok [03:48] i can fix that easily [03:48] Our .orig.tar.gz shouldn't even have the tar.bz2 in there. [03:48] well it has for now.. [03:48] But just in general. [03:48] should we kill it? [03:48] yeah [03:48] We're not Debian, we don't drag corpses behind us chained to the bumper. [03:49] ahah [03:49] there are a few entries in debian/changelog marked as (requires testing) or (requires review) [03:49] that's because i am not 100% of the reason why that stuff is there [03:52] The only thing that I see in there off hand is that some of the changes done directly to control.in/{main,opt} might be best done in sysdeps/depflags.pl [03:52] I *hate* sysdeps/depflags.pl [03:52] That was about where I ran out of steam redoing the packages for Debian in 2003. [03:53] What I think it should be is a tab delimited table or something like that which sits in control.in [03:54] Maybe a few different files, conflicts, depends, etc. [03:54] ARCH\tPACKAGE\tVERSION [04:00] imho we could simplify the packaging a lot with a set of shell scripts [04:01] or start eliminating tons of .mk stuff [04:01] There's a surprising amount of this that *can't* be simplified once you start to look at what it does. [04:01] But certainly half of rules.d/debhelper.mk can go. [04:02] I thought quilt provided a rules snippet to include, so I'm not sure why we have our own. [04:08] the tarball approach can go again; it was for the binutils-source package, elmo did prefer to have patched sources in this patch, so we can revert that again. [04:08] but keeping the binutils-source package [04:09] doko_: I've wondered a few times if it's better to use the upstream binutils releases or HJ Lu's snapshots, since his snapshots tend to include extra optimisation instructions and such. [04:10] But are still sort of crack-of-the-moment. [04:10] With his snapshots, we'dhave the HPPA TLS stuff already. [04:10] Otherwise we'll have to backport them to get hppa working. [04:13] jbailey: yes, I was thinking about it as well. but then, how switch back to FSF binutils without having any regressions? [04:14] Dunno. I've never understood why the binutils release cycle is so slow. [04:15] The changes that tend to go in there seem to be consistantly just opcode adds, etc. [04:17] if we can track these changes in a separate branch? [04:18] I don't think we have the bodies on toolchain to do that sort of work. [04:18] Since that drags the QA responsibility for those things onto us. [04:18] I think it just wouldn't get done in the end. [04:21] jbailey: i am getting a feisty amd64 chroot on ronne. the debs look good [04:22] jbailey: at least debdiff did spot only 2 changes.. one i knew about but we don't care (it's ppc only) and the other one it's just an extra file that needs investigation [04:34] We don't care about ppc anymore? =/ [04:35] it's already fixed in bzr.. i didn't feel restarting the builds for a ppc thingy [04:35] but at least i know it is fixed properly [04:39] dh_install: libc6-dev missing files (debian/tmp-libc/usr/lib/nptl*), aborting [04:39] GRRRRRRRRRRRRRRR [05:06] Right, debhelper 5 broke that construct, sadly. [05:06] I pouted at Joey for it. [05:06] foo* doesn't resolve to empty set in a glob anymore. [05:08] i don't think we ship anything with that name anyway [05:09] i386/ia64 did fail [05:09] amd64 is rebuilding and waiting sparc/ppc [05:10] we might as well chop it away if it's not required [05:17] (feisty-libc)fabbione@ronne:/lib$ [05:17] well.. they seem to work on amd64 at least [05:25] whee =) [05:26] waiting for all the builds to complete.. then i will respin with that postinst fix and the nptl fix [05:26] i am sure locales are broken [05:27] because we need to port the patch for belocs and the other search path from 2.4 [05:27] but at least we know that we can run === __keybuk [n=scott@217.205.109.249] has joined #ubuntu-toolchain [06:56] fabbione: what gcc do you guys use to build kernel? [06:56] gcc-4.1 [06:56] okay [06:56] Dvalin: doko is our gcc god here [06:56] yes [06:56] that's why I ask in here ;) [06:57] I have this weird issue [06:57] yeah but you are building on *mandriva* [06:57] you have issues.. no matter : [06:57] :P [06:57] with the atyfb driver, I tried recompiling the same old kernel where it was working [06:57] with current toolchain, not what I compiled it at that time [06:58] oh you are suspecting a gcc breakage? [06:58] otherwise everything being the same, and problem exist in the same kernel release which previously worked (even with the same config) [06:58] yes [06:58] Dvalin: i suggest you try with -O0 and check the asm output [06:59] in theory it should be the same [06:59] I'm thinking about trying to build with gcc 4.0.3 which I built last working kernel with.. [06:59] fabbione: okay, good tip, for checking the asm output.. I think you overestimating me ;) [06:59] Dvalin: nah.. that was a trick doko handed to me [07:00] checking the asm output? or -O0? [07:00] asm output [07:00] and -O0 ;) [07:00] both [07:01] okay [07:01] I'm not competent at asm stuff.. ;p [07:02] but I did score 100% at a simple asm asisgnment at an exam last spring ;) [07:02] harrharr [07:02] I think that landed me the C in stead of E which otherwise would be the final grade :p [07:03] You don't need to write asm fluently to be able to compare it. [07:03] ah [07:03] (Thank god, too, because my i386 asm is less than perfect) [07:03] I see your point :) [07:04] Useless architectures, like m68k, powerpc, hppa, and sparc. Sure, they're easy. :P [07:04] i386, not so much. [07:05] hehe [07:05] "useless" [07:05] quite a bombastic statement, no? ;) [07:05] Yes, that belonged in quotes. I missed adding the irony. :) [07:28] infinity: hppa can be annoyingly hard to read. It appears to be able to unable to load 32 bits into a register in a single operation. [07:29] jbailey: ia64 glibc are good [07:29] if i could only get sparc to complete the testsuite without a kernel crash [07:29] jbailey: i am uploading all the debs here: http://people.ubuntu.com/~fabbione/glibc-2.5/ [07:29] Joy. [07:29] amd64 is good too [07:29] Does it crash in a consistant place? [07:29] i386 will test tomorrow [07:29] it's a kernel problem.. [07:30] it lockups on high load [07:30] i need to downgrade to edgy kernel === fabbione was running 2.6.19-rc2 [07:30] Any idea if Ben is going to target 2.6.19 or 2.6.20 for fiesty? [07:31] .19 afaik [07:31] 9391 fabbione 21 0 5088 448 304 D 300 0.0 9:22.63 ld-linux.so.2 [07:31] now i have a process on 400 of CPU [07:32] fabbione: Any idea when we're targetting to open the next one? [07:32] I remember that edgy had some hitches, openning up. [07:32] the kernel is already in git [07:32] we need to get a few important things fixed [07:32] like that headers issue i was mentioning [07:32] otherwise we won't even be able to rebuild the kernel [07:32] Headers issue? [07:33] yes.. build .19 [07:33] install linux-libc-dev [07:33] and you are doomed: ) [07:33] you can't even rebuild the kernel with that stuff === jbailey knows of ia64 klibc headers and ppc merging ppc and ppc incorrectly. [07:33] it's totally broken [07:33] Err. [07:33] no.. this is worst [07:33] Kernel builds with -nostdinc. [07:33] Nothing in /usr/include should matter in the slighjtest. [07:33] not the scripts/* [07:33] and you need those [07:34] like.. hmmmm modpost? [07:34] I don't think I know about those. [07:34] you use them all the time.. you just don't know that :) [07:34] Can you toss a build failure into a pastebin? [07:34] jbailey: sure.. in a minute [07:34] No worries. [07:35] no actually i can't.. i don't have the deb handy.. [07:35] but i can show it here by memory [07:35] #include [07:35] #include [07:35] int main() { [07:35] return -EINVAL; [07:36] return -SOL_SOCKET; [07:36] } [07:36] you can't build that one [07:36] Right, but I'm curious about the actual failure. [07:37] it's an include order issue [07:37] either SOL_SOCKET or EINVAL is not defined [07:37] if you swap the include's at the top, you get the other error [07:37] gcc-4.1_4.1.1-17ubuntu1 is on ronne:~doko/gcc/4.1/ [07:38] doko_: cool.. there is a feisty-libc chroot (amd64) on ronne [07:38] doko_: [07:38] enabling long-double-128 on powerpc and sparc, configuring with --enable-secureplt on powerpc [07:38] you can build there if you like [07:38] it has glibc-2.5 installed [07:38] doko_: i will do ia64/ppc/sparc/i386 tomorrow [07:38] i am just too tired today to do it [07:38] actually.. i could do ia64 overnight [07:39] ii libc6.1 2.5-0ubuntu1 GNU C Library: Shared libraries [07:41] doko_: Do you happen to know what binutils FC6 is shipping with? I remember that they have the GNU HASH lookups for the PLT stuff as one of their features. [07:41] But I think that requires a new binutils snapshot. [07:42] http://cvs.fedora.redhat.com/viewcvs/devel/binutils/ [07:42] 2.17.50 [07:43] 2.17.50.0.6, the version number smells like beeing the HJ stuff ... [07:44] doko_: gcc-4.1 building on ia64 [07:44] doko_: do you want to ask B-D on feisty-libc chroot or should I? i can do the others locally [07:45] they were installed [07:45] currently building on feisty [07:45] hmm ok [07:45] good [08:15] Hmm, here's going to be an interesting question. [08:15] Some of the libc tests probably need corresponding kernel functions to pass. [08:15] jbailey: ? [08:15] What do the buildds run for a kernel> [08:15] oh yes.. i already noticed that [08:16] 2.6.17 basically everywhere [08:16] i saw a bunch of test failures [08:16] but i didn't track them down yet [08:16] and i don't think for bootstrapping we care too much [08:16] If you toss those into a pastebin somewhere, I might be able to offer you opinions on them. [08:17] jbailey: ronne:/home/fabbione/{i386,amd64}/ [08:17] ppc is on davis [08:17] i can upload sparc and ia64 later [08:18] davis is still building FYI [08:19] oh acutally i did build ia64 with .19 [08:20] make[3] : bug-atexit3-lib.cc: Command not found [08:20] make[3] : *** [/home/fabbione/i386/glibc-2.5/build-tree/i386-i686/dlfcn/bug-atexi [08:20] t3-lib.os] Error 127 [08:20] Eh, weird. [08:20] Oh, no G++ installed. [08:21] scp glibc-2.5.tar.bz2 chinstrap.ubuntu.com:glibc-2.5-ia64-log.tar.bz2 [08:22] jbailey: uh? i did use dpkg-buildpackage.. do we miss a B-D ? [08:23] checking for g++... g++ [08:23] hmmm [08:24] i readded the CXX patch from you... [08:24] could that be related? [08:24] 604-421-2460 604-726-2460 [08:24] ls [08:24] BAH [08:24] 0wn3d [08:29] mm/filemap.c: In function ?__generic_file_aio_write_nolock?: [08:29] mm/filemap.c:1830: sorry, unimplemented: inlining failed in call to ?generic_write_checks?: function body not available [08:30] mm/filemap.c:2133: sorry, unimplemented: called from here [08:30] fabbione: are you sure you actually can compile the kernel with -O0? [08:30] Dvalin: i am pretty sure you can [08:31] hmm [08:31] then I don't get why I get that error when compiling with -O0 [08:31] will try again with -O2 to see if it reproduces [08:31] i usually compile only the bits i need with -O0 [08:31] okay [08:32] so in other words, you don't know for sure that the *whole* kernel can be compiled with -O0? [08:32] no but it should be able to [08:32] soo [08:32] the error I got, a bug in kernel? [08:34] or gcc [08:35] it really depends what you are experimenting with [08:35] fabbione: It's entirely possibly that the kernel relies on optimiser tricks for correct code. [08:35] You can't compile glibc at -O0 for instance. [08:35] you are working on both at the same times so that makes it impossible to track easily [08:35] fabbione: I got the same error with the "old" compiler [08:35] jbailey: it's a possibility.. [08:35] I reverted back to last known good compiler [08:35] 4.0.3 [08:36] which I'm using now [08:40] fabbione: You didn't use debuild to build this? [08:40] dpkg-buildpackage -rfakeroot -uc -us -b [08:40] as i always do [08:41] debuild actually logs the whole build (as well as cleans some pieces of the environment) [08:41] So just "debuild -uc -us -b" is the equivalent. [08:41] hmm ok === mlpug [n=user@a84-231-238-186.elisa-laajakaista.fi] has joined #ubuntu-toolchain [08:42] we still shouldn't really on debuild.. it should just work... [08:43] if we need to sanitize the ENV that should happen in debian/rules [08:43] eh, what do you mean? [08:43] sbuild doesn't call debuild or dpkg-buildpackage [08:43] No - sometimes I set external environment varilables to change what's happening intentionally. [08:43] ok.. those are well defined things to trigger certain behavious [08:43] Sucks to be sbuild. If the buildds don't use what all the developpers use then I consider the buildd broken. [08:43] but i don't set anything in my env other than ccache [08:44] Right, I don't know that it's a problem or not. Just that debuild is handy for that. [08:44] Mostly what I'm wishing for is the .build file. [08:44] The logs that the glibc build produces on its own start logging too late. [08:44] jbailey: actually.. no.. i disagree.. according to policy you should be able to call ./debian/rules $target and it should work. All the other tools are "wrappers" for that [08:44] So? [08:44] the buildd should do what the developpers are doing for maximum reliability. [08:45] whether the devs change or whether the buildds change is irrelevant. [08:45] if debuild does extra cleaning, then it might fail on the buildd [08:45] well i don't use debuild and like you i did build 95% of the biggest packages around without issues... [08:45] if you understand what i mean [08:45] It's less likely, I think, since the buildds don't tend to have random things in their environment. [08:45] Whereas a user running gnome and a pile of crap might. [08:46] right, but in my buildd/chroots i don't set random crap either [08:46] i know that for a fact of me being sane :) [08:46] So you agree, nice. =) === jbailey hids [08:46] +e [08:46] ahah whatever :) [08:46] what i consider scary is this: [08:46] i have a clean environment [08:46] either way, I want a log file of the build more than I care about the environment. [08:46] It would've told me how make was called. [08:47] jbailey: the sources are stilll on ronne [08:47] it doesn't take long to build there [08:47] Nope, should be about 20 minutes. [08:47] more or less yeah [08:47] Which I can do. But I was asking that you consider using debuild since it just always produces a log file. [08:48] i will try.. i need to get used to type it :) [08:48] oh my wife made dinner! [08:48] bbl [08:48] enjoy! =) [08:48] thanks [08:48] bah! no source package! =) === jbailey also talks fabbione into dropping the -b =) [08:55] echo "CXX = " >> build-tree/i386-libc/configparms [08:55] that would be the bug. =) [08:57] Need s BUILD_CXX line in debian/rules [08:57] Although more I wonder how much we care about the cross-compilation case. [08:58] echo "CXX = g++-4.1 -fno-stack-protector" >> build-tree/i386-libc/configpa [08:58] Better. [08:58] doko_: Any idea if upstream gcc is going to integrate cleanly an option to enable the stack-protector by default? [08:59] jbailey: yes.. in ~fabbione/ [09:00] fabbione: All good. cp -a was my bitch. =) [09:00] jbailey: so are you going to commit the fix? [09:00] After I see a succesful test suite on i386, yes. =) [09:01] jbailey: also note that the patch pristine from 2.4.. so it have been buggy in edgy too? [09:02] I don't think these two tests existed in 2.4. [09:02] ok [09:02] So the only thing would've been the C++ abi test, we I never paid attention to anyway. [09:02] see.. as i said.. harmless errors in the logs [09:02] you should have trust me before :P [09:03] I didn't say I didn't trust you. =) I merely offered my opinion. [09:03] "wow, this is broken. Here's the fix." Easy opinions like that. =) [09:04] ahah [09:04] yeah yeah [09:04] fabbione: There've got to be *some* advantages of staring at this package for 6 years. =) [09:05] jbailey: like an extra discount for the super-pack offer from your shrink? [09:05] Doesn't help much after the surcharge. [09:05] 10 hours at the price of 8 [09:06] Something about my reality check bouncing... [09:06] and if you are a glibc maintianer 10 hours at the price of 6! [09:06] ehhe [09:07] jbailey: no idea ... [09:10] doko_: you want to look at debian bug #391858 [09:10] doko_: it's not a glibc bug, but gcc.. the same we fixed in ubuntu not too long ago [09:10] their fix is just wrong [09:10] and they don't take into account other arches like sparc [09:10] that does the same thing [09:24] Tags: experimental, fixed-in-experimental [09:25] yes but still in glibc [09:25] and you are the gcc maintainer so you might want to explain to them that it is wrong [09:28] fabbione: fixed-in-experimental, they did fix it already ;-p [09:29] doko_: yes i know.. whatever.. our gcc is fine and will cope.. [09:30] jbailey: the ppc build seems to hang on a test suite [09:30] i have a bunch of processes in Z on davis [09:31] Joy. [09:32] this is the second timei see this [09:32] in the same build [09:33] the first time did "unblock" itself [09:37] fabbione: Can you tell which test? [09:37] x/regex.h posix/wordexp.h posix/fnmatch.h posix/getopt.h posix/tar.h posix/sys/unistd.h posix/sched.h posix/re_comp.h posix/wait.h posix/cpio.h posix/spawn.h pwd/pwd.h resolv/resolv.h resolv/netdb.h resolv/arpa/nameser.h resolv/arpa/nameser_compat.h resource/sys/resource.h resource/sys/vlimit.h resource/sys/vtimes.h resource/ulimit.h rt/aio.h rt/mqueue.h setjmp/setjmp.h shadow/shadow.h signal/signal.h signal/sys/signal.h socket/sys/soc [09:37] ket.h socket/sys/un.h stdio-common/printf.h stdio-common/stdio_ext.h stdlib/stdlib.h stdlib/alloca.h stdlib/monetary.h stdlib/fmtmsg.h stdlib/ucontext.h sysdeps/generic/inttypes.h sysdeps/generic/stdint.h stdlib/errno.h stdlib/sys/errno.h string/string.h string/strings.h string/memory.h string/endian.h string/argz.h string/envz.h string/byteswap.h sunrpc/rpc/auth.h sunrpc/rpc/auth_des.h sunrpc/rpc/auth_unix.h sunrpc/rpc/clnt.h sunrpc/r [09:37] pc/des_crypt.h sunrpc/rpc/key_prot.h sunrpc/rpc/netdb.h sunrpc/rpc/pmap_clnt.h sunrpc/rpc/pmap_prot.h sunrpc/rpc/pmap_rmt.h sunrpc/rpc/rpc.h sunrpc/rpc/rpc_des.h sunrpc/rpc/rpc_msg.h sunrpc/rpc/svc.h sunrpc/rpc/svc_auth.h sunrpc/rpc/types.h sunrpc/rpc/xdr.h sunrpc/rpcsvc/bootparam.h sysvipc/sys/ipc.h sysvipc/sys/msg.h sysvipc/sys/sem.h sysvipc/sys/shm.h termios/termios.h termios/sys/termios.h termios/sys/ttychars.h time/time.h time/sys [09:37] /time.h time/sys/timeb.h wcsmbs/wchar.h wctype/wctype.h > /home/fabbione/glibc-2.5/build-tree/powerpc-libc/begin-end-check.out [09:37] this is all i can get [09:38] or you need to remind me how to scroll back in screen [09:40] C-a { [09:40] err [09:40] C-a [ [09:41] but I don't remember what begin-end-check.out is. [09:41] I can look in my i386 build logs. [09:41] Meh, they haven't started the test suite yet. [09:42] I'm fighting doko for CPU time on ronne. =) [09:43] jbailey: if we really need a running .17 to build glibc we need to talk to elmo for the buildd [09:44] Shouldn't need it on ppc. [09:44] Will certainly need it on parisc. [09:45] what about i386/amd64/sparc? [09:45] and ia64? [09:45] Mainstream arches should all be fine. [09:46] ok [09:46] Have to check with Dave on sparc to be certain. [09:46] But since their nptl port worked fine, I wouldn't expect that to change. [09:46] no.. [09:46] The rest of the arches all had corporate funding for their ports, so they got done early. [09:47] ok.. i killed the build on ppc.. waiting Znarl to kill some Zl processes leftover [09:47] and restart with debuild [09:50] jbailey: ppc will wait tomorrow [09:51] i need to get some sleep [09:52] fabbione: g'n! =) [09:52] night [09:53] seems like I was right [09:53] building kernel with old gcc [09:53] made it work