Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Wayne Gowcher <wgowcher@yahoo.com>
Cc: Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: pthread support in mipsel-linux
Date: Thu, 21 Feb 2002 10:25:03 -0800	[thread overview]
Message-ID: <20020221102503.A28936@lucon.org> (raw)
In-Reply-To: <20020221181204.48818.qmail@web11908.mail.yahoo.com>; from wgowcher@yahoo.com on Thu, Feb 21, 2002 at 10:12:04AM -0800

On Thu, Feb 21, 2002 at 10:12:04AM -0800, Wayne Gowcher wrote:
> H.J.
> 
> Thank you for your reply.
> 
> > The threads works well with glibc compiled with
> > -mips2. But the threads
> > in my RedHat 7.1 is broken when compiled with -mips2
> > :-(. I have fixed
> > it in glibc CVS.
> 
> Just to clarify, the glibc rpm in your Redhat 7.1 is
> compiled with -mips1 right ? So as it is broken yes ?

Yes. -mips1 doesn't work well with thread.

> 
> So if I REALLY wanted to use pthreads with your redhat
> 7.1 distribution, could I get away with checking out
> the current glibc from CVS, recompiling it and
> installing over the rpm glibc ? Or is that too
> simplistic, and it will need recompilation of a lot of
> other applications ? 

It should be mostly ok if you use gcc 2.96. But glibc in CVS lacks
a few mips change in my glibc in RedHat 7.1. At least, you may want
glibc-2.2-mmap64.patch in my glibc.



H.J.

  reply	other threads:[~2002-02-21 19:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21  1:36 set_io_port_base()? Matthew Dharm
2002-02-21  1:57 ` set_io_port_base()? Ralf Baechle
2002-02-21  2:05   ` set_io_port_base()? Matthew Dharm
2002-02-21  2:13     ` set_io_port_base()? Ralf Baechle
2002-02-21  2:27       ` set_io_port_base()? Jun Sun
2002-02-21  2:48         ` set_io_port_base()? Matthew Dharm
2002-02-21  2:48           ` set_io_port_base()? Matthew Dharm
2002-02-21  3:03           ` set_io_port_base()? Jason Gunthorpe
2002-02-21  5:35           ` set_io_port_base()? Jun Sun
2002-02-21  3:30         ` set_io_port_base()? Ralf Baechle
2002-02-21 16:34         ` pthread support in mipsel-linux Wayne Gowcher
2002-02-21 17:55           ` H . J . Lu
2002-02-21 18:12             ` Wayne Gowcher
2002-02-21 18:25               ` H . J . Lu [this message]
2002-02-21 18:45                 ` Wayne Gowcher
2002-02-22  8:52                   ` Florian Lohoff
2002-02-22 13:38                 ` Maciej W. Rozycki
2002-02-22 13:45                   ` Hiroyuki Machida
2002-02-22 14:28                     ` Maciej W. Rozycki
2002-02-22 16:53                   ` H . J . Lu
2002-02-22 16:57                     ` H . J . Lu
2002-02-22 17:06                     ` Maciej W. Rozycki
2002-02-22 17:14                       ` H . J . Lu
2002-04-19 17:06             ` Equivalent of ioperm / iopl in linux mips ? Wayne Gowcher
2002-04-20  9:03               ` Geert Uytterhoeven
2002-04-22 11:35                 ` Maciej W. Rozycki
2002-04-22 14:55                   ` Geert Uytterhoeven
2002-04-22 15:30                     ` Maciej W. Rozycki
2002-04-22 15:33                       ` Geert Uytterhoeven
2002-04-22 17:44                       ` Ralf Baechle
2002-04-22 18:01                         ` Maciej W. Rozycki
2002-02-21  2:08   ` set_io_port_base()? Matthew Dharm
2002-02-21  2:16     ` set_io_port_base()? Ralf Baechle

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=20020221102503.A28936@lucon.org \
    --to=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=wgowcher@yahoo.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