Obsoleting libc_r: How to create compat links

[Daniel Eischen]

On Fri, 27 Jun 2003, Marcel Moolenaar wrote:

> On Fri, Jun 27, 2003 at 11:05:50AM +0300, Ruslan Ermilov wrote:
> > Funny thing: reading your commit mail, and right after that
> > receiving this message.  :-)
> > 
> > On Fri, Jun 27, 2003 at 12:56:07AM -0700, Marcel Moolenaar wrote:
> > > [Ruslan added for his insights]
> > > 
> > > Ok,
> > > 
> > > I decided to obsolete libc_r on ia64 so that I can de-pessimize the
> > > setjmp/longjmp code some time before 5.2 and have sufficient time to
> > > deal with problems due to not having libc_r.
> > > 
> > > One thing we probably want to do is create compatibility links from
> > > libc_r* to libthr* or libkse*. At this time I libthr is tested on
> > > ia64, so I opt to have libc_r linked to libthr. What's the best way
> > > to do that, so that it can be used for other platforms in due time?
> > > 
> > First off, symlinking won't help old binaries that were linked
> > dynamically with libc_r.so.X, but you're supposed to well know
> > that already.  :-)
> 
> Correct. I'm not worried about compatibility with previous releases
> and the likes, because ia64 is still tier 2. I want "cc -pthread"
> to work.

-pthread is obsoleted in -current.  I'm surprised that it
hasn't been nuked yet.  There hasn't been a need for it
in well over 2 years.  Just use -lpthread (-lkse) or -lthr.

-- 
Dan Eischen