From: Stuart Hughes <stuarth@lineo.com>
To: linux-mips@oss.sgi.com
Subject: problems with libpthread at start-up
Date: Fri, 14 Dec 2001 10:50:15 +0000 [thread overview]
Message-ID: <3C19D967.58F2BC90@lineo.com> (raw)
Hi everyone,
I've successfully built and deployed a system using a toolchain I built
using the instructions at:
http://www.ltc.com/~brad/mips/mips-cross-toolchain, which were very
helpful. This gives a combination of:
binutils-2.11.90.0.25, gcc-3.0.1, glibc-2.2.3, linuxthreads-2.2.3 &
glibc-2.2.3-mips-base-addr-got.diff
A simple 'hello world' programs in both c and c++ work, statically and
dynamically linked, but as soon as I try to link or use pthreads I get
the following (dynamic linking):
#
./helloc
[helloc:23] Illegal instruction 00000003 at 2ad0847c
ra=2ab76820
My ldd shows
# /lib/ld.so.1 --list
./helloc
libpthread.so.0 => //lib/libpthread.so.0
(0x2aaaa000)
libc.so.6 => //lib/libc.so.6
(0x2ab05000)
/lib/ld.so.1 => /lib/ld.so.1
(0x55550000)
libgcc_s.so.1 => //lib/libgcc_s.so.1
(0x2acb1000)
I'm running on an IDT79RC32334
It seems as though I must have missed a patch or something. Does anyone
know if there is a fix for this.
BTW, the hello program does not even create a pthread, all I did was add
-lpthread onto the compile line.
--
Regards, Stuart
reply other threads:[~2001-12-14 11:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C19D967.58F2BC90@lineo.com \
--to=stuarth@lineo.com \
--cc=linux-mips@oss.sgi.com \
/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