Re: Compile error, kde related?

2008-03-19 Thread Leslie Jensen


Mel wrote:

Nope. But I would be interested to see what the line is that compiles uic. And 
what configure produces.


I still think there's something '6.x-ish' going on here, but without knowing 
how uic gets built, it's anyone's guess.


Could you try the following:
cd /usr/ports/x11/qt33
make clean
mkdir /var/log/portbuilds
make build /var/log/portbuilds/`make -V PKGNAME`.log 21
make -V CONFIGURE_ARGS  /var/log/portbuilds/`make -V PKGNAME`.log
cat `make -V WRKSRC`/config.log \
/var/log/portbuilds/`make -V PKGNAME`.log

Then put that log up somewhere if you have webspace, or try to find references 
to '-pthread', 'libpthread', 'libthr' and the final link command that makes 
uic.


It's probably some setting you have or some stray library that causes this and 
until you get it resolved, you can't trust any threaded application you build 
from ports. Or, it's specific for qt, but I highly doubt that.


I'm getting this error, no config.log file

cat: /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/config.log: No 
such file or directory


find /usr/ports/x11-toolkits/qt33/ -name config*
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/src/3rdparty/zlib/configure
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/src/3rdparty/libmng/makefile
s/configure.in
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/src/3rdparty/libmng/configur
e
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/src/3rdparty/libmng/configur
e.in
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/src/3rdparty/libmng/config.g
uess
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/src/3rdparty/libmng/config.s
ub
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/src/3rdparty/libpng/configur
e
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/src/3rdparty/sqlite/config.h
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/qvfb/config.ui
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/qvfb/.obj/release-shar
ed-mt/config.o
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/qvfb/config.h
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/qvfb/config.cpp
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/assistant/config.cpp
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/assistant/config.h
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/assistant/.obj/release
-shared-mt/config.o
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/designer/designer/conf
igtoolboxdialog.ui.h
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/designer/designer/conf
igtoolboxdialog.ui
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/designer/designer/conf
igtoolboxdialog.h
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/designer/designer/conf
igtoolboxdialog.cpp
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/tools/designer/designer/conf
igtoolboxdialog.o
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/configure
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/config.tests
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/configure.orig
/usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/config.status

I need advise on how to proceed.
Thanks
Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [Fwd: Re: Compile error, kde related?]

2008-03-18 Thread Leslie Jensen

Mel wrote:

 Nope. But I would be interested to see what the line is that compiles 
uic. And what configure produces.


 I still think there's something '6.x-ish' going on here, but without 
knowing how uic gets built, it's anyone's guess.


 Could you try the following:
 cd /usr/ports/x11/qt33
 make clean
 mkdir /var/log/portbuilds
 make build /var/log/portbuilds/`make -V PKGNAME`.log 21
 make -V CONFIGURE_ARGS  /var/log/portbuilds/`make -V PKGNAME`.log
 cat `make -V WRKSRC`/config.log \
 /var/log/portbuilds/`make -V PKGNAME`.log

 Then put that log up somewhere if you have webspace, or try to find 
references to '-pthread', 'libpthread', 'libthr' and the final link 
command that makes uic.


 It's probably some setting you have or some stray library that causes 
this and until you get it resolved, you can't trust any threaded 
application you build from ports. Or, it's specific for qt, but I highly 
doubt that.


-- Mel


Here's is what I've done so far.
There's two problems, the command

cat `make -V WRKSRC`/config.log \
/var/log/portbuilds/`make -V PKGNAME`.log

Generates an error, Please see below. And the log file is empty!


-
bsdpc01# cd /usr/ports/x11-toolkits/qt33

bsdpc01# make clean
===  Cleaning for qt-copy-3.3.8_6

bsdpc01# sh
# make build /var/log/portbuilds/`make -V PKGNAME`.log 21

# make -V CONFIGURE_ARGS  /var/log/portbuilds/`make -V PKGNAME`.log

