From: Khem Raj <raj.khem@gmail.com>
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: Thu, 05 Jul 2012 13:03:56 -0700 [thread overview]
Message-ID: <4FF5F32C.7080905@gmail.com> (raw)
In-Reply-To: <CAJ2CSBvQJtFPBXf-QEVm7bO84W4_K2ziYAOR=1kiQfENyK_D_Q@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/18ywACgkQuwUzVZGdMxTGgQCfV0OhuBE+gaoqYyq8oCpyKUP1
K8gAniKed69w0iLjnZznAeGOoS8ovt9H
=x3RK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-07-05 20:15 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 [this message]
2012-07-06 8:55 ` Richard Purdie
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=4FF5F32C.7080905@gmail.com \
--to=raj.khem@gmail.com \
--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.