Juanito


Group: Members
Posts: 1601
Joined: Sep. 2005 |
 |
Posted: Oct. 17 2007,12:30 |
 |
I after a "hiatus" on this story, I finally managed to compile glibc-2.3.2 - for some reason it needs about 800MB to compile for a 13MB tar.bz2 package...
So now I have gcc, binutils, glibc, m4, etc, etc compiled on dsl to /opt/build using a compile environment built from "sarge" debs (chosen because the "sarge" libc6 is closest to that of dsl). If I understand correctly, gcc requires "kernel headers" in addition to the glibc headers in order to be able to compile - I plan to take the headers from /include in the full 2.4.26 kernel sources - does this make the most sense in dsl terms?
|