qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: bent jakobsen <jakobsen.bent@gmail.com>
To: Grzegorz Kulewski <kangur@polcom.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Problems compiling qemu-snapshot
Date: Thu, 2 Jun 2005 05:14:33 +0200	[thread overview]
Message-ID: <61f63af305060120147268ba53@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0506012228040.14006@alpha.polcom.net>

Hi,

On 6/1/05, Grzegorz Kulewski <kangur@polcom.net> wrote:
> On Wed, 1 Jun 2005, bent jakobsen wrote:
> 
> > Hi,
> >
> > When I try to compile the lastest qemu-snapshot (2005-05-31_23) I get
> > the following error:
> >
> > gcc -g -Wl,-shared -o qemu-i386 elfload.o main.o syscall.o mmap.o
> > signal.o path.o osdep.o thunk.o vm86.o libqemu.a gdbstub.o -lm
> > /usr/bin/ld: errno: TLS definition in /lib/libc.so.6 section .tbss
> > mismatches non-TLS reference in libqemu.a(helper2.o)
> > /lib/libc.so.6: could not read symbols: Bad value
> > collect2: ld returned 1 exit status
> >
> >
> > Has anyone seen this before ?  Or am I the only one who has seen this ?
> >
> > I think this started to happen when I updated the Linux kernel (to
> > 2.6.11.11), or perhaps when I updated to glibc version 2.3.5
> 
> Probably glibc...
> 
> TLS = mechanizm for having some variables per-thread. It requires new gcc,
> binutils and maybe glibc.
> 
> errno = global variable (or macro or something - differs from one compiler
> to another...) that was defined in ancient days of early UNIXes ('70
> probably) to hold last error after syscall. But when you have multiple
> threads this variable must be par-thread to actually mean something (if it
> would be global you would never know if it holds last error for your
> thread or some other thread in your app). So newer glibcs set it probably
> as per-thread rather than global.
> 
> Are you absolutely sure that you have compatible and well compiled set of
> kernel, kernel headers, gcc, glibc? Because it looks like something could
> be broken here. How did you upgrade your glibc? What is your
> distributions? What are your versions of above core packages?
> 
> 
> Grzegorz Kulewski
> 

Hi,

I'm almost sure that I have the latest versions :)  This might also be
the problem :)

What is my distribution: Sorcerer
How did I update: augur easy

For your information:
Sorcerer is an sourcebased distribution like gentoo, it is just more
up to date, in regards to the different applications, and then it is a
lot easier to keep up to date, and to install (in my thoughts - but
one might have a different views upon these points).

But yes of course I can have a broken dependency on my box(es), if so
I'll be glad if anyone could say where it is broken, as qemu-snapshot
is the only application (which I know off) that I can not compile
successfully. But I'll of course keep updateing the box.

Now the versions:

glibc: 2.3.5
gcc:  3.4.4
linux: 2.6.11.11
binutils: 2.16
coreutils: 5.2.1

Did I miss any ? If so I'll gladly provide them

Best regards

Bent Jakobsen

      reply	other threads:[~2005-06-02  3:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 18:29 [Qemu-devel] Problems compiling qemu-snapshot bent jakobsen
2005-06-01 20:38 ` Grzegorz Kulewski
2005-06-02  3:14   ` bent jakobsen [this message]

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=61f63af305060120147268ba53@mail.gmail.com \
    --to=jakobsen.bent@gmail.com \
    --cc=kangur@polcom.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).