Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [REGRESSION] [PATCH] glib-1.2: merged native and non-native recipes
Date: Fri, 01 Oct 2010 07:05:56 -0700	[thread overview]
Message-ID: <4CA5EAC4.5020400@mentor.com> (raw)
In-Reply-To: <1285937266.4079.14.camel@mattotaupa>

Paul Menzel wrote:
> Dear Fahad, dear Tom,
> 
> 
> Am Donnerstag, den 09.09.2010, 11:31 +0200 schrieb Vitus Jensen:
> 
>> On Wed, 8 Sep 2010, Fahad Usman wrote:
>>
>>> * removed the glib-1.2-native_1.2.10.bb file
>>> * added NATIVE_INSTALL_WORKS = "1"
>>> * added BBCLASSEXTEND = "native"
>>> * converted do_stage of native recipe to do_install_virtclass-native in the combined recipe
>>> * added DEPENDS_virtclass-native = "" to avoid dependencies loops
>>> * added gettext in inherit because it was needed by the native recipes
>>> * bumped PR
>>>
>>> Signed-off-by: Fahad Usman <fahad_usman@mentor.com>
>>> ---
>>> recipes/glib-1.2/glib-1.2-native_1.2.10.bb |   49 ----------------------------
>>> recipes/glib-1.2/glib-1.2_1.2.10.bb        |   20 ++++++++++-
>>> 2 files changed, 18 insertions(+), 51 deletions(-)
>>
>>> diff --git a/recipes/glib-1.2/glib-1.2_1.2.10.bb b/recipes/glib-1.2/glib-1.2_1.2.10.bb
>>> index 72ee826..67266d4 100644
>>> --- a/recipes/glib-1.2/glib-1.2_1.2.10.bb
>>> +++ b/recipes/glib-1.2/glib-1.2_1.2.10.bb
>>> @@ -4,7 +4,8 @@ SECTION = "libs"
>>> PRIORITY = "optional"
>>> LICENSE = "LGPL"
>>> DEPENDS = "glib-1.2-native"
>>> -PR = "r4"
>>> +DEPENDS_virtclass-native = ""
>>> +PR = "r5"
>> I don't know if everyone thinks so but I feel the following line is more 
>> elegant:
>>
>> DEPENDS_pn-glib-1.2 += "glib-1.2-native"
>>
>> You skip the DEPENDS_virtclass-native line and may use the "+=" operator.
> 
> […]
> 
> Tom committed an updated patch in 44af05 [1]. Unfortunately building the
> recipe fails for me in `do_configure()`.
> 
>         […]
>         | checking for arm-oe-linux-gnueabi-gcc... arm-oe-linux-gnueabi-gcc -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
>         | checking whether the C compiler works... no
>         | configure: error: in `/oe/build-minimal-eglibc/minimal-dev/work/armv7a-oe-linux-gnueabi/glib-1.2-1.2.10-r5/glib-1.2.10':
>         | configure: error: C compiler cannot create executables
>         | See `config.log' for more details.
>         | ERROR: Function do_configure failed
>         NOTE: package glib-1.2-1.2.10-r5: task do_configure: Failed
>         […]
> 
> Do you know what might cause this? Reverting this commit the recipe can
> be build.

I just built it for angstrom-2008.1 / beagleboard (target and native). 
I've kicked off a minimal/eglibc/beagleboard build now.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-10-01 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 11:43 [PATCH] glib-1.2: merged native and non-native recipes Fahad Usman
2010-09-09  9:31 ` Vitus Jensen
2010-10-01 12:47   ` [REGRESSION] " Paul Menzel
2010-10-01 14:05     ` Tom Rini [this message]
2010-10-01 14:33       ` Tom Rini

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=4CA5EAC4.5020400@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox