From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gcc errors while building core-image-sato-sdk
Date: Fri, 06 Jul 2012 09:55:42 +0100 [thread overview]
Message-ID: <1341564942.3104.3.camel@ted> (raw)
In-Reply-To: <4FF5F32C.7080905@gmail.com>
On Thu, 2012-07-05 at 13:03 -0700, Khem Raj wrote:
> On 7/4/2012 11:51 PM, Damian, Alexandru wrote:
> > I guess the root of the problem is when the autotools start up -
> > we're having autoconf 2.68, which is not liked by gcc 4.7.1
> >
>
> thats a red herring. You should instead find out why is it trying to
> autoreconf
>
> > configure.ac:33: error: Please use exactly Autoconf 2.64 instead of
> > 2.68. config/override.m4:12: _GCC_AUTOCONF_VERSION_CHECK is
> > expanded from... configure.ac:33: the top level autom4te: m4 failed
> > with exit status: 1
> >
> >
> > I'm gonna downgrade to autoconf 2.64 and see what happens.
> >
>
> it wont help.
I merged a couple of gcc changes fairly quickly to address a variety of
problems people started hitting (including the autobuilder). The svn
nature of the recipe is causing a few issues with the subversion 1.7
change. I am wondering if we should just point it to the svn checkout
tarball by default and leave the svn url for use when updating only and
populating the mirror?
Cheers,
Richard
next prev parent reply other threads:[~2012-07-06 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 12:55 gcc errors while building core-image-sato-sdk Damian, Alexandru
2012-07-04 14:32 ` Mihai Lindner
2012-07-04 14:45 ` Richard Purdie
2012-07-04 14:50 ` Damian, Alexandru
2012-07-04 15:02 ` Richard Purdie
2012-07-04 15:06 ` Damian, Alexandru
2012-07-04 15:21 ` Martin Jansa
2012-07-05 6:51 ` Damian, Alexandru
2012-07-05 20:03 ` Khem Raj
2012-07-06 8:55 ` Richard Purdie [this message]
2012-07-06 16:00 ` Khem Raj
2012-07-06 17:23 ` Saul Wold
2012-07-07 0:54 ` 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=1341564942.3104.3.camel@ted \
--to=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox