Re: Programs not accepting input?

On 07/21/2006 08:32, Robert Watson wrote: On Fri, 21 Jul 2006, Greg 'groggy' Lehey wrote: I've been keeping a closer eye on my problem. I'm using fvwm1 with click-to-focus and lose-focus-on-screen-switch. If I move from one screen to another and quickly click on a window, the border

Re: Strange keyboard (viral?) behaviour

On 06/12/06 14:17, Philip Lykke Carlsen wrote: mandag 12 juni 2006 20:48 skrev du: Philip Lykke Carlsen wrote: Hm. A little more research seems to have narrowed it down a bit. Apparently the text come from my sisters windows pc and is transmitted realtime to my freebsd machine, peculiar as it

Re: weird problems with porupgrade

Hannes Hauswedell wrote: hi everybody! since some time now i am developing kports an advanced kde frontend for the freebsd-ports and in future also pkgsrc and openbsd ports. since the last release last summer i have gone through a complete rewrite and right now am at the point where i monitor

Re: automatic checking of source code

Divacky Roman wrote: hi I just found http://mygcc.free.fr/ which is a project for automatic checking of source code for bugs (memory leaks, unreleased locks, null pointer dereferences). I recall there was some SoC project to achieve something similar but this is complete and ready to run... it

Re: repeatedly opening the same .so(s) is slow?

Peter Jeremy wrote: On Tue, 2006-Mar-21 14:31:24 +0100, [EMAIL PROTECTED] wrote: Set libltdl_cv_sys_dlopen_deplibs=yes in the environment before running configure and try again. And yes, this is *exactly* the same idiosyncraty as KDE. This is needed for both guile and libltdl. After

Re: repeatedly opening the same .so(s) is slow?

Eric Schuele wrote: Peter Jeremy wrote: On Tue, 2006-Mar-21 14:31:24 +0100, [EMAIL PROTECTED] wrote: Set libltdl_cv_sys_dlopen_deplibs=yes in the environment before running configure and try again. And yes, this is *exactly* the same idiosyncraty as KDE. This is needed for both guile

repeatedly opening the same .so(s) is slow?

Hello, Sorry if the subject is misleading, not sure how to label this one. I have a port (gnucash) which takes 3-4 minutes to open on a 2.6GHz machine. It used to take 15-20 seconds till all of the libtool changes. I have no idea if the symptom is related to libtool or not. Others have

Re: repeatedly opening the same .so(s) is slow?

Peter Jeremy wrote: On Mon, 2006-Mar-20 10:49:57 -0600, Eric Schuele wrote: I have a port (gnucash) which takes 3-4 minutes to open on a 2.6GHz machine. It used to take 15-20 seconds till all of the libtool changes. It takes 15 minutes on a -current Athlon XP-1800 and about 2 minutes

Re: repeatedly opening the same .so(s) is slow?

Peter Jeremy wrote: On Mon, 2006-Mar-20 10:49:57 -0600, Eric Schuele wrote: I have a port (gnucash) which takes 3-4 minutes to open on a 2.6GHz machine. It used to take 15-20 seconds till all of the libtool changes. It takes 15 minutes on a -current Athlon XP-1800 and about 2 minutes

Re: repeatedly opening the same .so(s) is slow?

[EMAIL PROTECTED] wrote: On Mon, Mar 20, 2006 at 10:49:57AM -0600, Eric Schuele wrote: I have a port (gnucash) which takes 3-4 minutes to open on a 2.6GHz machine. It used to take 15-20 seconds till all of the libtool changes. This sounds exactly like the problems I initially had with KDE

Re: ATI drivers for FreeBSD - anything? [Slightly OT]

Maxime Henrion wrote: Albert Vest wrote: On Sat, 19 Nov 2005 01:58:25 +0200 (EET) Vladimir Kushnir [EMAIL PROTECTED] wrote: Hi all, Is there any project on FreeBSD wrapper for ATI Linux drivers (like nVidia's used to be)? If so - I'd be more than happy to test (sorry I can hardly write it