Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: OE build of qemux86 fails for linux-yocto: undefined reference to `.LASF1122'
Date: Tue, 24 Jun 2014 13:50:35 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1406241348150.12872@localhost> (raw)


  doing a test build of core-image-minimal for qemux86 using current
git pull of openembedded-core, and got:

|   LD      init/built-in.o
| drivers/built-in.o:(.debug_info+0x106096a): undefined reference to
`.LASF1122'
|
/home/rpjday/oe/builds/oe/qemux86/tmp-eglibc/work/qemux86-oe-linux/linux-yocto/3.14.5+gitAUTOINC+602be954ac_41d5fe27dc-r0/linux/Makefile:827:
recipe for target 'vmlinux' failed
| make[2]: *** [vmlinux] Error 1
| Makefile:133: recipe for target 'sub-make' failed
| make[1]: *** [sub-make] Error 2
| Makefile:26: recipe for target 'all' failed
| make: *** [all] Error 2
| ERROR: oe_runmake failed

  i'm about to try again to make sure it wasn't a transient glitch,
but has anyone else seen this?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


             reply	other threads:[~2014-06-24 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 17:50 Robert P. J. Day [this message]
2014-06-24 20:25 ` OE build of qemux86 fails for linux-yocto: undefined reference to `.LASF1122' Bruce Ashfield
2014-06-24 20:25   ` Robert P. J. Day

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=alpine.LFD.2.11.1406241348150.12872@localhost \
    --to=rpjday@crashcourse.ca \
    --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