Re: [OE-core] [PATCH] libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-09-27 Thread Richard Purdie
On Thu, 2013-09-26 at 18:40 -0400, Denys Dmytriyenko wrote: On Tue, Feb 12, 2013 at 01:36:44PM -0600, Jason Wessel wrote: If you never use sstate and always build everything from scratch you will never see this problem. However, if you use sstate and build directories that last a long time

Re: [OE-core] [PATCH] libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-09-27 Thread Richard Purdie
On Fri, 2013-09-27 at 10:20 +0100, Richard Purdie wrote: On Thu, 2013-09-26 at 18:40 -0400, Denys Dmytriyenko wrote: On Tue, Feb 12, 2013 at 01:36:44PM -0600, Jason Wessel wrote: If you never use sstate and always build everything from scratch you will never see this problem. However, if

Re: [OE-core] [PATCH] libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-09-27 Thread Denys Dmytriyenko
On Fri, Sep 27, 2013 at 11:06:42AM +0100, Richard Purdie wrote: On Fri, 2013-09-27 at 10:20 +0100, Richard Purdie wrote: On Thu, 2013-09-26 at 18:40 -0400, Denys Dmytriyenko wrote: On Tue, Feb 12, 2013 at 01:36:44PM -0600, Jason Wessel wrote: If you never use sstate and always build

Re: [OE-core] [PATCH] libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-09-26 Thread Denys Dmytriyenko
On Tue, Feb 12, 2013 at 01:36:44PM -0600, Jason Wessel wrote: If you never use sstate and always build everything from scratch you will never see this problem. However, if you use sstate and build directories that last a long time eventually you can end up with the scenario where libtool gets

[OE-core] [PATCH] libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-02-12 Thread Jason Wessel
If you never use sstate and always build everything from scratch you will never see this problem. However, if you use sstate and build directories that last a long time eventually you can end up with the scenario where libtool gets a hard coded path in it for sed, and sed may not exist. The

Re: [OE-core] [PATCH] libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-02-12 Thread Richard Purdie
On Tue, 2013-02-12 at 13:36 -0600, Jason Wessel wrote: If you never use sstate and always build everything from scratch you will never see this problem. However, if you use sstate and build directories that last a long time eventually you can end up with the scenario where libtool gets a hard

Re: [OE-core] [PATCH] libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-02-12 Thread Richard Purdie
On Tue, 2013-02-12 at 16:03 -0600, Jason Wessel wrote: On 02/12/2013 03:39 PM, Richard Purdie wrote: On Tue, 2013-02-12 at 13:36 -0600, Jason Wessel wrote: If you never use sstate and always build everything from scratch you will never see this problem. However, if you use sstate and build

Re: [OE-core] [PATCH] libtool-native_2.4.2.bb: Always use /bin/sed for SED

2013-02-12 Thread Khem Raj
On Tue, Feb 12, 2013 at 2:53 PM, Richard Purdie richard.pur...@linuxfoundation.org wrote: On Tue, 2013-02-12 at 16:03 -0600, Jason Wessel wrote: On 02/12/2013 03:39 PM, Richard Purdie wrote: On Tue, 2013-02-12 at 13:36 -0600, Jason Wessel wrote: If you never use sstate and always build