Since winkie banned me from #cross-lfs, I'll ask my questions here: I'm banging on a PPC with uClibc system to run under uClibc, starting from http://cross-lfs.org/view/1.0.0/ppc/ and I have a few questions.
1) page http://cross-lfs.org/view/1.0.0/ppc/cross-tools/variables.html This builds for the tuple "powerpc-unknown-linux" but what PPC variant is that? I'm guessing ppc7xx, not ppc4xx or any of the newer stuff? 2) page http://cross-lfs.org/view/1.0.0/ppc/cross-tools/linux-headers.html What's the deal with the "ppc" and "powerpc" /include/asm directories? I vaguely remember the kernel guys migrating stuff last year, but my question is about headers referring to /include/asm. The instructions say to make the powerpc-asm directory /include/asm, but _also_ to copy /include/ppc-asm into the kernel headers under that name? This is the first architecture I've seen that for, and I'm wondering what's going on. (Is there any backstory here?) (I then got to the point where it's building "hello world" against uClibc, which runs under qemu-ppc far enough to print hello world and then segfaults with a null pointer dereference on exit. I suspect this is a probably with recent uClibc svn snapshots, and I'm debugging it. I had a similar problem with the armv4l crt1.o exit code a month or two back. My problem, not yours...) Rob -- Vista: Windows Millenium Second Edition _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
