This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: old release question: glibc-2.2.5 + gcc-3.4.0 generate static appsthat segfault at startup?
- From: Wolfram Gloger <wmglo at dent dot med dot uni-muenchen dot de>
- To: dank at kegel dot com
- Cc: libc-alpha at sources dot redhat dot com
- Date: 24 May 2004 10:03:19 -0000
- Subject: Re: old release question: glibc-2.2.5 + gcc-3.4.0 generate static appsthat segfault at startup?
- References: <40B0A71C.5050906@kegel.com>
Hi,
> glibc-2.3.2 works for me, but I'm also using an older release, 2.2.5,
> and was hoping someone here would remember something about this issue.
>
> I built a gcc-3.4.0-glibc-2.2.5 toolchain for i686,
How did you sucessfully build gcc-3.4 (or -3.3, anything > 3.2) with
glibc-2.2.5? Did you perhaps build C only (no g++)? glibc-2.2.5 has
several occurences of __thread in its header files, which is a keyword
in newer gccs.
Building _anything_ that involves thread support with such a gcc on
glibc-2.2.5 always failed for me.
> (gdb) bt
> #0 0x00000000 in ?? ()
> #1 0x08048850 in ptmalloc_init () at malloc.c:1756
Maybe this also has to do with some subtle __thread-related problem?
Regards,
Wolfram.