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
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/q
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
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
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
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
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
_
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 tha
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
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
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
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
>
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 =>
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 o
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: **
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 ch
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? li
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 prett
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
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 muc
20 matches
Mail list logo