# cat `make -V WRKSRC`/config.log /var/log/portbuilds/`make -V
PKGNAME`.log
cat: /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/config.log: No
such file or directory

# cat `make -V WRKSRC`/config.log \/var/log/portbuilds/`make -V
PKGNAME`.log
cat: /usr/ports/x11-toolkits/qt33/work/qt-x11-free-3.3.8/config.log: No
such file or directory
cat: : No such file or directory

# ls /var/log/portbuilds
qt-copy-3.3.8_6.log


ll /var/log/portbuilds/
total 0
-rw-r--r--  1 root  wheel  0 Mar 18 15:27 qt-copy-3.3.8_6.log
---

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-17 Thread Leslie Jensen



Nope. But I would be interested to see what the line is that compiles uic. And 
what configure produces.


I still think there's something '6.x-ish' going on here, but without knowing 
how uic gets built, it's anyone's guess.


Could you try the following:
cd /usr/ports/x11/qt33
make clean
mkdir /var/log/portbuilds
make build /var/log/portbuilds/`make -V PKGNAME`.log 21
make -V CONFIGURE_ARGS  /var/log/portbuilds/`make -V PKGNAME`.log
cat `make -V WRKSRC`/config.log \
/var/log/portbuilds/`make -V PKGNAME`.log

Then put that log up somewhere if you have webspace, or try to find references 
to '-pthread', 'libpthread', 'libthr' and the final link command that makes 
uic.


It's probably some setting you have or some stray library that causes this and 
until you get it resolved, you can't trust any threaded application you build 
from ports. Or, it's specific for qt, but I highly doubt that.


Hi
I'm getting an error!

bsdpc01# make build /var/log/portbuilds/`make -V PKGNAME`.log 21

Ambiguous output redirect.

/Leslie




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-16 Thread Leslie Jensen



Leslie Jensen skrev:


Mel skrev:

On Saturday 15 March 2008 18:10:00 Leslie Jensen wrote:

portupgrade -Rf x11-toolkits/qt33
If uic still does not show linked to libthr, I have no clue what causes
that on your system. I'd inspect /etc/libmap.conf, /etc/make.conf, the
config.log for qt33 and the final link command that produces the uic
binary.


I've tried to make a fresh instal of FreeBSD 7.0 and there is libthr 
linked as it should be. What I don't understand is that on the system 
where I have the problem I did a pkg_delete -a after it was upgraded to 
7.0, and manually deleted everything left in /usr/local before starting 
over with the ports.


Can I manually link uic to libthr and would it be a clean hack or?
/Leslie

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-16 Thread Mel
On Sunday 16 March 2008 12:56:22 Leslie Jensen wrote:
 Leslie Jensen skrev:
  Mel skrev:
  On Saturday 15 March 2008 18:10:00 Leslie Jensen wrote:
  portupgrade -Rf x11-toolkits/qt33
  If uic still does not show linked to libthr, I have no clue what
  causes that on your system. I'd inspect /etc/libmap.conf,
  /etc/make.conf, the config.log for qt33 and the final link command
  that produces the uic binary.

 I've tried to make a fresh instal of FreeBSD 7.0 and there is libthr
 linked as it should be. What I don't understand is that on the system
 where I have the problem I did a pkg_delete -a after it was upgraded to
 7.0, and manually deleted everything left in /usr/local before starting
 over with the ports.

 Can I manually link uic to libthr and would it be a clean hack or?

Nope. But I would be interested to see what the line is that compiles uic. And 
what configure produces.

I still think there's something '6.x-ish' going on here, but without knowing 
how uic gets built, it's anyone's guess.

Could you try the following:
cd /usr/ports/x11/qt33
make clean
mkdir /var/log/portbuilds
make build /var/log/portbuilds/`make -V PKGNAME`.log 21
make -V CONFIGURE_ARGS  /var/log/portbuilds/`make -V PKGNAME`.log
cat `make -V WRKSRC`/config.log \
/var/log/portbuilds/`make -V PKGNAME`.log

Then put that log up somewhere if you have webspace, or try to find references 
to '-pthread', 'libpthread', 'libthr' and the final link command that makes 
uic.

It's probably some setting you have or some stray library that causes this and 
until you get it resolved, you can't trust any threaded application you build 
from ports. Or, it's specific for qt, but I highly doubt that.
-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-15 Thread Leslie Jensen



There's your problem. I don't see a libpthread or better on 7.x a libthr.so 
linked in:


libthr.so.3 = /lib/libthr.so.3 (0x38b55000)

is what it shows on my 7.x system.

So the question is, why isn't qt built with thread support. I don't see how 
that's possible with the current ports makefile.

Do you have a file /lib/libthr.so*?



Yes I do.

bsdpc01# find /lib | grep libthr.so
/lib/libthr.so.3

So what do you suggest I do now?

/Leslie


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-15 Thread Mel
On Saturday 15 March 2008 10:04:21 Leslie Jensen wrote:
  There's your problem. I don't see a libpthread or better on 7.x a
  libthr.so linked in:
 
  libthr.so.3 = /lib/libthr.so.3 (0x38b55000)
 
  is what it shows on my 7.x system.
 
  So the question is, why isn't qt built with thread support. I don't see
  how that's possible with the current ports makefile.
  Do you have a file /lib/libthr.so*?

 Yes I do.

 bsdpc01# find /lib | grep libthr.so
 /lib/libthr.so.3

 So what do you suggest I do now?


portupgrade -Rf x11-toolkits/qt33
If uic still does not show linked to libthr, I have no clue what causes that 
on your system. I'd inspect /etc/libmap.conf, /etc/make.conf, the config.log 
for qt33 and the final link command that produces the uic binary.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-15 Thread Leslie Jensen




portupgrade -Rf x11-toolkits/qt33
If uic still does not show linked to libthr, I have no clue what causes that 
on your system. I'd inspect /etc/libmap.conf, /etc/make.conf, the config.log 
for qt33 and the final link command that produces the uic binary.




I just did
bsdpc01# pkg_info | grep qt3
and found no qt33 installed!
So I'll start with installing it :-)

I'm not sure what to do with uic but maybe that'll clear when it's 
installed.


If the kdebase port needs qt33 to build, shouldn't it be installed as a 
dependency?


/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-15 Thread Mel
On Saturday 15 March 2008 18:10:00 Leslie Jensen wrote:
  portupgrade -Rf x11-toolkits/qt33
  If uic still does not show linked to libthr, I have no clue what causes
  that on your system. I'd inspect /etc/libmap.conf, /etc/make.conf, the
  config.log for qt33 and the final link command that produces the uic
  binary.

 I just did
 bsdpc01# pkg_info | grep qt3
 and found no qt33 installed!

That could be, cause the port is called qt33 but the package once installed 
qt-3 or qt-copy-3 :P
Better: pkg_info qt-*
-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-15 Thread Leslie Jensen


That could be, cause the port is called qt33 but the package once installed 
qt-3 or qt-copy-3 :P

Better: pkg_info qt-*


Yes I realised that after I wrote my mail.
I'm in the progress of
portupgrade -Rf x11-toolkits/qt33
I'll report back when it's done.
/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-15 Thread Leslie Jensen


Mel skrev:

On Saturday 15 March 2008 18:10:00 Leslie Jensen wrote:

portupgrade -Rf x11-toolkits/qt33
If uic still does not show linked to libthr, I have no clue what causes
that on your system. I'd inspect /etc/libmap.conf, /etc/make.conf, the
config.log for qt33 and the final link command that produces the uic
binary.

I just did
bsdpc01# pkg_info | grep qt3
and found no qt33 installed!


That could be, cause the port is called qt33 but the package once installed 
qt-3 or qt-copy-3 :P

Better: pkg_info qt-*


Now after portupgrade -Rf x11-toolkits/qt33 is seems as if I still have 
the problem.


bsdpc01# ldd /usr/local/bin/uic
/usr/local/bin/uic:
libqt-mt.so.3 = /usr/local/lib/libqt-mt.so.3 (0x280d)
libmng.so.1 = /usr/local/lib/libmng.so.1 (0x287b2000)
libjpeg.so.9 = /usr/local/lib/libjpeg.so.9 (0x28813000)
libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28832000)
libz.so.4 = /lib/libz.so.4 (0x28857000)
libXi.so.6 = /usr/local/lib/libXi.so.6 (0x28869000)
libXrender.so.1 = /usr/local/lib/libXrender.so.1 (0x28871000)
libXrandr.so.2 = /usr/local/lib/libXrandr.so.2 (0x28879000)
libXcursor.so.1 = /usr/local/lib/libXcursor.so.1 (0x2888)
libXinerama.so.1 = /usr/local/lib/libXinerama.so.1 (0x28889000)
libXft.so.2 = /usr/local/lib/libXft.so.2 (0x2888c000)
libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x2889e000)
libfontconfig.so.1 = /usr/local/lib/libfontconfig.so.1 
(0x2890c000)

libXext.so.6 = /usr/local/lib/libXext.so.6 (0x28936000)
libX11.so.6 = /usr/local/lib/libX11.so.6 (0x28944000)
libSM.so.6 = /usr/local/lib/libSM.so.6 (0x28a31000)
libICE.so.6 = /usr/local/lib/libICE.so.6 (0x28a39000)
libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x28a5)
libm.so.5 = /lib/libm.so.5 (0x28b45000)
libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x28b5a000)
libc.so.7 = /lib/libc.so.7 (0x28b65000)
libaudio.so.2 = /usr/local/lib/libaudio.so.2 (0x28c61000)
libXt.so.6 = /usr/local/lib/libXt.so.6 (0x28c77000)
liblcms.so.1 = /usr/local/lib/liblcms.so.1 (0x28cc7000)
libXfixes.so.3 = /usr/local/lib/libXfixes.so.3 (0x28cf7000)
libexpat.so.6 = /usr/local/lib/libexpat.so.6 (0x28cfc000)
libXau.so.6 = /usr/local/lib/libXau.so.6 (0x28d1c000)
libXdmcp.so.6 = /usr/local/lib/libXdmcp.so.6 (0x28d1f000)
librpcsvc.so.4 = /usr/lib/librpcsvc.so.4 (0x28d24000)


What do you suggest I do now?

/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


[Fwd: Re: Compile error, kde related?]

2008-03-14 Thread Leslie Jensen



Mutex unlock failure: Operation not permitted


I think you mixed some threading libraries. That string or variants of 
it, is

nowhere to be found in /usr/src anymore.

I found this post:
http://lists.freebsd.org/pipermail/freebsd-threads/2004-March/001759.html

Any of that relevant for you? like entries in libmap?

--
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.



Thank you Mel. I'll check it out.

By the way, I tried to CC your mailaddress but it bounced.

If you want the information from the bounced mail, Please let me know.

Thanks
/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-14 Thread Leslie Jensen


I think you mixed some threading libraries. That string or variants of it, is 
nowhere to be found in /usr/src anymore.


I found this post:
http://lists.freebsd.org/pipermail/freebsd-threads/2004-March/001759.html

Any of that relevant for you? like entries in libmap?



I read the thread and checked my libmap.conf. There's none of the 
entries mentioned in the post.


I'd like to add that my system is an upgraded 7.0 - release from 6.2.
I made pkg_delete -a because I had a problem with libcrypt that I 
couldn't fix.


I'll appreciate any hint.

Thanks
/Leslie

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Re: Compile error, kde related?

2008-03-14 Thread Leslie Jensen
I don't know if it can be of any help but if I ctrl-c the cli when the 
compiling hangs I get the following.



Mutex unlock failure: Operation not permitted
^Cgmake[2]: *** Deleting file `kdcopview.cpp'
gmake[2]: *** [kdcopview.cpp] Interrupt: 2
gmake[1]: *** [all-recursive] Interrupt: 2
gmake: *** [all] Interrupt: 2


