[12:38] lamont: ping when you're back. [02:03] The glibc is on chinstrap in my homedir. Builds here. The only thing you need is a current breezy chroot and gcc-3.4 from Debian. [02:04] I'll check my mail tomorrow sometime, and then I'll be online Sunday evening. === jbailey heads off. [06:13] doko: well, all tests failed again, but the package built, except for libgcc1 and co, it seems. [06:14] doko: correction, some tests failed. [06:16] doko: i guess the 64bit tests failed, and that is the problem, message is -m64 not supported in this configuration. [06:17] oh well. === ogra [~ogra@p5089E62A.dip.t-dialin.net] has joined #ubuntu-toolchain [06:06] WARNING: The following essential packages will be removed [06:06] This should NOT be done unless you know exactly what you are doing! [06:06] apt dpkg dselect (due to dpkg) sysvinit initscripts (due to sysvinit) === lamont smacks jbailey and doko [06:07] I wonder if I can just force dpkg to do the install and tweak /var/lib/dpkg/status to lie about the version number [06:07] well, off to get out of trouble with the wife for a few hours [06:08] ? [06:11] trying to install the debian gcc-3.4 bits to build the glibc jbailey has for me. [06:11] downgrades libgcc1, causing all those packages to be selected for removal. -> bummer [06:11] but must run for a bit - was just going to start the first step before I ran away. [06:12] the debian version is newer than hoary? [06:13] no. hoary had libgcc1=4.0-0pre6ubuntu7 [06:13] grumble [06:14] anyway, I need a working set of packages to build the glibc bits with. I'll let you two ponder that until I get back in a few hours. [06:14] lamont: :) [06:14] lamont: i had also trouble with that. [09:15] doko: you there ? [09:15] doko: something funny happened. [09:16] svenl: really funny? [09:16] doko: some of the tests failed, but not all, the package build a couple of .debs (most of them i think, including lib64stdc++ and gcc) but no trace of any libgcc1 or libgcc1_64. [09:16] doko: yep. [09:17] find build -name libgcc1_* ? [09:17] doko: how do you come clear with this huge build log ? [09:17] doko: doesn't find anything such. [09:18] there are a couple libgcc.a and libgcc_s.so in build/gcc though. [09:18] sorry, find build -name libgcc_* ? [09:19] $ find build -name libgcc\* [09:19] build/gcc/libgcc [09:19] build/gcc/libgcc/nof/libgcc.map [09:19] build/gcc/libgcc/libgcc.map [09:19] build/gcc/nof/libgcc.a [09:19] build/gcc/nof/libgcc_eh.a [09:19] build/gcc/libgcc.a [09:19] build/gcc/libgcc_eh.a [09:19] build/gcc/libgcc_s.so.1.backup [09:19] build/gcc/libgcc_s.so.1 [09:19] build/gcc/libgcc_s_nof.so.1.backup [09:19] build/gcc/libgcc_s_nof.so.1 [09:19] build/gcc/libgcc_s_nof.so [09:19] build/gcc/libgcc.mk [09:19] build/gcc/libgcc_s.so [09:20] hmm, no 64bit libgcc ... [09:21] or is this 4.0 for experimental? [09:21] the fun thing is that not even the 32bit libgcc did build. [09:21] no, the ubuntu gcc-3.4 [09:29] doko: any hint on what i could be looking at there ? [09:33] hmm, no currently not. [09:34] can i try building the libgcc stuff without rebuilding the whole stuff ? To get a smaller log or something. [09:35] ugh, you may want to look at gcc/Makefile, where it builds libgcc, but if the compiler isn't configured for 64bit, then that won't help at all ... [09:36] doko: what i don't understand is why : 1) the 32bit libgcc didn't build, or 2) why the whole lot of other .debs where built. [09:38] and the lib64stdc++6 does contain a shared lib? [09:38] nope, its empty. [09:39] and there is no non-64bit libstdc++ now that i look at it. [09:39] strange.