-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Please cc me, I'm not registered to the list.] Hello, I try to write a little toy kernel for ppc64 and ia64, mainly to get to know the architectures. Actually this message is about 2 question, one the one hand, they're tightly related, on the other hand they're relatively different (therefore I wasn't sure whether to send 2 messages or not). The first question is about what target to build in my case. Conceptually I want a completely OS-independant toolchain only consisting of binutils and a C compiler, but which target expresses this? <target>-unknown-unknown doesn't work (system not recognized). For ppc64, the following configuration options seem to do what I want: "--prefix=... --target=powerpc64-unknown-linux-gnu --enable-languages=c - --disable-shared --disable-threads --without-headers --disable-libssp - --disable-libmudflap". But the ia64 cross toolchains thing seems to be even more tricky. For what I know it depends on glibc (depending on kernel-headers?), but I definitely don't want glibc. I don't think it is conceptually right to depend on linux kernel headers or glibc headers if neither is used. So what should one pass here? I tried some options (--target=ia64-unknown-elf, --with-newlib) to workaround this, without success (always problems compiling fde-glibc.c obviously related to headers [stdlib.h, link.h] not found). Thanks for any help. - -- - -ness- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEuAxEvD/ijq9JWhsRAn5GAJ9BSluP6Li/DjKYeSKDPAlNmG2dGACeIK3/ B0Tz1kWBuwbH0uyhvx+cbK4= =NT72 -----END PGP SIGNATURE-----
