qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liu <proljc@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel]  Inconsistency detected by ld.so error, what can I do?
Date: Wed, 4 Jan 2012 17:05:32 +0800	[thread overview]
Message-ID: <CAJBMM-tzVySBSQW8o=Ku6sm1VEA2Z9YjrZFfk3oCotU4KbinGA@mail.gmail.com> (raw)

Hi all

I configure qemu as:
./configure --prefix=$PREFIX --target-list=mipsel-softmmu,mipsel-linux-user

a.out is compiled by mipsel-linux-gcc.
When I run a.out using qemu-mipsel, I get a error like this:
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 466:
elf_machine_rela_relative: Assertion `((reloc->r_info) & 0xffffffff)
== 8' failed!

What should I do?

Thanks.

--Jia Liu

             reply	other threads:[~2012-01-04  9:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04  9:05 Liu [this message]
2012-01-08 10:14 ` [Qemu-devel] Inconsistency detected by ld.so error, what can I do? Andreas Färber
2012-01-17  8:02   ` Liu

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='CAJBMM-tzVySBSQW8o=Ku6sm1VEA2Z9YjrZFfk3oCotU4KbinGA@mail.gmail.com' \
    --to=proljc@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).