Re: List replies
Hi, On Sat, Mar 22, 2008 at 11:54 PM, Tore Lund <[EMAIL PROTECTED]> wrote: > > I request that this misunderstood piece of "etiquette" is revised. If > someone has the brains to find this list as well as the brains to use > FreeBSD at all, they also have the brains to come back here to look for > answers. Copying the sender makes no sense at all, as far as I can see. > Whether or not headers should be modified is a separate matter. Sorry for interrupting your discussion. Just a sidenote: I actually did the mistake of subscribing to mailing list, because I did not know that I would be able to post (and receive answers) without being subscribed. That resulted in a few tens of messages not related to the subject I posted about on the very first day, including yours one. If I *had* to go through this in order to get my problem solved, I would rather use some forum. > > -- >Tore > Best regards, Dmitry RCL Rekman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x)
Hi, On Sat, Mar 22, 2008 at 7:19 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote: > Dmitry RCL Rekman wrote: > > Hi, > > > > On Sat, Mar 22, 2008 at 6:57 PM, Kris Kennaway <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Dmitry RCL Rekman wrote: > > > Hi, > > > > > > On Sat, Mar 22, 2008 at 6:40 PM, Kris Kennaway <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > > > > > > Well, the commandline used to build libqt-mt is included > > in the > > > log and > > > > it also links to -pthread... > > > > > > Yes, also uic (correctly) links directly to -pthread (I > > missed this on > > > first read). The only way I can see this failing is if your > > /lib is not > > > correctly populated. What is the output of > > > > > > ls -l /lib/libthr* /usr/lib/libpthr* > > > > > > > > > # ls -l /lib/libthr* /usr/lib/libpthr* > > > -r--r--r-- 1 root wheel 66928 Feb 29 12:20 /lib/libthr.so.3 > > > lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 > > /usr/lib/libpthread.a -> > > > libthr.a > > > lrwxr-xr-x 1 root wheel 10 Feb 29 12:21 > > /usr/lib/libpthread_p.a -> > > > libthr_p.a > > > > Yep, your world is broken, you are missing a /usr/lib/libpthread.so > > symlink. > > > > > > Ok, I created a symlink /usr/lib/libpthread.so -> /usr/lib/libthr.so and > > am trying to build kdebase3 again. Will inform shortly :-) > > Well you'll likely have to rebuild other things first to recover from > the damage compiled into an unknown subset of your existing ports. > Repeating portupgrade -fa might be the best option. > Ok, after creating that symlink kdebase3 has been successfully built. However, I'm starting portupgrade -fa according to your advice. Thank you very much for resolving the problem! I think that freebsd-update script and/or the appropriate guide should be updated so those symlinks are created automatically. > > Kris > Best regards, Dmitry RCL Rekman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PS/2 mice suddenly stopped working
Hi, On Sat, Mar 22, 2008 at 6:02 PM, Greg Mars <[EMAIL PROTECTED]> wrote: > I just turned on today and my ps/2 mouse (actually SB with a ps/2 adapter) > was not working. > Tried reconfiguring in sysinstall to no avail. > Tried another pure ps/2 mouse and it didn't work either. > Took off the usb-ps/2 adapter off the original mouse, plugged it in a usb > port, and now it works. > > Everything used to work just the day before. > I guess it's possible something could be wrong with the port > (which would be sad since the motherboard is probably 2-3 weeks old) > > Does anyone have any ideas on how to test this? > I don't have another OS on this box and installing one won't be easy. > I used to have similar problem once - PS/2 (real PS/2, not one with an USB adapter) mouse got stuck every time it was left inactive for more than 5 minutes or so. I sort of "cured" it by restarting moused every 5 minutes with a cron job - so next time you may also try restarting moused before unplugging the mouse. By no means it is meant to be correct solution, I am just suggesting you to check whether the problem is caused by software or hardware. Best regards, Dmitry RCL Rekman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x)
Hi, On Sat, Mar 22, 2008 at 6:57 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote: > Dmitry RCL Rekman wrote: > > Hi, > > > > On Sat, Mar 22, 2008 at 6:40 PM, Kris Kennaway <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > Well, the commandline used to build libqt-mt is included in the > > log and > > > it also links to -pthread... > > > > Yes, also uic (correctly) links directly to -pthread (I missed this > on > > first read). The only way I can see this failing is if your /lib is > not > > correctly populated. What is the output of > > > > ls -l /lib/libthr* /usr/lib/libpthr* > > > > > > # ls -l /lib/libthr* /usr/lib/libpthr* > > -r--r--r-- 1 root wheel 66928 Feb 29 12:20 /lib/libthr.so.3 > > lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a -> > > libthr.a > > lrwxr-xr-x 1 root wheel 10 Feb 29 12:21 /usr/lib/libpthread_p.a -> > > libthr_p.a > > Yep, your world is broken, you are missing a /usr/lib/libpthread.so > symlink. Ok, I created a symlink /usr/lib/libpthread.so -> /usr/lib/libthr.so and am trying to build kdebase3 again. Will inform shortly :-) > > Kris > Best regards, Dmitry RCL Rekman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x)
Hi, On Sat, Mar 22, 2008 at 6:40 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote: > > Well, the commandline used to build libqt-mt is included in the log and > > it also links to -pthread... > > Yes, also uic (correctly) links directly to -pthread (I missed this on > first read). The only way I can see this failing is if your /lib is not > correctly populated. What is the output of > > ls -l /lib/libthr* /usr/lib/libpthr* > # ls -l /lib/libthr* /usr/lib/libpthr* -r--r--r-- 1 root wheel 66928 Feb 29 12:20 /lib/libthr.so.3 lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a -> libthr.a lrwxr-xr-x 1 root wheel 10 Feb 29 12:21 /usr/lib/libpthread_p.a -> libthr_p.a > > Kris > > > Best regards, Dmitry RCL Rekman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x)
Hi, On Sat, Mar 22, 2008 at 6:14 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote: > > Actually, the problem was tracked down to be inside uic. When built on > my > > (and Leslie's) 7.0 "upgraded" from 6.x system, uic does not link to > > libthr.so, while in a newly-installed 7.0 it does. > > It should not be linking (directly) to libthr at all, it should be > linking to libpthread (which is a symlink to it). > Yes, it does link to -lpthread, but ldd tells different things on newly installed 7.0 and 7.0 upgraded from 6.2... I don't know if it's the reason, that was Mel's guess ( http://docs.freebsd.org/cgi/mid.cgi?200803141208.57610.fbsd.questions ). > > > So one of people here (Mel) asked to provide the actual commandline used > to > > link uic (see this for reference: > > http://docs.freebsd.org/cgi/mid.cgi?200803161912.18248.fbsd.questions), > > which is what I did. > > It links to libqt-mt and presumably gets its thread library from there, > so the question extends there. > Well, the commandline used to build libqt-mt is included in the log and it also links to -pthread... > > > Log of the actual "mutex unlock failure" error was already posted in > this > > list, it's here: http://docs.freebsd.org/cgi/mid.cgi?47D8DBC0.3010106 > > OK, I suppose I was confused because you posted this under a new subject > instead of as a followup to the earlier messages, so context was lost > from your mails. > Ok, my fault - should have taken the same subject :-) If you are willing to further investigate the issue, I can provide more details about my system or even give you the shell access. > > Kris > Best regards, Dmitry RCL Rekman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x)
Hi, On Sat, Mar 22, 2008 at 5:47 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote: > Dmitry RCL Rekman wrote: > > Hi, > > > > On Sat, Mar 22, 2008 at 3:52 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote: > > > >> RCL wrote: > >>> Hi, > >>> > >>> I'm having the same troubles as Leslie Jensen when compiling KDE (or > >>> anything that uses uic, e.g. amarok): > >>> compile process stucks with the following message: > >>> > >>> Mutex unlock failure: Operation not permitted > > > Well, it actually did not rebuild the KDE & friends (because of > > aforementioned problem with unlocking the mutex), so I had to interrupt > > that, leaving some ports alone. I admit that is a deviation from upgrade > > procedure, but it is not perhaps the reason of mutex problem, because it > > appeared while rebuilding the ports for the first time. > > There is no reference in your log file to "Mutex unlock failure". > It does not appear when building Qt, but when building e.g. kdebase3 (when uic is used). Actually, the problem was tracked down to be inside uic. When built on my (and Leslie's) 7.0 "upgraded" from 6.x system, uic does not link to libthr.so, while in a newly-installed 7.0 it does. So one of people here (Mel) asked to provide the actual commandline used to link uic (see this for reference: http://docs.freebsd.org/cgi/mid.cgi?200803161912.18248.fbsd.questions ), which is what I did. Log of the actual "mutex unlock failure" error was already posted in this list, it's here: http://docs.freebsd.org/cgi/mid.cgi?47D8DBC0.3010106 > > Kris > Best regards, Dmitry RCL Rekman ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "Mutex unlock failure" when compiling KDE (upgrade from 6.x)
Hi,
On Sat, Mar 22, 2008 at 3:52 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> RCL wrote:
> > Hi,
> >
> > I'm having the same troubles as Leslie Jensen when compiling KDE (or
> > anything that uses uic, e.g. amarok):
> > compile process stucks with the following message:
> >
> > Mutex unlock failure: Operation not permitted
> >
> > I found out that the problem was already being investigated here on
> > the list, but no solution has yet been proposed :(
> > If it helps, I performed the steps that Mel asked to perform and
> > here's the log file of Qt build process:
> >
> > http://rcl.mine.nu/outbound/freebsd/qt-copy-3.3.8_6.log.tar.gz
> >
> > The actual command that is used to link uic is:
> > c++ -fno-exceptions -Wl,-rpath,/usr/local/lib
> > -Wl,-rpath,/usr/local/lib -pthread -o ../../../bin/uic
> > .obj/release-shared-mt/main.
> > o .obj/release-shared-mt/uic.o .obj/release-shared-mt/form.o
> > .obj/release-shared-mt/object.o .obj/release-shared-mt/subclassing
> > .o .obj/release-shared-mt/embed.o
> > .obj/release-shared-mt/widgetdatabase.o
> > .obj/release-shared-mt/domtool.o .obj/release-shared-
> > mt/parser.o-L/usr/local/lib
> > -L/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/lib
> > -L/usr/local/lib -lqt-mt -lmng -ljpeg -lp
> > ng -lz -lXi -lXrender -lXrandr -lXcursor -lXinerama -lXft -lfreetype
> > -lfontconfig -lXext -lX11 -lm -lSM -lICE
> >
> > There's no file libpthread.* in /usr/local/lib. These are
> > libpthread.so/a files I have:
> >
> > # ls -la `locate libpthread.{a,so}`
> > lrwxrwxrwx 1 root wheel 19 Feb 29 13:57
> > /usr/compat/linux/lib/libpthread.so.0 -> libpthread-2.3.6.so
> > lrwxrwxrwx 1 root wheel 18 Feb 29 13:57
> > /usr/compat/linux/lib/obsolete/linuxthreads/libpthread.so.0 ->
> > libpthread-0.10.so
> > lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a ->
> libthr.a
> > -r--r--r-- 1 root wheel 136020 Feb 29 16:16
> > /usr/local/lib/compat/libpthread.so.1
> > -r-xr-xr-x 1 root wheel 43284 Oct 17 00:52
> > /usr/local/lib/valgrind/libpthread.so
> > lrwxr-xr-x 1 root wheel 13 Oct 17 00:52
> > /usr/local/lib/valgrind/libpthread.so.2 -> libpthread.so
> >
> > I upgraded the system nearly a month ago (On 29th Feb) and since then
> > I cannot build any KDE application (not even rebuild kde base/lib
> > ports themselves).
> > Upgrade procedure I used is described here:
> >
> http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html
> >
> > I hope the information provided will help further investigate the
> > problem. I don't want to reinstall the system, that feels like a
> > solution from Windows world :-)
>
> Are you certain that your portupgrade -af completed successfully after
> you upgraded the base OS? If this was not completed it will cause
> problems along these lines.
>
Well, it actually did not rebuild the KDE & friends (because of
aforementioned problem with unlocking the mutex), so I had to interrupt
that, leaving some ports alone. I admit that is a deviation from upgrade
procedure, but it is not perhaps the reason of mutex problem, because it
appeared while rebuilding the ports for the first time.
> Kris
>
Best regards,
Dmitry RCL Rekman
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