/Leslie



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-14 Thread Leslie Jensen


Ok, the error is generated by uic:
./src/tools/qmutex_unix.cpp:qWarning(Mutex unlock failure: %s, 
strerror(ret));


Which fails on pthread_mutex_unlock call.
Could you show the output of:
ldd /usr/local/bin/uic



bsdpc01# ldd /usr/local/bin/uic
/usr/local/bin/uic:
libqt-mt.so.3 = /usr/local/lib/libqt-mt.so.3 (0x280d)
libmng.so.1 = /usr/local/lib/libmng.so.1 (0x287b2000)
libjpeg.so.9 = /usr/local/lib/libjpeg.so.9 (0x28813000)
libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28832000)
libz.so.4 = /lib/libz.so.4 (0x28857000)
libXi.so.6 = /usr/local/lib/libXi.so.6 (0x28869000)
libXrender.so.1 = /usr/local/lib/libXrender.so.1 (0x28871000)
libXrandr.so.2 = /usr/local/lib/libXrandr.so.2 (0x28879000)
libXcursor.so.1 = /usr/local/lib/libXcursor.so.1 (0x2888)
libXinerama.so.1 = /usr/local/lib/libXinerama.so.1 (0x28889000)
libXft.so.2 = /usr/local/lib/libXft.so.2 (0x2888c000)
libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x2889e000)
libfontconfig.so.1 = /usr/local/lib/libfontconfig.so.1 
(0x2890c000)

