From: Tom Rini <tom_rini@mentor.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: eggdbus build failure in master
Date: Mon, 20 Jun 2011 15:59:00 -0700 [thread overview]
Message-ID: <4DFFD0B4.2070002@mentor.com> (raw)
In-Reply-To: <BANLkTinGcZQ1x+ZA-iY5uGVN3OokNxA95w@mail.gmail.com>
On 06/20/2011 03:57 PM, Khem Raj wrote:
> On Mon, Jun 20, 2011 at 3:51 PM, Tom Rini <tom_rini@mentor.com> wrote:
>> On 06/20/2011 01:20 PM, Darren Hart wrote:
>>> I'm seeing a consistent eggdbus build failure that seems to be related
>>> to the perl-native relocation. I've cleanall'd autoconf and automake,
>>> native and target versions. The failure persists.
>>>
>>> Anyone have any ideas on how to get this building? I'll start a clean
>>> build in another directory for now.
>>
>> It's a glib problem, you need to switch glib-mkenums to using
>> /usr/bin/env perl (you're building in too deep a path for #! to work
>> with the full path to perl-native).
>>
>
> you mean import from oe
>
> commit c63403cb9c02641476f9e275fb2e63bb54f5e46d
> Author: Tom Rini <tom_rini@mentor.com>
> Date: Thu Nov 18 06:38:28 2010 -0700
>
> glib-2.0: Fix glib-mkenums to use /usr/bin/env perl
>
> Signed-off-by: Tom Rini <tom_rini@mentor.com>
Yes, that one and probably a few others where I said '/usr/bin/env perl'
in the git log for fixing deep-path builds. Thanks :)
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-06-20 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 20:20 eggdbus build failure in master Darren Hart
2011-06-20 22:51 ` Tom Rini
2011-06-20 22:57 ` Khem Raj
2011-06-20 22:59 ` Tom Rini [this message]
2011-06-21 6:35 ` [poky] " Koen Kooi
2011-06-21 6:35 ` Koen Kooi
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=4DFFD0B4.2070002@mentor.com \
--to=tom_rini@mentor.com \
--cc=poky@yoctoproject.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.