**** BEGIN LOGGING AT Wed May 21 02:59:58 2014 May 21 08:03:28 good morning May 21 08:41:08 morning all May 21 08:41:27 bluelightning, morning May 21 08:43:46 <__valle__> morning May 21 08:45:28 hi kroon, __valle__ May 21 12:38:38 Hi ! Once I build executables of nativesdk recipes, I try to execute one of them. For example, nativesdk-python/2.7.3-r0.3/image/ ... /usr/bin/python2.7 . I get "No such file or directory". file command tells me it's a x86_64 binary and it has exec rights. Why is it not working ? May 21 12:42:16 rbuchmann_: nativesdk recipes are intended to go into SDKs; so they are linked against their own libc rather than your system's May 21 12:43:24 so either build an SDK containing the package produced by the recipe and install that on your machine, or you could build the recipe as -native and then that would produce executables suitable for running on your machine directly May 21 12:43:48 I have some builds on other computer that works. I mean in some cases, I'm able to execute the binaries from nativesdk directory May 21 12:49:04 This is what I understand from the code : nativesdk is built to run on the building machine and should run as is if not moved. The generated sdk (.sh) is a compressed script that rellocate the binaries to be able to run from the new install. May 21 12:51:53 rbuchmann_: nativesdk is designed to work on a "third" machine which may or may not be the build machine May 21 12:53:19 Bluelighting: ok. Thx ! May 21 12:55:01 According to "file" command, my generated native executables are "for GNU/Linux 2.6.24". Generated nativesdk executables are "for GNU/Linux 2.6.16". Does anyone know why ? May 21 12:55:25 rbuchmann_: that comes from the libc the version is linked to May 21 12:55:46 rbuchmann_: there is an OLDEST_KERNEL variable in our system which sets that; the default value is "2.6.16" May 21 12:56:58 (roughly, it's supposed to control which kernel-version specific features are enabled in eglibc; whether it matters much in practice I'm not too sure) May 21 13:23:30 <_valle_> How can I make pulseaudio to startup at boot with the --system flag? May 21 13:23:44 "bitbake -e" tells me OLDEST_KERNEL variable is set but not used in anyway for the recipe (nativesdk-python) May 21 13:24:16 <_valle_> I have seen this in the pulseaudio.inc: USERADD_PARAM_pulseaudio-server = "--system --home /var/run/pulse May 21 13:25:06 rbuchmann_: it's used by eglibc, not by the individual recipe May 21 13:32:35 Where do I set the USERADD_PARAM_pulseaudio-server? May 21 13:51:04 _valle_: USERADD_PARAM is parameters for useradd, that —system means "create a system user" May 21 13:51:18 _valle_: if you want the system-wide daemon, i think you want pulseaudio-server May 21 13:51:42 i think you might need to write your own init script if that doesn't come with one out of the box May 21 20:05:20 hi there May 21 20:05:32 has anybody ever used minnowboard as a PXE/iSCSI server? **** BEGIN LOGGING AT Thu May 22 02:25:12 2014 **** ENDING LOGGING AT Thu May 22 02:59:58 2014