libXext.so.6 = /usr/local/lib/libXext.so.6 (0x28936000)
libX11.so.6 = /usr/local/lib/libX11.so.6 (0x28944000)
libSM.so.6 = /usr/local/lib/libSM.so.6 (0x28a31000)
libICE.so.6 = /usr/local/lib/libICE.so.6 (0x28a39000)
libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x28a5)
libm.so.5 = /lib/libm.so.5 (0x28b45000)
libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x28b5a000)
libc.so.7 = /lib/libc.so.7 (0x28b65000)
libaudio.so.2 = /usr/local/lib/libaudio.so.2 (0x28c61000)
libXt.so.6 = /usr/local/lib/libXt.so.6 (0x28c77000)
liblcms.so.1 = /usr/local/lib/liblcms.so.1 (0x28cc7000)
libXfixes.so.3 = /usr/local/lib/libXfixes.so.3 (0x28cf7000)
libexpat.so.6 = /usr/local/lib/libexpat.so.6 (0x28cfc000)
libXau.so.6 = /usr/local/lib/libXau.so.6 (0x28d1c000)
libXdmcp.so.6 = /usr/local/lib/libXdmcp.so.6 (0x28d1f000)
librpcsvc.so.4 = /usr/lib/librpcsvc.so.4 (0x28d24000)

