[oe] [oe,RFC,v2] Alternative to busybox, using "proper tools"

Did anything ever happen with this[1] patch? If not, is there another convenient way to use the proper tools in leiu of busybox? For larger machines it's very nice to have a more civilized environment. Thanks, - Ben ___ Openembedded-devel mailing list

[oe] [PATCH] boost: Change HOST_* to BUILD_*

It seems the HOST_* variables no longer exist? --- recipes/boost/boost-with-bjam.inc |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/recipes/boost/boost-with-bjam.inc b/recipes/boost/boost-with-bjam.inc index 68d9e74..dd0a3a3 100644 --- a/recipes/boost/boost-with-bjam.in

Re: [oe] Dealing with ttyS -> ttyO rename on OMAP3 in 2.6.37

On Tue, 18 Jan 2011 23:07:14 +0100, Koen Kooi wrote: > The machine maintainer should know which kernel is going to get used and > can change the machine.conf accordingly. > For example, I will change the beagleboard one once the .37 kernel is > considered good enough (it's currently lacking ISP su

[oe] Dealing with ttyS -> ttyO rename on OMAP3 in 2.6.37

As you may know, the kernel's OMAP serial driver has been fixed in 2.6.37 to move away from the ttyS naming towards the OMAP-specific ttyO prefix. This was done in light of the fact that ttyS is apparently reserved for traditional PC-style serial controllers. I've spent the last day or two trying

[oe] Using native package build tree when building target package

Today I've been looking at the icu package, which is quite out-of-date in the repository. Unfortunately, it seems that the latest version (4.6) requires that the absolute path to a source tree built for the host be passed to configure. Does anyone have any clever ideas concerning how this might be

[oe] [PATCH] boost: Initial commit of 1.45.0

--- .../01-fix-default-python-config.patch | 29 recipes/boost/boost-with-bjam.inc | 164 recipes/boost/boost_1.45.0.bb | 15 ++ 3 files changed, 208 insertions(+), 0 deletions(-) create mode 100644 recipes/boost/bo

[oe] [PATCH] boost: Initial commit of 1.45.0

--- .../01-fix-default-python-config.patch | 29 recipes/boost/boost-with-bjam.inc | 164 recipes/boost/boost_1.45.0.bb | 15 ++ 3 files changed, 208 insertions(+), 0 deletions(-) create mode 100644 recipes/boost/bo

[oe] Boost 1.45

For a long time, the newest version of boost in openembedded has been 1.41, released over two years ago. As far as I can tell, the reason for this is that the recipe uses the cmake branch, which has been stagnant for the last several years. The reason for this is that the build system used by boos

[oe] Python 2.7.1 support

I spent a few hours over the last few days forward porting the python 2.6 recipes to 2.7.1. At this point I can build both python-native and python on for my ARM target. I don't have time or access to hardware at the moment so I can't test the produce binaries but I figured I'd send this out in th

[oe] Wiki spam

Can someone with the ability please delete the following spam pages on the Wiki? http://www.openembedded.org/index.php/Acai_-_acai_berry_detox_discount_orders_-_extreme_acai_fatburn http://www.openembedded.org/index.php/Ashwagandha_-_ashwagandha_withania_somnifera_-_ashwagandha_erectile http://www

[oe] Kernel build under meta-toolchain SDK fails

Hey all, Recently I tried updating our openembedded environment for an embedded application built around the BeagleBoard. Unfortunately, the build failed while configuring the kernel with an inexplicable bus error. To trace down the issue I installed the latest meta-toolchain sdk and tried buildin