From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] jpeg-native: Do not use libtool-cross for native recipe
Date: Thu, 27 Sep 2012 16:16:53 +0100 [thread overview]
Message-ID: <1348759013.8493.5.camel@ted> (raw)
In-Reply-To: <CAMKF1sqFe+8xmEg6r+g9+2xLo0TYyfGQp0aYOCT+kp-WHE03+A@mail.gmail.com>
On Thu, 2012-09-27 at 07:14 -0700, Khem Raj wrote:
> On Wed, Sep 26, 2012 at 6:59 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Tue, 2012-09-25 at 06:27 -0700, Khem Raj wrote:
> >> On Tue, Sep 25, 2012 at 1:14 AM, Richard Purdie
> >> <richard.purdie@linuxfoundation.org> wrote:
> >> > This wallpapers over cracks. Why is libtool-native/libtool-cross broken?
> >> > Shouldn't we fix whatever is breaking libtool?
> >> >
> >>
> >> it is not broken. But we were ending up using cross-libtool for native
> >> recipe that does not seem right.
> >
> > Looking at your original error message, it says:
> >
> > /work/yocto/poky/build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux-libtool
> >
> > which is libtool-native. I appreciate that the OEMAKE line to use the
> > cross version is wrong but it looks like it still manages to find the
> > native libtool and that it isn't working.
>
> hmmm I tried and it worked fine when libtool-cross was staged. I guess
> my problem was
> that it was trying to find native sed in native sysroot. I cant
> reproduce it. But I guess
> the patch still makes sense. I can send it with commit message changed
> if you are ok with that
I'm not really. I'd like to understand what the problem is we're fixing
before I take patches. We don't understand what is wrong here.
Cheers,
Richard
next prev parent reply other threads:[~2012-09-27 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 23:55 [PATCH] jpeg-native: Do not use libtool-cross for native recipe Khem Raj
2012-09-25 8:14 ` Richard Purdie
2012-09-25 13:27 ` Khem Raj
2012-09-26 13:59 ` Richard Purdie
2012-09-27 14:14 ` Khem Raj
2012-09-27 15:16 ` Richard Purdie [this message]
2012-09-27 15:44 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1348759013.8493.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.