/Leslie
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-14 Thread Mel
On Friday 14 March 2008 09:12:22 Leslie Jensen wrote:
  I think you mixed some threading libraries. That string or variants of
  it, is nowhere to be found in /usr/src anymore.
 
  I found this post:
  http://lists.freebsd.org/pipermail/freebsd-threads/2004-March/001759.html
 
  Any of that relevant for you? like entries in libmap?

 I read the thread and checked my libmap.conf. There's none of the
 entries mentioned in the post.

 I'd like to add that my system is an upgraded 7.0 - release from 6.2.
 I made pkg_delete -a because I had a problem with libcrypt that I
 couldn't fix.

 I'll appreciate any hint.

Ok, the error is generated by uic:
./src/tools/qmutex_unix.cpp:qWarning(Mutex unlock failure: %s, 
strerror(ret));

Which fails on pthread_mutex_unlock call.
Could you show the output of:
ldd /usr/local/bin/uic


-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-14 Thread Mel
On Friday 14 March 2008 10:43:29 Leslie Jensen wrote:
  Ok, the error is generated by uic:
  ./src/tools/qmutex_unix.cpp:qWarning(Mutex unlock failure: %s,
  strerror(ret));
 
  Which fails on pthread_mutex_unlock call.
  Could you show the output of:
  ldd /usr/local/bin/uic

 bsdpc01# ldd /usr/local/bin/uic
 /usr/local/bin/uic:
  libqt-mt.so.3 = /usr/local/lib/libqt-mt.so.3 (0x280d)
  libmng.so.1 = /usr/local/lib/libmng.so.1 (0x287b2000)
  libjpeg.so.9 = /usr/local/lib/libjpeg.so.9 (0x28813000)
  libpng.so.5 = /usr/local/lib/libpng.so.5 (0x28832000)
  libz.so.4 = /lib/libz.so.4 (0x28857000)
  libXi.so.6 = /usr/local/lib/libXi.so.6 (0x28869000)
  libXrender.so.1 = /usr/local/lib/libXrender.so.1 (0x28871000)
  libXrandr.so.2 = /usr/local/lib/libXrandr.so.2 (0x28879000)
  libXcursor.so.1 = /usr/local/lib/libXcursor.so.1 (0x2888)
  libXinerama.so.1 = /usr/local/lib/libXinerama.so.1 (0x28889000)
  libXft.so.2 = /usr/local/lib/libXft.so.2 (0x2888c000)
  libfreetype.so.9 = /usr/local/lib/libfreetype.so.9 (0x2889e000)
  libfontconfig.so.1 = /usr/local/lib/libfontconfig.so.1
 (0x2890c000)
  libXext.so.6 = /usr/local/lib/libXext.so.6 (0x28936000)
  libX11.so.6 = /usr/local/lib/libX11.so.6 (0x28944000)
  libSM.so.6 = /usr/local/lib/libSM.so.6 (0x28a31000)
  libICE.so.6 = /usr/local/lib/libICE.so.6 (0x28a39000)
  libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x28a5)
  libm.so.5 = /lib/libm.so.5 (0x28b45000)
  libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x28b5a000)
  libc.so.7 = /lib/libc.so.7 (0x28b65000)
  libaudio.so.2 = /usr/local/lib/libaudio.so.2 (0x28c61000)
  libXt.so.6 = /usr/local/lib/libXt.so.6 (0x28c77000)
  liblcms.so.1 = /usr/local/lib/liblcms.so.1 (0x28cc7000)
  libXfixes.so.3 = /usr/local/lib/libXfixes.so.3 (0x28cf7000)
  libexpat.so.6 = /usr/local/lib/libexpat.so.6 (0x28cfc000)
  libXau.so.6 = /usr/local/lib/libXau.so.6 (0x28d1c000)
  libXdmcp.so.6 = /usr/local/lib/libXdmcp.so.6 (0x28d1f000)
  librpcsvc.so.4 = /usr/lib/librpcsvc.so.4 (0x28d24000)


