-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Ken Moffat wrote:
> the builds on Monday (gcc-4.2.1) and Tuesday (gcc-4.2.0) seem to have
> been using a 2.6.22-rc1 kernel, but chroot was built against 2.6.22
> (release) headers, which might explain why each of them show an oops
> for 'touch'.

Well, so far I haven't seen anything like what you were describing.  I'm
building the current CLFS development book (aka what was on the web last
night and tonight), without any kind of automated process.  (Yeah, yeah,
I know, automation makes it way easier.  I still haven't settled on any
particular method yet, and plus copying and pasting from the browser
window makes me feel like I have some control over the process.  :-P )

Anyway, I got the /cross-tools and /tools stuff all built, and entered
chroot.  I set up the directories and symlinks and stuff, and before
starting the test-suite requirements (tcl/expect/dejagnu/tree), I tried
to build coreutils.  It built fine, though I didn't install it.

But this is running on 2.6.21.3, not 2.6.22*, so it's probably not a
great test either.  It is a multilib->multilib build, though (the host
is a CLFS from around 1.0.0rc3 or so).

I also haven't gone any farther than building coreutils inside chroot;
if you think it'd be good to see whether bash gives me any grief, I can
try to get that far at some point, hopefully tomorrow.  Or sometime in
the next couple days.

(What I *do* see are lots of warnings from a couple of glibc headers,
including /tools/include/sys/stat.h.  The warnings have something to do
with inlining functions and C89 vs. C99 rules; I assume these are
showing up for everyone, right?  I tried to decipher the sys/stat.h
header itself, and the warning lines were a mess of preprocessor chains.
__extern_inline, in particular, expands to something other than what I'd
expect if I run gcc -E (instead of -c) on su.c in coreutils, given the
output of "gcc -E -dM /dev/null".  Hopefully harmless?)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGsT9iS5vET1Wea5wRA+0eAKDE1Oy1h+v7X4XdxJ4OSYvVg4IGawCfbbyv
or3k9VUcpHlscK200CPpOYA=
=26dR
-----END PGP SIGNATURE-----
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev

Reply via email to