Some of the Puppy Linux guys are getting excited about the RaspberryPi board. See their site:
http://www.raspberrypi.org/ I have only ever used T2 to compile for x86, on PCs. But, I decided to give ARM a go. The RaspberryPi uses an arm1176jzf-s CPU, which T2 has an option for -- though it is strange, there are TWO entries for the same CPU in kconfig. I chose a generic + xorg + desktop, and compiling has been merrily going on, but stopped at the installation of Linux 3.0.7: ---------------------------- Running 'depmod -a -b /mnt/sda10/t2/t2-trunk-svn39804-28oct2011/build/raspi1-9.0-trunk-generic-arm-gnueabi-arm1176jzf-s-cross-linux/ -q -F /boot/System.map 3.0.7-dist' ... Kernel: 3.0.7-dist, module dir: /mnt/sda10/t2/t2-trunk-svn39804-28oct2011/build/raspi1-9.0-trunk-generic-arm-gnueabi-arm1176jzf-s-cross-linux/lib/modules/3.0.7-dist System.map: /mnt/sda10/t2/t2-trunk-svn39804-28oct2011/build/raspi1-9.0-trunk-generic-arm-gnueabi-arm1176jzf-s-cross-linux/boot/System.map_3.0.7-dist Create dirtree ... Copying kernel modules ... vfat.ko fat.ko nls_base.ko fat.ko nls_base.ko Injecting programs and configuration ... cp: cannot stat `/mnt/sda10/t2/t2-trunk-svn39804-28oct2011/build/raspi1-9.0-trunk-generic-arm-gnueabi-arm1176jzf-s-cross-linux/lib/udev/cdrom_id': No such file or directory Due to previous errors, no 1-linux26.log file! (Try enabling xtrace in the config to track an error inside the build system.) --- BUILD ERROR --- -------------------------------- I don't know what script is doing that cp operation, nor do I know if it is really necessary to copy 'cdrom_id', as I am only building binary tarballs. Anyway, I cheated, I got 'cdrom_id' out of a Debian ARM .deb package, and just stuck it into the build. Obviously though, a proper solution is required. Question 1: Udev is supposed to build that file, why didn't it? Question 2: If I don't really need that file (?), where can I disable that 'cp' operation? I would appreciate anyone's advice on this. Regards, Barry Kauler ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
