All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE Core mailing list <Openembedded-core@lists.openembedded.org>
Subject: Re: autom4te segfault in Dumper.so when configuring intltool
Date: Fri, 17 Apr 2015 08:15:36 +0100	[thread overview]
Message-ID: <1429254936.6976.191.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1soYC_BnMGv4Su5Z+6v1oFKpYCfRWvFxdnPXp9i04BAHHQ@mail.gmail.com>

On Thu, 2015-04-16 at 22:09 -0400, Khem Raj wrote:
> On Wed, Apr 15, 2015 at 5:37 PM, Andre McCurdy <armccurdy@gmail.com> wrote:
> >
> > Hiding OE sysroot perl when configuring intltool and using only host
> > perl does also prevent the segfault.
> >
> > I'm not sure what the correct fix is though. Perhaps have the
> > autoconf-native scripts run host perl via a wrapper which removes any
> > reference to OE sysroot perl from the PATH?
> 
> Not sure why Richard suggested that but may be his intention was to
> build automake-native early enough since perl takes a bit of time to
> build and it would serialize the build but we dont know unless we
> measure, may be there are enough native tools to build to keep
> processors spinning while its building perl-native
> in theory correct fix is to add dependency on perl native for autoconf
> native and do the necessary surgeries (if required to use perl-native)

autoconf-native is near enough one of the primary pieces of the
dependency chain. Having it depend on perl-native is a very very bad
idea, if its possible at all. It might be "correct" in principle but in
practise its not workable.

Cheers,

Richard





  reply	other threads:[~2015-04-17  7:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 21:34 autom4te segfault in Dumper.so when configuring intltool Andre McCurdy
2015-04-14 23:39 ` Martin Jansa
2015-04-15  2:05   ` Andre McCurdy
2015-04-15 10:08     ` Martin Jansa
2015-04-15 21:37       ` Andre McCurdy
2015-04-17  2:09         ` Khem Raj
2015-04-17  7:15           ` Richard Purdie [this message]
2015-04-17 15:28             ` 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=1429254936.6976.191.camel@linuxfoundation.org \
    --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.