Re: [Scratchbox-users] [Scratchbox2] How to use python setup.py build under scratchbox
Dear all, I have now generated a tools root but I think I have done something wrong because now is the sb2-init command not working correctly. I generated a qemux86 image with the angstrom online build system (Narcissus) this image should be basically the same as the image I have for my beagleboard but then for the i686 architecture. * hansan@mediachan:~/Beagelboard/angstrom_rootfs$ sb2-init -m devel -t /home/hansan/Beagelboard/i86_rootfs/ beagle_angstrom2 /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-gcc Using /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-gcc to detect target architecture: Reading mode-specific settings.. Finished writing sb2.gcc.config gcc configured. sb2-init: Target architecture is 'arm' sb2-init: Host architecture is 'i[3456]86' Reading mode-specific settings.. Finished writing sb2.config sb2-init: Creating Debian build system settings for this target: /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sb2-init: configuring libtool for this target: /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Running /home/hansan/sb2/bin/sb2-build-libtool failed You can run this manually later, otherwise your sb2 environment is correctly setup and ready to use* Probably there is something wrong with my tools root. I am also not able to call sb2 /home/hansan/sb2/bin/sb2-build-libtool successfully. *hansan@mediachan:~/Beagelboard/angstrom_rootfs$ sb2 /home/hansan/sb2/bin/sb2-build-libtool /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory* I think that the problem is that my tools root fs expect to be a real root fs and does not expect to reside in a directory. Probably that breaks some paths to libraries... Some idea how to fix this, or some tips on how to get a decent tools root. Kind regards, Han On Wed, Mar 16, 2011 at 12:12 PM, Han Hartgers han.hartg...@gmail.comwrote: Dear Lauri, Many thanks for the explanation. I did read about the tools root, but disregarded that as unimportant. Can you be a bit more specific about what this tools root should include? Should this file system include the same libraries and header files as the target rootfs? I can fairly easy generate a similar root file system for my beagleboard as for a i686 architecture and use the beagleboard one as target root file system and the i686 one as tool root. When they are both of the same version then I expect them to have the same files but different architectures. I will try how this goes and let you know. Greetings, Han On Tue, Mar 15, 2011 at 11:35 PM, Lauri T. Aarnio lauri.t.aar...@nokia.com wrote: On Mar 14, 2011, at 4:41 AM, ext Han Hartgers wrote: This is the relevant (?) output of the sb2-init command. configured at 2011-03-10_17:38:35 by user 'hansan', with command ( cd /home/hansan/Beagelboard/angstrom_rootfs; sb2-init beagle_angstrom /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-gcc ) I think that the problem is in the way how your target has been initialized; devel needs a separate tools root. There is something about it on the manual page, but maybe the description is too brief, and in any case, the fact that it is possible to use sb2 -m devel also when sb2-init was executed without the -t option can be classified as a bug. This is the relevant part from the man page (man sb2): The other two development modes, accel and devel have more complete support for different tools, but these are not necessarily as easy to set up as the simple mode is. Both accel and devel are intended to be used with a separate tools root directory, consisting of host-compatible binaries of the same programs that exist in the target file system as foreign binaries (e.g. target root can contain arm binaries, whereas tools root has x86 binaries of the exactly versions of the same programs). This is configured with the -t option of sb2-init(1). Lauri ___ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users ___ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
Re: [Scratchbox-users] [Scratchbox2] How to use python setup.py build under scratchbox
On Thu, Mar 17, 2011 at 1:05 AM, Lauri T. Aarnio lauri.t.aar...@nokia.comwrote: On Mar 16, 2011, at 5:12 AM, ext Han Hartgers wrote: Many thanks for the explanation. I did read about the tools root, but disregarded that as unimportant. long time ago it was possible to use devel without a separate tools root, I think. But obviously that haven't been tested lately, and on the other hand, it is a feature which isn't really useful anyway, as we have learned. I'll try to explain the history of these more complex mapping modes, devel and accel, hopefully that clarifies something: Removed a lot of text So, a built-in requirement of accel is that the set of tools is built from the exactly same sources that you are using in the target. Which is the only configuration that can be recommended anyway, as we have learned. Alternatively, devel can be used, but it should not offer any advantages over accel. (In fact, because I don't know any cases where accel would be worse than devel if the same-codebase-for-both requirement is met, I'm planning to drop the aging devel mode from the next major version of SB2) BTW, sb2 will be using the dynamic linker/loader (ld.so = ld-linux.so.*) from the tools root in accel and devel modes. There are some things that work better if you apply the patches that are shipped with SB2 and rebuild glibc; see external_patches/README for details. Many thanks for your extensive explanation. Maybe it would be nice to add this explanation to the wiki / website for future reference. I will have to recompile my tools root to get the patches included. This should be not too complictated by using the openembedded / angstrom build system. Kind regards, Han ___ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
Re: [Scratchbox-users] [Scratchbox2] How to use python setup.py build under scratchbox
On Mar 14, 2011, at 4:41 AM, ext Han Hartgers wrote: This is the relevant (?) output of the sb2-init command. configured at 2011-03-10_17:38:35 by user 'hansan', with command ( cd /home/hansan/Beagelboard/angstrom_rootfs; sb2-init beagle_angstrom /usr/local/angstrom/arm/bin/arm-angstrom- linux-gnueabi-gcc ) I think that the problem is in the way how your target has been initialized; devel needs a separate tools root. There is something about it on the manual page, but maybe the description is too brief, and in any case, the fact that it is possible to use sb2 -m devel also when sb2-init was executed without the -t option can be classified as a bug. This is the relevant part from the man page (man sb2): The other two development modes, accel and devel have more complete support for different tools, but these are not necessarily as easy to set up as the simple mode is. Both accel and devel are intended to be used with a separate tools root directory, consisting of host- compatible binaries of the same programs that exist in the target file system as foreign binaries (e.g. target root can contain arm binaries, whereas tools root has x86 binaries of the exactly versions of the same programs). This is configured with the -t option of sb2-init(1). Lauri ___ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
Re: [Scratchbox-users] [Scratchbox2] How to use python setup.py build under scratchbox
Dear Lauri, Many thanks for the explanation. I did read about the tools root, but disregarded that as unimportant. Can you be a bit more specific about what this tools root should include? Should this file system include the same libraries and header files as the target rootfs? I can fairly easy generate a similar root file system for my beagleboard as for a i686 architecture and use the beagleboard one as target root file system and the i686 one as tool root. When they are both of the same version then I expect them to have the same files but different architectures. I will try how this goes and let you know. Greetings, Han On Tue, Mar 15, 2011 at 11:35 PM, Lauri T. Aarnio lauri.t.aar...@nokia.comwrote: On Mar 14, 2011, at 4:41 AM, ext Han Hartgers wrote: This is the relevant (?) output of the sb2-init command. configured at 2011-03-10_17:38:35 by user 'hansan', with command ( cd /home/hansan/Beagelboard/angstrom_rootfs; sb2-init beagle_angstrom /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-gcc ) I think that the problem is in the way how your target has been initialized; devel needs a separate tools root. There is something about it on the manual page, but maybe the description is too brief, and in any case, the fact that it is possible to use sb2 -m devel also when sb2-init was executed without the -t option can be classified as a bug. This is the relevant part from the man page (man sb2): The other two development modes, accel and devel have more complete support for different tools, but these are not necessarily as easy to set up as the simple mode is. Both accel and devel are intended to be used with a separate tools root directory, consisting of host-compatible binaries of the same programs that exist in the target file system as foreign binaries (e.g. target root can contain arm binaries, whereas tools root has x86 binaries of the exactly versions of the same programs). This is configured with the -t option of sb2-init(1). Lauri ___ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users ___ Scratchbox-users mailing list Scratchbox-users@lists.scratchbox.org http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
