Re: misc questions / comments / rambelings

From: Jon Noack (noackjr_at_alumni.rice.edu)
Date: 05/31/04 

Date: Mon, 31 May 2004 16:57:41 -0500
To: Doug White <dwhite@gumbysoft.com>

On 05/31/04 12:44, Doug White wrote:
> On Sun, 30 May 2004, asfdqwer xzcvdsf wrote:
>> Now that I'm running current is there anything special I have to
>> change in make.conf? Should I still have to define "WITH_THREADS"
>> and "WITH_LIBMAP" or do the ports autorecognize the kse -->
>> pthreads change?
>
> As long as your ports tree is up to date and you don't have anything
> threads-related in /etc/make.conf or /etc/libmap.conf, you should be
> ok. You will have to rebuild anything that uses threads, though, and
> that includes XFree86. If you have kde and/or qt installed it gets a
> little more complicated.

Perhaps I am mistaken on this, but can't you just map libc_r ->
libpthread in /etc/libmap.conf instead of rebuilding everything? I know
this won't work in every case (nVidia driver, MySQL had some libpthread
issues a while back, etc.), but I would try it before recompiling
everything...

 From /usr/src/UPDATING:
20040303:
     If you are having trouble with the libc_r -> libpthread transition
     (see the 20040130 entry), place the following lines at the top of
     /etc/libmap.conf:

     libc_r.so.5 libpthread.so.1
     libc_r.so libpthread.so

     This will cause all programs and libraries linked against libc_r
     to use libpthread instead.

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

Relevant Pages

  • Re: How to replace libpthread correctly on 7.0?
    ... I removed and rebuilt all my ports using the ports system, and so far I haven't noticed any problems with them. ... When I attempted to rebuild Code::Blocks, the build failed with an error relating to libpthread.so.2. ... I searched the web a bit and discovered that libpthread had fallen out of favor in 7 and was being replaced by something else. ... I thought that "make" was making all new executables and libraries, but in fact it was pulling in an old library that was linked to libpthread. ...
    (freebsd-questions)
  • Re: kdesu crash under 5.2-RELEASE with libkse via libmap.conf
    ... On Monday 09 February 2004 13:23, Doug White wrote: ... The KDE crash window popped up and I ... > Or the backtrace will be in abort. ... Looks like they're just dyn-linked to libc_r, in which case libpthread should ...
    (freebsd-current)
  • How to replace libpthread correctly on 7.0?
    ... I removed and rebuilt all my ports using the ports system, and so far I haven't noticed any problems with them. ... When I attempted to rebuild Code::Blocks, the build failed with an error relating to libpthread.so.2. ... I searched the web a bit and discovered that libpthread had fallen out of favor in 7 and was being replaced by something else. ... For my personal projects, is the -pthread switch any good anymore, or is there a different switch I should be using now? ...
    (freebsd-questions)
  • Re: backing to 5.2.1, problem with threading and "cxa_atexit"
    ... >> I recon it is in libpthread in current, but wasn't there at 5.2.1, ... > library on -current, you should rebuild all apps, which are ...
    (freebsd-current)
  • Re: KSE headache: Spinlock called when not threaded
    ... > I found out some apps recompiled with KSE libpthread (not from ports, ... obscure way of saying "there are two threads libraries linked to this ... If so, rebuild that library ... so it pulls in libpthread instead of libc_r. ...
    (freebsd-questions)