All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andy Pont" <andy.pont@sdcsystems.com>
To: <yocto@yoctoproject.org>
Subject: Build failure (Segmentation fault) with Fido on CentOS
Date: Mon, 14 Sep 2015 09:10:45 +0100	[thread overview]
Message-ID: <027301d0eec4$dc759b00$9560d100$@pont@sdcsystems.com> (raw)

Hello,

After several years away from OpenEmbedded and MVL6 I am back trying to work
with Yocto and BitBake!

My build system is a Core-i7 3770 running CentOS 6.7 (x86_64) with all the
latest updates applied.  I have cloned Fido from the git repository and set
the target as "genericx86" and started the build with "bitbake
core-image-minimal".  The build is failing with the following output (some
path names changed to protect the innocent):

g++: Internal error: Segmentation fault (program as)
| Please submit a full bug report.
| See <http://bugzilla.redhat.com/bugzilla> for instructions.
| Makefile:1059: recipe for target 'tree.o' failed
| make[1]: *** [tree.o] Error 1
| make[1]: *** Waiting for unfinished jobs....
| rm gcc.pod
| make[1]: Leaving directory
'XXXXX/build/tmp/work/x86_64-poky-linux/gcc-cross-initial-i586/4.9.2-r0/gcc-
4.9.2/build.x86_64-linux.i586-poky-linux/gcc'
| Makefile:3954: recipe for target 'all-gcc' failed
| make: *** [all-gcc] Error 2
| ERROR: oe_runmake failed
| WARNING:
XXXXX/build/tmp/work/x86_64-poky-linux/gcc-cross-initial-i586/4.9.2-r0/temp/
run.do_compile.9831:1 exit 1 from
|   exit 1
| ERROR: Function failed: do_compile (log file is located at
XXXXX/build/tmp/work/x86_64-poky-linux/gcc-cross-initial-i586/4.9.2-r0/temp/
log.do_compile.9831)

As CentOS runs some very old versions of certain tools I have installed the
native standalone SDK (v1.8) to get a version of Python that works for
BitBake.  Is this down to the fact that the native gcc/g++ version on CentOS
is 4.4.7 and binutils is v2.20.51 or have I missed something in the setup?

Thanks,

Andy.




                 reply	other threads:[~2015-09-14  8:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='027301d0eec4$dc759b00$9560d100$@pont@sdcsystems.com' \
    --to=andy.pont@sdcsystems.com \
    --cc=yocto@yoctoproject.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.