qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 1453436 <1453436@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1453436] [NEW] Building on OS X: Undefined symbols ___emutls_v.prng_state and ___emutls_v.prng_state_data
Date: Mon, 11 May 2015 16:17:50 +0100	[thread overview]
Message-ID: <CAFEAcA9pUyfTPNzZAB1hmLm46_-5v6dUFfHeXwCrccY9BZnqQA@mail.gmail.com> (raw)
In-Reply-To: <20150509181946.28678.5025.malonedeb@soybean.canonical.com>

On 9 May 2015 at 19:19, Molt <molt@gmx.net> wrote:
> Public bug reported:
>
> Trying to build qemu on my system fails during linking with the error:
>
> Undefined symbols for architecture x86_64:
>   "___emutls_v.prng_state", referenced from:
>       _main in region-test.o
>       __GLOBAL__sub_I_65535_0_region_test.c in region-test.o
>   "___emutls_v.prng_state_data", referenced from:
>       _main in region-test.o
>       __GLOBAL__sub_I_65535_0_region_test.c in region-test.o
>
> My setup:
>
> OS: OS X 10.10.3, 64bit
> gcc: 5.1.0
> clang: 6.1.0
>
> configure command:
>
> configure --prefix="$HOME/local" --cc=clang --host-cc=clang
> --cxx=clang++

I build on OSX 10.10.3 with that clang version, but I build with
the system pixman (in /opt/X11 and presumably part of the optional
X11 OSX download), so I guess that's the difference in our setups
here.

I tried building having configured --without-system-pixman,
but that seems to fail to compile much earlier than your error:

make[3]: *** No rule to make target `pixman-combine.h.template',
needed by `pixman-combine32.h'. Stop.

-- PMM

  reply	other threads:[~2015-05-11 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-09 18:19 [Qemu-devel] [Bug 1453436] [NEW] Building on OS X: Undefined symbols ___emutls_v.prng_state and ___emutls_v.prng_state_data Molt
2015-05-11 15:17 ` Peter Maydell [this message]
2015-05-14  9:42 ` [Qemu-devel] [Bug 1453436] " Molt
2015-05-14 10:13 ` Peter Maydell
2015-05-14 11:24 ` Molt
2016-10-24 10:21 ` Thomas Huth

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=CAFEAcA9pUyfTPNzZAB1hmLm46_-5v6dUFfHeXwCrccY9BZnqQA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=1453436@bugs.launchpad.net \
    --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).