Hello,
I'm a pretty recent T2 user. I have created HTPC Linux distro and so far it was a sort of spinoff of "Puppy" Linux distro. However, in the end "stock Puppy distro" was so heavily modified and customized that "HTPC" version started to live life ot its own. I started to look for easy way to build to HTPC distro from ground up to make sure that everything is optimized for HTPC usage and nothing else. I was comparing LFS and T2 projects and eventually I decided I'm going to use T2 project. Looks like people around T2 project have done a lot I no longer need to do manually. Good work. I have re-compiled "everything" in T2 (svn t2-trunk version) and compiling packages seems to work OK. However, I'm having a bit of troubles compiling a new initrd system using Busybox binaries (the real target system uses "real binaries" and not busybox replacements). My "htpc customized" target doesn't include busybox in list of included packages because the "live" distro doesn't use busybox. Therefore I compiled busybox package as a separate command. I compiled my "normal" target using following command: ./scripts/Build-Target -cfg vdrhtpc This went just fine but I cannot use the "stock" T2 initrd so I used only binary packages from this compilation (and I know there seem to be udev issue with t2-trunk version and initrd bootscripts). Then I downloaded and compiled busybox sources using following commands: ./scripts/Download busybox ./scripts/Build-Pkg -cfg vdrhtpc busybox Downloading went just fine and compilation seem to go just fine but then catastrofen stroke. Build-Pkg command didn't install busybox binaries to "chrooted" environment but instead to "live linux" system and overwriting all my normal binaries in development environment (had to re-install my Linux but at least I got rid of all unnecessary stuff accumulated into it :-) ). What did I do wrong? Probably a lot but is there something special I need to do if I compile single package (not part of normal target packages list) and NOT want it to install binaries over live Linux system? Now when I think of this then probably installing busybox binaries over the "chrooted" vdrhtpc TOOLCHAIN/rootfs system would have been equally wrong result but naturally less hazardous. Is the right way to create a new target specific for a this "initrd" compilation? Or can I create instruct T2 to prepare the Busybox source directory (all T2 magic with patches etc) and just compile the package but not install (not live linux and not into chrooted target rootfs)? Or even instruct T2 to prepate Busybox source directory and then manually compiling (make) sources and skipping "make install" step? Thanks in advance and best regards, Mike N -- View this message in context: http://www.nabble.com/Busybox-compilation-installed-binaries-to-%22real%22-Linux-and-not-to-chrooted-%22T2-Linux%22-tp14249992p14249992.html Sent from the T2 mailing list archive at Nabble.com. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
