Re: [OE-core] SDK relocation issues

2013-06-11 Thread Tasslehoff Kjappfot
On 06/11/2013 03:24 PM, Laurentiu Palcu wrote:> On Tue, Jun 11, 2013 at 03:09:49PM +0200, Tasslehoff Kjappfot wrote: >> >> I have time for one more :) >> >> What does it mean that the SDK is relocatable? That I can choose >> when I run the .sh where I want to

Re: [OE-core] SDK relocation issues

2013-06-11 Thread Tasslehoff Kjappfot
On 06/11/2013 02:43 PM, Laurentiu Palcu wrote: Hi Tasslehoff, On Tue, Jun 11, 2013 at 11:35:26AM +0200, Tasslehoff Kjappfot wrote: I compiled an SDK and extracted/installed it to my source tree instead of /usr/local/. I have made /usr/local/oecore-i686 a symlink to the actual location. With

Re: [OE-core] SDK relocation issues

2013-06-11 Thread Tasslehoff Kjappfot
Hi Laurentiu. I just saw your mail, but won't have time to investigate until tomorrow. Just wanted to add one comment. * denzil did not support relocation and you could only install the sdk in /usr/local; In denzil I extracted the SDK to /home/tasslehoff/src/oe/toolchains/oecore-i686,

[OE-core] SDK relocation issues

2013-06-11 Thread Tasslehoff Kjappfot
I compiled an SDK and extracted/installed it to my source tree instead of /usr/local/. I have made /usr/local/oecore-i686 a symlink to the actual location. With the latest Dylan this broke. Denzil: ❯❯❯ ldd arm-angstrom-linux-gnueabi-gcc linux-gate.so.1 => (0xf771d000) libc.so.6 => /lib

Re: [OE-core] Generating a movable SDK

2012-07-03 Thread Tasslehoff Kjappfot
On 06/20/2012 08:03 AM, Tasslehoff Kjappfot wrote: On 06/19/2012 10:33 PM, Khem Raj wrote: On Tuesday, June 19, 2012, Steve English mailto:steve.engl...@navetas.com>> wrote: > Hi, > I've generated a cross compiling ARM SDK (angstrom-eglibc-x86_64-armv7a-v2012.05-toolch

Re: [OE-core] Generating a movable SDK

2012-06-19 Thread Tasslehoff Kjappfot
On 06/19/2012 10:33 PM, Khem Raj wrote: On Tuesday, June 19, 2012, Steve English mailto:steve.engl...@navetas.com>> wrote: > Hi, > I've generated a cross compiling ARM SDK (angstrom-eglibc-x86_64-armv7a-v2012.05-toolchain.tar.bz2) that works great if installed in /usr/local/oecore-x86_64. I w

[OE-core] [PATCH] boost: set python-root correctly

2012-04-24 Thread Tasslehoff Kjappfot
Signed-off-by: Tasslehoff Kjappfot --- meta/recipes-support/boost/boost.inc | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc index c9306df..5341a8c 100644 --- a/meta/recipes-support

[OE-core] [PATCH] boost: set python-root correctly

2012-04-24 Thread Tasslehoff Kjappfot
--- meta/recipes-support/boost/boost.inc |8 +++- meta/recipes-support/boost/boost_1.49.0.bb |2 +- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/meta/recipes-support/boost/boost.inc b/meta/recipes-support/boost/boost.inc index c9306df..fbdf292 100644 --- a/meta

Re: [OE-core] Error compiling Boost with Python support on 64-bit host for 32-bit target.

2012-04-24 Thread Tasslehoff Kjappfot
On 04/24/2012 11:44 AM, Richard Purdie wrote: On Tue, 2012-04-24 at 23:02 +0200, Tasslehoff Kjappfot wrote: boost.inc: # To enable python, uncomment the following: #BOOST_LIBS += "python" #DEPENDS += "python" #PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}" #PYTH

Re: [OE-core] Error compiling Boost with Python support on 64-bit host for 32-bit target.

2012-04-24 Thread Tasslehoff Kjappfot
Ouch. Didn't mean to make this a part of another thread. Sorry about that. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

[OE-core] Error compiling Boost with Python support on 64-bit host for 32-bit target.

2012-04-24 Thread Tasslehoff Kjappfot
boost.inc: # To enable python, uncomment the following: #BOOST_LIBS += "python" #DEPENDS += "python" #PYTHON_ROOT = "${STAGING_DIR_HOST}/${prefix}" #PYTHON_VERSION = "2.5" If this is uncommented, stuff fails with messages like: | ...failed gcc.compile.c++ bin.v2/libs/python/build/69ffc88faf507

Re: [OE-core] GCC fails when SDK is not extracted to /usr/local

2011-12-08 Thread Tasslehoff Kjappfot
On Dec 8, 2011, at 3:56 PM, Tom Rini wrote: > On Wed, Dec 7, 2011 at 12:16 AM, Tasslehoff Kjappfot > wrote: >> gcc fails when I extract my SDK to another place than /usr/local. >> >> Output when it fails: >> >> $ ./arm-angstrom-linux-gnueabi-gcc >>

[OE-core] GCC fails when SDK is not extracted to /usr/local

2011-12-06 Thread Tasslehoff Kjappfot
gcc fails when I extract my SDK to another place than /usr/local. Output when it fails: $ ./arm-angstrom-linux-gnueabi-gcc bash: ./arm-angstrom-linux-gnueabi-gcc: No such file or directory Readelf output: $ readelf -d arm-angstrom-linux-gnueabi-gcc Dynamic section at offset 0x34394 contains 2

Re: [OE-core] Workaround to compile linux-omap_2.6.39.bb?

2011-10-05 Thread Tasslehoff Kjappfot
> OE-Core uses fetch2 and that is a tarball from fetch1. You'd need to > convert that tarball into the form that fetch2 expects and rename it, > then you stand some chance of it working. > > Also note that your recipes needs to be using a fixed source revision > and that revision needs to be pres

[OE-core] Workaround to compile linux-omap_2.6.39.bb?

2011-10-05 Thread Tasslehoff Kjappfot
I need to compile linux-omap_2.6.39.bb, but it fails since the tmlind-repos are not currently on kernel.org. I have downloaded git_git.kernel.org.pub.scm.linux.kernel.git.tmlind.linux-omap-2.6.git_v2.6.39.tar.gz from the angstrom mirrors. Can I extract that into my downloads/ in a way that wi