All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Bogdan Marinescu : autoconf: updated to 2.69
Date: Mon, 06 Aug 2012 15:24:18 +0100	[thread overview]
Message-ID: <1344263058.9756.166.camel@ted> (raw)
In-Reply-To: <20120806134521.GK3267@jama.jama.net>

On Mon, 2012-08-06 at 15:45 +0200, Martin Jansa wrote:
> On Wed, Jul 25, 2012 at 02:18:11PM +0200, Martin Jansa wrote:
> > On Sun, Jul 22, 2012 at 10:44:06AM +0000, git@git.openembedded.org wrote:
> > > Module: openembedded-core.git
> > > Branch: master
> > > Commit: effb75d42098b3e367d393215fd5d52a0191e954
> > > URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=effb75d42098b3e367d393215fd5d52a0191e954
> > > 
> > > Author: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
> > > Date:   Thu Jul 19 13:33:52 2012 +0300
> > > 
> > > autoconf: updated to 2.69
> > > 
> > > Tested with core-image-sato-sdk and lib32-core-image-sato-sdk.
> > > This update was done mainly because multilib builds failed on master with this error:
> > > 
> > > | autoreconf: running: aclocal -I /poky/build/tmp/work/x86-pokymllib32-linux/lib32-automake-1.12.1-r0/automake-1.12.1/m4/ -I /poky/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.12 -I /poky/build/tmp/work/x86-pokymllib32-linux/lib32-automake-1.12.1-r0/automake-1.12.1/aclocal-copy/ -I /poky/build/tmp/work/x86-pokymllib32-linux/lib32-automake-1.12.1-r0/automake-1.12.1/m4/ -I /poky/build/tmp/sysroots/x86_64-linux/usr/share/aclocal-1.12 -I /poky/build/tmp/work/x86-pokymllib32-linux/lib32-automake-1.12.1-r0/automake-1.12.1/aclocal-copy/ --force --warnings=cross
> > > | aclocal: warning: unknown warning category 'cross'
> > > | configure.ac:18: error: Autoconf version 2.69 or higher is required
> > 
> > since this upgrade I see autom4te segfaulting when building webkit-efl
> > autom4te[8513]: segfault at 29e782688 ip 00007f7c52a96e23 sp 00007fff07731020 error 4 in Dumper.so[7f7c52a90000+8000]
> > 
> > webkit-efl build finishes fine and is usable afaik but someone would
> > expect tools like autoconf to behave better and not segfault.
> > 
> > This happens on 2 different builders each with different webkit-efl
> > version.
> 
> Nobody else have seen this in dmesg? It happens quite often and probably
> not only while building webkit-efl. Because I don't build webkit-efl so
> often:
> dmesg | grep -c "segfault at.*Dumper.so"
> 37
> 
> It could be related to perl as Dumper.so is part of perl install
> dev-lang/perl-5.16.0 (/usr/lib64/perl5/5.16.0/x86_64-linux-thread-multi/auto/Data/Dumper/Dumper.so)
> 
> Maybe inheriting perlnative in autoconf would solve that too.

autoconf-native *must* use the system perl. Trying to do anything else
will result in circular dependencies.

Cheers,

Richard




      reply	other threads:[~2012-08-06 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120722104406.D46AB10330@opal>
2012-07-25 12:18 ` [oe-commits] Bogdan Marinescu : autoconf: updated to 2.69 Martin Jansa
2012-08-06 13:45   ` Martin Jansa
2012-08-06 14:24     ` Richard Purdie [this message]

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=1344263058.9756.166.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@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 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.