/srv/irclogs.ubuntu.com/2005/05/22/#ubuntu-toolchain.txt

jbaileylamont: ping when you're back.12:38
jbaileyThe 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:03
jbaileyI'll check my mail tomorrow sometime, and then I'll be online Sunday evening.02:04
=== jbailey heads off.
svenldoko: well, all tests failed again, but the package built, except for libgcc1 and co, it seems.06:13
svenldoko: correction, some tests failed.06:14
svenldoko: i guess the 64bit tests failed, and that is the problem, message is -m64 not supported in this configuration.06:16
svenloh well.06:17
=== ogra [~ogra@p5089E62A.dip.t-dialin.net] has joined #ubuntu-toolchain
lamontWARNING: The following essential packages will be removed06:06
lamontThis should NOT be done unless you know exactly what you are doing!06:06
lamont  apt dpkg dselect (due to dpkg) sysvinit initscripts (due to sysvinit)06:06
=== lamont smacks jbailey and doko
lamontI wonder if I can just force dpkg to do the install and tweak /var/lib/dpkg/status to lie about the version number06:07
lamontwell, off to get out of trouble with the wife for a few hours06:07
doko?06:08
lamonttrying to install the debian gcc-3.4 bits to build the glibc jbailey has for me.06:11
lamontdowngrades libgcc1, causing all those packages to be selected for removal.  -> bummer06:11
lamontbut must run for a bit - was just going to start the first step before I ran away.06:11
lamontthe debian version is newer than hoary?06:12
lamontno.  hoary had libgcc1=4.0-0pre6ubuntu706:13
lamontgrumble06:13
lamontanyway, 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
svenllamont: :)06:14
svenllamont: i had also trouble with that.06:14
svenldoko: you there ? 09:15
svenldoko: something funny happened.09:15
dokosvenl: really funny?09:16
svenldoko: 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
svenldoko: yep.09:16
dokofind build -name libgcc1_* ?09:17
svenldoko: how do you come clear with this huge build log ?09:17
svenldoko: doesn't find anything such.09:17
svenlthere are a couple libgcc.a and libgcc_s.so in build/gcc though.09:18
dokosorry, find build -name libgcc_* ?09:18
svenl$ find build -name libgcc\*09:19
svenlbuild/gcc/libgcc09:19
svenlbuild/gcc/libgcc/nof/libgcc.map09:19
svenlbuild/gcc/libgcc/libgcc.map09:19
svenlbuild/gcc/nof/libgcc.a09:19
svenlbuild/gcc/nof/libgcc_eh.a09:19
svenlbuild/gcc/libgcc.a09:19
svenlbuild/gcc/libgcc_eh.a09:19
svenlbuild/gcc/libgcc_s.so.1.backup09:19
svenlbuild/gcc/libgcc_s.so.109:19
svenlbuild/gcc/libgcc_s_nof.so.1.backup09:19
svenlbuild/gcc/libgcc_s_nof.so.109:19
svenlbuild/gcc/libgcc_s_nof.so09:19
svenlbuild/gcc/libgcc.mk09:19
svenlbuild/gcc/libgcc_s.so09:19
dokohmm, no 64bit libgcc ...09:20
dokoor is this 4.0 for experimental?09:21
svenlthe fun thing is that not even the 32bit libgcc did build.09:21
svenlno, the ubuntu gcc-3.409:21
svenldoko: any hint on what i could be looking at there ?09:29
dokohmm, no currently not.09:33
svenlcan i try building the libgcc stuff without rebuilding the whole stuff ? To get a smaller log or something.09:34
dokough, 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:35
svenldoko: 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:36
dokoand the lib64stdc++6 does contain a shared lib?09:38
svenlnope, its empty.09:38
svenland there is no non-64bit libstdc++ now that i look at it.09:39
svenlstrange.09:39

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