Quote:
Originally Posted by spiky0011
|
Thanks. Ya, I did come across that CLFS config example in my efforts over the last week or so. I tried something similar and config ran ok but still get make/build errors that I don't quite yet understand.
Is it reasonable to assume that I can leave my existing system intact and build a secondary more up to date binutils, gcc, and both 32/64 bit glibc on that host without having to create a full chroot'd environment? I was just trying to --prefix everything to some directory under my home as the root for the tool chain. I tried both 1) cross-compiling with specific --host, --target, and --build specs and 2) just letting config decide on those parameters. I did get binutils, gcc, and glibc to build and seemingly work all as 64 bit. I had some old apps that had some 32 bit code and wouldn't link with that new glibc. I tried various options for configuring/building glibc as 32 bit but there were unknown data structures/types encountered during make that I couldn't seem to find anywhere. Anyway, is my approach even reasonable/do-able?
Thanks again.