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: Tue, 25 Sep 2012 09:14:38 +0100 [thread overview]
Message-ID: <1348560878.8662.29.camel@ted> (raw)
In-Reply-To: <1348530910-9917-1-git-send-email-raj.khem@gmail.com>
On Mon, 2012-09-24 at 16:55 -0700, Khem Raj wrote:
> This fixes errors when building native recipes like below
> Additionally fix some space issues.
>
> /work/yocto/poky/build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux-libtool:
> line 981: /work/yocto/poky/build/tmp/sysroots/x86_64-linux//bin/sed: No
> such file or directory
> | x86_64-linux-libtool: compile: Failed to create `.libs'
> | make[1]: *** [jaricom.lo] Error 1
> | make[1]: *** Waiting for unfinished jobs....
> |
> /work/yocto/poky/build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux-libtool:
> line 981: /work/yocto/poky/build/tmp/sysroots/x86_64-linux//bin/sed: No
> such file or directory
> |
> /work/yocto/poky/build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux-libtool:
> line 981: /work/yocto/poky/build/tmp/sysroots/x86_64-linux//bin/sed: No
> such file or directory
> | x86_64-linux-libtool: compile: Failed to create `.libs'
> | x86_64-linux-libtool: compile: Failed to create `.libs'
This wallpapers over cracks. Why is libtool-native/libtool-cross broken?
Shouldn't we fix whatever is breaking libtool?
Cheers,
Richard
next prev parent reply other threads:[~2012-09-25 8:27 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 [this message]
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
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=1348560878.8662.29.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.