There's your problem. I don't see a libpthread or better on 7.x a libthr.so 
linked in:

libthr.so.3 = /lib/libthr.so.3 (0x38b55000)

is what it shows on my 7.x system.

So the question is, why isn't qt built with thread support. I don't see how 
that's possible with the current ports makefile.
Do you have a file /lib/libthr.so*?

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-13 Thread Leslie Jensen


Mel skrev:

On Wednesday 12 March 2008 15:28:25 Leslie Jensen wrote:


The compile error I get is

Mutex unlock failure: Operation not permitted

   Any suggestions?


Details maybe? Just one line that's a pretty generic error message, that's 
likely to be caused by system limits, isn't gonna get you much help.
The entire compilation line, the failure up until make returns control back to 
the shell, that's what you'll need to provide at minimum.




Yes of course, here are some details:

bsdpc01# uname -a
FreeBSD bsdpc01.homenet.home 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 
24 19:59:52 UTC 2008 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386



portsnap fetch update

All ports up to date, otherwise compiled and installed.

cd /usr/ports/x11/kdebase3/

make


c++ -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include  -I/usr/local/include 
 -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT   -I/usr/local/include 
-I/usr/local/include  -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE 
-D_LARGE_FILES=1  -Wno-long-long -Wundef -Wall -W -Wpointer-arith 
-DNDEBUG -DNO_DEBUG -O2 -O2 -fno-strict-aliasing -pipe 
-Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common 
-DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT 
-DQT_NO_TRANSLATION -D_GNU_SOURCE  -MT kdcoplistview.o -MD -MP -MF 
.deps/kdcoplistview.Tpo -c -o kdcoplistview.o kdcoplistview.cpp

