On 12/26/05, Ken Moffat <[EMAIL PROTECTED]> wrote: > I've been attempting to run an ICA on my CLFS ppc builds (CLFS from > 20051214, but modified to also build a minimal 64-bit toolchain in > /opt/kgcc because the cpu is a G5). So, my observations have very > little to do with the alphabetical branch per-se.
No big deal. Thanks for taking a look (you too, Tushar!). Although your building in a different direction, I think a lot of the alphabetical niggles can be figured out by a trained LFS eye. > Oh, and *some* examinations of ar archives in farce were broken again [ > not sure if this showed, other than in the runtime error messages ] - > fixed in farce-001-4 which is now available. I'll update. Thanks. > Anyway, you have differences in > > mkfs - ok for me, but my fsck.ext2 (and its other names) differed. Haven't tested, but diffing the two build logs shows that it pulls in gettext and doesn't detect xgettext and msgmerge since we do the mini gettext build in /tools. Maybe moving gettext before e2fsprogs will clear this up. Here's the diff (with my extra logging garbage snipped out): --- iter1/e2fsprogs-1.38.log 2005-12-22 22:33:48.000000000 -0800 +++ iter2/e2fsprogs-1.38.log 2005-12-23 01:05:18.000000000 -0800 @@ -99,10 +99,10 @@ checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether NLS is requested... yes -checking for msgfmt... /tools/bin/msgfmt -checking for gmsgfmt... /tools/bin/msgfmt -checking for xgettext... no -checking for msgmerge... no +checking for msgfmt... /usr/bin/msgfmt +checking for gmsgfmt... /usr/bin/msgfmt +checking for xgettext... /usr/bin/xgettext +checking for msgmerge... /usr/bin/msgmerge checking for ranlib... ranlib checking for strerror in -lcposix... no checking for an ANSI C-conforming const... yes > bison, perl, vim - for me, these differ between my second and third > builds, but not for my third and fourth, nor for the first and second - > I guess this is the whole point of ICA and the build will be assumed > guilty unless an explanation can be produced. Needs investigation. perl is a beast that I'll tackle another day. bison looks for bison and flex, but will build without it: @@ -75,12 +75,11 @@ checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ANSI C... (cached) none needed checking dependency style of gcc... (cached) gcc3 -checking for flex... no -checking for lex... no -checking for yywrap in -lfl... no -checking for yywrap in -ll... no -checking for bison... no -checking for byacc... no +checking for flex... flex +checking for yywrap in -lfl... yes +checking lex output file root... lex.yy +checking whether yytext is a pointer... yes +checking for bison... bison -y checking for ranlib... ranlib checking for gm4... no checking for gnum4... no DIY builds bison and flex in /tools, so maybe this is the reason I'm seeing the difference. Did LFS use to build bison and flex in /tools? I can't remember. I don't know about your oddities except for the obvious booted/chrooted situation. I'm gonna try to get flex linked into bison and see if that cleans up the differences. Do you think I should move flex up in Ch. 6 or add bison and flex to Ch. 5? > nscd - ok for me I'm having some weirdness with glibc. I think you may be right about not installing the locales for the purposes of ICA. I'm gonna change the locale installation to check for RUN_ICA in my scripts. DIY doesn't install any locales in the Referce Build and a note is shown that the need for locales to satisfy testsuites is deprecated. http://www.diy-linux.org/x86-reference-build/chroot.html#c-glibc > libstdc++.a and libsupc++.a - the anonymous namespaces. [ Note that > farce is content to match the corresponding .so files by running 'strip > --strip-all' - maybe that is hiding more than it should.] Agreed. Guess I have to determine whether that's the only diff, though. > locale-archive - I only see this differing when it is updated in place! > (that is, in ICA). The size for me with 'ls -l' is unchanged, so I'm > not particularly worried, seems to be a feature of reinstalling locales > in-situ. Possibly, a useful ICA run should never install locales (since > there is no 'expect', so it won't be running testsuites). I think you're right about that. I shut off the tests when doing ICA, anyway. Thanks for the input. I'll make a couple changes and blast off another build tomorrow. Please send me any suggestions you have. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
