"Frank W. Miller" wrote: > I'm not sure why I would need to have a different libc. I'm going to run > the cross compiler and binutils on my Linux box. I only want to use them to > generate an x86_64 binary kernel that I'll boot on another machine. > Wouldn't the cross compiler just use the fc8 libc to do its work? I'm talking about target libs not host libs. > May I assume you're talking about providing some libc functionality for the > target? If that's the case, the kernel is standalone, i.e. its built using > --freestanding. That way no other libs get linked in except what I specify > exactly. Okay, I thought you were saying you had the kernel and wanted to start on the userspace. If it's freestanding then you can skip building libgcc which eliminates the need for a target libc. You can either just do the standard "make all" and let it error at libgcc or you can do "make all-gcc" which builds just the compiler. Brian
