Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: openembedded-devel@lists.openembedded.org
Subject: testing branch 2010-10-08: Udev 151 issues.
Date: Tue, 12 Oct 2010 11:31:58 +0100	[thread overview]
Message-ID: <4CB4391E.6030909@cam.ac.uk> (raw)

Hi All,

I'm getting, 

NOTE: make
mkdir -p extras/keymap
  GEN    extras/keymap/keys.txt
  GEN    extras/keymap/keys-from-name.gperf
  GEN    extras/keymap/keys-from-name.h
  GEN    extras/keymap/keys-to-name.h
make --no-print-directory all-recursive
Making all in .
  CC     libudev/libudev.lo
  CC     libudev/libudev-list.lo
  CC     libudev/libudev-util.lo
  CC     libudev/libudev-device.lo
  CC     libudev/libudev-enumerate.lo
  CC     libudev/libudev-monitor.lo
  CC     libudev/libudev-queue.lo
libudev/libudev-queue.c: In function 'udev_queue_skip_devpath':
libudev/libudev-queue.c:185:1: internal compiler error: in cond_exec_process_insns, at ifcvt.c:273
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [libudev/libudev-queue.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
FATAL: oe_runmake failed


in udev 151 and have been since 2010-10-04 (worked previously though I guess udev may
have changed).

Building imote2-image
 
MACHINE = "imote2"
DISTRO = "angstrom-2010.x"

Anyone seeing anything similar?

Jonathan



             reply	other threads:[~2010-10-12 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 10:31 Jonathan Cameron [this message]
2010-10-12 10:56 ` testing branch 2010-10-08: Udev 151 issues Paul Menzel
2010-10-12 11:59 ` Jaap de Jong
2010-10-12 16:41   ` Jonathan Cameron

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=4CB4391E.6030909@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=openembedded-devel@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