mv -f .deps/kdcoplistview.Tpo .deps/kdcoplistview.Po
/usr/local/bin/moc kdcopview.h -o kdcopview.moc
rm -f kdcopview.cpp
echo '#include kdialog.h'  kdcopview.cpp
echo '#include klocale.h'  kdcopview.cpp
/usr/local/bin/uic -L /usr/local/lib/kde3/plugins/designer -nounload -tr 
tr2i18n -i kdcopview.h ./kdcopview.ui  kdcopview.cpp.temp ; ret=$?; \
/usr/local/bin/perl -pe s,tr2i18n( \\ ),QString::null,g 
kdcopview.cpp.temp | /usr/local/bin/perl -pe s,tr2i18n( \\\, \\ 
),QString::null,g | /usr/local/bin/perl -pe 
s,image([0-9][0-9]*)_data,img\$1_kdcopview,g | /usr/local/bin/perl -pe 
s,: QWizard\(,: KWizard(,g  kdcopview.cpp ;\

rm -f kdcopview.cpp.temp ;\
if test $ret = 0; then echo '#include kdcopview.moc'  
kdcopview.cpp; else rm -f kdcopview.cpp ; exit $ret ; fi

Mutex unlock failure: Operation not permitted

--

After this the cli just hangs! Processor goes idle.

Disk and memory looks good.

/Leslie

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-13 Thread Mel
On Thursday 13 March 2008 08:46:08 Leslie Jensen wrote:
 Mel skrev:
  On Wednesday 12 March 2008 15:28:25 Leslie Jensen wrote:
  The compile error I get is
 
  Mutex unlock failure: Operation not permitted
 
 Any suggestions?
 
  Details maybe? Just one line that's a pretty generic error message,
  that's likely to be caused by system limits, isn't gonna get you much
  help. The entire compilation line, the failure up until make returns
  control back to the shell, that's what you'll need to provide at minimum.

 Yes of course, here are some details:

 bsdpc01# uname -a
 FreeBSD bsdpc01.homenet.home 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb
 24 19:59:52 UTC 2008
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386


 portsnap fetch update

 All ports up to date, otherwise compiled and installed.

 cd /usr/ports/x11/kdebase3/

 make

 
 c++ -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include  -I/usr/local/include
   -D_THREAD_SAFE -pthread -DQT_THREAD_SUPPORT   -I/usr/local/include
 -I/usr/local/include  -I/usr/local/include -D_GETOPT_H -D_THREAD_SAFE
 -D_LARGE_FILES=1  -Wno-long-long -Wundef -Wall -W -Wpointer-arith
 -DNDEBUG -DNO_DEBUG -O2 -O2 -fno-strict-aliasing -pipe
 -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common
 -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT
 -DQT_NO_TRANSLATION -D_GNU_SOURCE  -MT kdcoplistview.o -MD -MP -MF
 .deps/kdcoplistview.Tpo -c -o kdcoplistview.o kdcoplistview.cpp
 mv -f .deps/kdcoplistview.Tpo .deps/kdcoplistview.Po
 /usr/local/bin/moc kdcopview.h -o kdcopview.moc
 rm -f kdcopview.cpp
 echo '#include kdialog.h'  kdcopview.cpp
 echo '#include klocale.h'  kdcopview.cpp
 /usr/local/bin/uic -L /usr/local/lib/kde3/plugins/designer -nounload -tr
 tr2i18n -i kdcopview.h ./kdcopview.ui  kdcopview.cpp.temp ; ret=$?; \
  /usr/local/bin/perl -pe s,tr2i18n( \\ ),QString::null,g
 kdcopview.cpp.temp | /usr/local/bin/perl -pe s,tr2i18n( \\\, \\
 ),QString::null,g | /usr/local/bin/perl -pe
 s,image([0-9][0-9]*)_data,img\$1_kdcopview,g | /usr/local/bin/perl -pe
 s,: QWizard\(,: KWizard(,g  kdcopview.cpp ;\
  rm -f kdcopview.cpp.temp ;\
  if test $ret = 0; then echo '#include kdcopview.moc' 
 kdcopview.cpp; else rm -f kdcopview.cpp ; exit $ret ; fi
 Mutex unlock failure: Operation not permitted

I think you mixed some threading libraries. That string or variants of it, is 
nowhere to be found in /usr/src anymore.

I found this post:
http://lists.freebsd.org/pipermail/freebsd-threads/2004-March/001759.html

Any of that relevant for you? like entries in libmap?

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Compile error, kde related?

2008-03-12 Thread Leslie Jensen

I've done pkg_delete -a on a newly upgraded 7.0-RELEASE.

After installing approx. 400 ports I'm trying to install kdebase, 
kdegames and kdeutils. I do not want to install the kde-metaport that's 
why I go about it this way.


The compile error I get is

Mutex unlock failure: Operation not permitted

  Any suggestions?

Thanks
Leslie


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Compile error, kde related?

2008-03-12 Thread Mel
On Wednesday 12 March 2008 15:28:25 Leslie Jensen wrote:

 The compile error I get is

 Mutex unlock failure: Operation not permitted

Any suggestions?

Details maybe? Just one line that's a pretty generic error message, that's 
likely to be caused by system limits, isn't gonna get you much help.
The entire compilation line, the failure up until make returns control back to 
the shell, that's what you'll need to provide at minimum.

-- 
Mel

Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]