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
On Fri, Jul 6, 2012 at 1:55 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
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
On 07/06/2012 09:00 AM, Khem Raj wrote:
On Fri, Jul 6, 2012 at 1:55 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
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
On Fri, Jul 6, 2012 at 10:23 AM, Saul Wold s...@linux.intel.com wrote:
On 07/06/2012 09:00 AM, Khem Raj wrote:
On Fri, Jul 6, 2012 at 1:55 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
I merged a couple of gcc changes fairly quickly to address a variety of
problems people
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
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
-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
On 7/4/2012 3:55 PM, Damian, Alexandru wrote:
Hi guys,
From time to time I get errors building gcc (although I didn't trigger a
rebuild!) when runnign
bitbake core-image-sato-sdk
The error is attached:
On Wed, 2012-07-04 at 17:32 +0300, Mihai Lindner wrote:
On 7/4/2012 3:55 PM, Damian, Alexandru wrote:
Hi guys,
From time to time I get errors building gcc (although I didn't trigger a
rebuild!) when runnign
bitbake core-image-sato-sdk
The error is attached:
The question wasn't why it fails, but why sometimes it goes through, why
sometimes fail, and why is it retriggered
without any changes to the config or files (run 5 times the
core-image-sato-sdk build in a row, and at least once it will fail).
I don't trust systems that are not deterministic :).
On Wed, 2012-07-04 at 17:50 +0300, Damian, Alexandru wrote:
The question wasn't why it fails, but why sometimes it goes through,
why sometimes fail, and why is it retriggered
without any changes to the config or files (run 5 times the
core-image-sato-sdk build in a row, and at least once it
I guess the problem is no lmld, (skips over), Mihai says that
- library search path /usr/lib/cmplrs/cc2.11 is unsafe for
cross-compilation
is the cause.
I'm unable to trace back the cc2.11 file name (path).
Let's take it bit by bit, we have two issues here.
1. - why the configure hangs from
On Wed, Jul 04, 2012 at 06:06:55PM +0300, Damian, Alexandru wrote:
I guess the problem is no lmld, (skips over), Mihai says that
- library search path /usr/lib/cmplrs/cc2.11 is unsafe for
cross-compilation
It's one of issues I sometimes see during gcc upgrades.. and it was
there with e.g.
12 matches
Mail list logo
