22 Jan
2012
22 Jan
'12
5:35 p.m.
I am unable to build tdelibs when I use tqt3 rather than qt3. I can build tdelibs with
qt3.
GIT 2805.
Build log failure:
In file included from /dev/shm/tdelibs/dcop/dcopclient.cpp:2285:
/dev/shm/tdelibs.build/dcop/dcopclient.moc:121: error: ISO C++ forbids declaration of
'QCString' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:121: error: expected ',' or
'...' before '&' token
/dev/shm/tdelibs.build/dcop/dcopclient.moc:121: error: prototype for 'void
DCOPClient::applicationRegistered(int)' does not match any in class
'DCOPClient'
/dev/shm/tdelibs/dcop/dcopclient.h:745: error: candidate is: void
DCOPClient::applicationRegistered(const TQCString&)
/dev/shm/tdelibs.build/dcop/dcopclient.moc:134: error: ISO C++ forbids declaration of
'QCString' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:134: error: expected ',' or
'...' before '&' token
/dev/shm/tdelibs.build/dcop/dcopclient.moc:134: error: prototype for 'void
DCOPClient::applicationRemoved(int)' does not match any in class 'DCOPClient'
/dev/shm/tdelibs/dcop/dcopclient.h:754: error: candidate is: void
DCOPClient::applicationRemoved(const TQCString&)
/dev/shm/tdelibs.build/dcop/dcopclient.moc:166: error: ISO C++ forbids declaration of
'QCString' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:166: error: expected ',' or
'...' before '&' token
/dev/shm/tdelibs.build/dcop/dcopclient.moc:166: error: prototype for 'void
DCOPClient::callBack(int, int)' does not match any in class 'DCOPClient'
/dev/shm/tdelibs/dcop/dcopclient.h:794: error: candidate is: void
DCOPClient::callBack(int, const TQCString&, const TQByteArray&)
/dev/shm/tdelibs.build/dcop/dcopclient.moc: In member function 'virtual bool
DCOPClient::qt_emit(int, TQUObject*)':
/dev/shm/tdelibs.build/dcop/dcopclient.moc:196: error: ISO C++ forbids declaration of
'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:196: error: ISO C++ forbids declaration of
'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:196: error: expected primary-expression before
'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:196: error: expected ')' before
'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:197: error: ISO C++ forbids declaration of
'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:197: error: ISO C++ forbids declaration of
'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:197: error: expected primary-expression before
'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:197: error: expected ')' before
'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:200: error: ISO C++ forbids declaration of
'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:200: error: ISO C++ forbids declaration of
'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:200: error: expected primary-expression before
'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:200: error: expected ')' before
'const'
make[2]: *** [dcop/CMakeFiles/DCOP-shared.dir/dcopclient.cpp.o] Error 1
make[2]: Leaving directory `/dev/shm/tdelibs.build'
make[1]: *** [dcop/CMakeFiles/DCOP-shared.dir/all] Error 2
make[1]: Leaving directory `/dev/shm/tdelibs.build'
make: *** [all] Error 2
Darrell
23 Jan
23 Jan
12:33 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
I am unable to build tdelibs when I
use tqt3 rather than qt3. I can build tdelibs with qt3.
GIT 2805.
In tqt3 I reversed the visibility patch and that had no effect. I remain unable to build
tdelibs with tqt3.
Darrell
1:08 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
I am unable to build tdelibs when I use tqt3 rather
than qt3. I can build
tdelibs with qt3.
GIT 2805.
Build log failure:
In file included from /dev/shm/tdelibs/dcop/dcopclient.cpp:2285:
/dev/shm/tdelibs.build/dcop/dcopclient.moc:121: error: ISO C++ forbids
declaration of 'QCString' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:121: error: expected ',' or
'...' before '&' token
/dev/shm/tdelibs.build/dcop/dcopclient.moc:121: error: prototype for 'void
DCOPClient::applicationRegistered(int)' does not match any in class
'DCOPClient'
/dev/shm/tdelibs/dcop/dcopclient.h:745: error: candidate is: void
DCOPClient::applicationRegistered(const TQCString&)
/dev/shm/tdelibs.build/dcop/dcopclient.moc:134: error: ISO C++ forbids
declaration of 'QCString' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:134: error: expected ',' or
'...' before '&' token
/dev/shm/tdelibs.build/dcop/dcopclient.moc:134: error: prototype for 'void
DCOPClient::applicationRemoved(int)' does not match any in class
'DCOPClient'
/dev/shm/tdelibs/dcop/dcopclient.h:754: error: candidate is: void
DCOPClient::applicationRemoved(const TQCString&)
/dev/shm/tdelibs.build/dcop/dcopclient.moc:166: error: ISO C++ forbids
declaration of 'QCString' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:166: error: expected ',' or
'...' before '&' token
/dev/shm/tdelibs.build/dcop/dcopclient.moc:166: error: prototype for 'void
DCOPClient::callBack(int, int)' does not match any in class 'DCOPClient'
/dev/shm/tdelibs/dcop/dcopclient.h:794: error: candidate is: void
DCOPClient::callBack(int, const TQCString&, const TQByteArray&)
/dev/shm/tdelibs.build/dcop/dcopclient.moc: In member function 'virtual
bool DCOPClient::qt_emit(int, TQUObject*)':
/dev/shm/tdelibs.build/dcop/dcopclient.moc:196: error: ISO C++ forbids
declaration of 'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:196: error: ISO C++ forbids
declaration of 'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:196: error: expected
primary-expression before 'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:196: error: expected ')' before
'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:197: error: ISO C++ forbids
declaration of 'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:197: error: ISO C++ forbids
declaration of 'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:197: error: expected
primary-expression before 'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:197: error: expected ')' before
'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:200: error: ISO C++ forbids
declaration of 'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:200: error: ISO C++ forbids
declaration of 'type name' with no type
/dev/shm/tdelibs.build/dcop/dcopclient.moc:200: error: expected
primary-expression before 'const'
/dev/shm/tdelibs.build/dcop/dcopclient.moc:200: error: expected ')' before
'const'
make[2]: *** [dcop/CMakeFiles/DCOP-shared.dir/dcopclient.cpp.o] Error 1
make[2]: Leaving directory `/dev/shm/tdelibs.build'
make[1]: *** [dcop/CMakeFiles/DCOP-shared.dir/all] Error 2
make[1]: Leaving directory `/dev/shm/tdelibs.build'
make: *** [all] Error 2
Did you rebuild all dependency packages, including tqtinterface and arts,
before attempting to rebuild tdelibs?
1:59 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
OK, post the full build log somewhere. I suspect an
#included file is not
being found.
tdelibs build log:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
Darrell
2:07 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
OK, post the
full build log
somewhere. I suspect an
#included file is not
being found.
tdelibs build log:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
2:39 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
On 23 January 2012 17:07, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
A little strange. That first log was run with NUMJOBS=-j1.
I ran a second time with NUMJOBS=-j3 and the errors were different:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
tdelibs cannot be run with multiple jobs.
OK, post the full build log
somewhere. I
suspect an
#included file is not
being found.
tdelibs build log:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
2:42 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
On 23 January 2012 17:07, Darrell Anderson
<humanreadable(a)yahoo.com>
wrote:
A little strange. That first log was run with NUMJOBS=-j1.
I ran a second time with NUMJOBS=-j3 and the errors were different:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
tdelibs cannot be run with multiple jobs.
Umm...yes it can. I run it that way all the time on an 8 core build machine.
Tim
OK, post the full build log
somewhere. I
suspect an
#included file is not
being found.
tdelibs build log:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
2:47 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
On 23 January 2012 17:42, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
wow really? I was almost sure. bad memory maybe
On 23 January
2012 17:07, Darrell Anderson <humanreadable(a)yahoo.com>
wrote:
tdelibs cannot be run with multiple jobs.
Umm...yes it can. I run it that way all the time on an 8 core build machine.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> OK,
post the full build log
somewhere. I suspect an
> #included file is not
> being found.
tdelibs build log:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
A little strange. That first log was run with NUMJOBS=-j1.
I ran a second time with NUMJOBS=-j3 and the errors were different:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
2:59 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
On 23 January 2012 17:42, Timothy Pearson
<kb9vqf(a)pearsoncomputing.net>
wrote:
wow really? I was almost sure. bad memory maybe
Autotools was restricted to -j1, but CMake can work with as many cores as
you can give it.
Tim
On 23
January 2012 17:07, Darrell Anderson <humanreadable(a)yahoo.com>
wrote:
Umm...yes it can. I run it that way all the time on an 8 core build
machine.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
> > OK, post the full build log
> somewhere. I suspect an
> > #included file is not
> > being found.
>
> tdelibs build log:
>
>
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
A little strange. That first log was run with NUMJOBS=-j1.
I ran a second time with NUMJOBS=-j3 and the errors were different:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
tdelibs cannot be run with multiple jobs.
2:46 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
OK, post the full build log
somewhere. I
suspect an
#included file is not
being found.
tdelibs build log:
http://humanreadable.nfshost.com/trinity/build_logs/tdelibs-R14.0.0-i486-13…
2:56 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
Can you please post the full output of the
tqtinterface
build? It looks
like tqtinterface was not built in native TQt3 mode.
http://humanreadable.nfshost.com/trinity/build_logs/tqtinterface-R14.0.0-i4…
Darrell
3:06 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
Can you please
post the full output of the tqtinterface
build? It looks
like tqtinterface was not built in native TQt3 mode.
http://humanreadable.nfshost.com/trinity/build_logs/tqtinterface-R14.0.0-i4…
3:25 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
Basically the #define TQT_REAL_TQT is not being set.
tqt3 sets that
define in qglobal.h, so one of the only ways for the build
to break is if
the wrong qglobal.h file is being included.
Can you verify that you only have one copy of qglobal.h on
your system,
and that TQT_REAL_TQT is #defined to 1 in that file?
I cleaned the build system and rebuilt tqtinterface. After installing, I had the following
qglobal.h files:
/usr/lib/qt/include/Qt/qglobal.h
/usr/lib/qt/include/QtCore/qglobal.h
/usr/include/tqt/Qt/qglobal.h
/usr/include/tqt/tqglobal.h
/opt/trinity/include/qglobal.h
I verified TQT_REAL_TQT is set to 1:
grep TQT_REAL_TQT /opt/trinity/include/qglobal.h
#define TQT_REAL_TQT 1
I have tqt3 installing to /opt/trinity and tqtinterface installing to /usr.
Here is a copy of the tqtinterface CMakeCache.txt:
http://humanreadable.nfshost.com/trinity/build_logs/CMakeCache.txt
Darrell
4:22 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
Basically the #define TQT_REAL_TQT is not being set.
tqt3 sets that define in qglobal.h, so one of the only ways for the build
to break is if the wrong qglobal.h file is being included.
How did you determine that? I could add some error checks in my build scripts if I knew on
what to key.
Darrell
4:24 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
Basically the
#define TQT_REAL_TQT is not being set.
tqt3 sets that define in qglobal.h, so one of the only ways for the
build
to break is if the wrong qglobal.h file is being included.
How did you determine that? I could add some error checks in my build
scripts if I knew on what to key.
5:21 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
> Basically
the #define
TQT_REAL_TQT is not being set.
> tqt3 sets that define in qglobal.h, so one of
the
only ways for the
> build
> to break is if the wrong qglobal.h file is being
included.
How did you determine that? I could add some error
checks in my build
scripts if I knew on what to key.
It's just a guess. :-) Try adding this line:
#define TQT_REAL_TQT 1
to the top of your installed tqt.h file, then try to
rebuild tdelibs.
Okay, tried that. Same failures. :(
I'm going to rebuild qt3 and tqt3 with NUMJOBS=-j1 so I can compare the build logs of
both.
Darrell
5:36 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
> Basically the #define
TQT_REAL_TQT is not
being set.
> tqt3 sets that define in qglobal.h, so one of
the
only ways for the
> build
> to break is if the wrong qglobal.h file is being
included.
How did you determine that? I could add some error
checks in my build
scripts if I knew on what to key.
It's just a guess. :-) Try adding this line:
#define TQT_REAL_TQT 1
to the top of your installed tqt.h file, then try to
rebuild tdelibs.
Okay, tried that. Same failures. :(
I'm going to rebuild qt3 and tqt3 with NUMJOBS=-j1 so I can compare the
build logs of both.
5:43 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
I have no idea what would be causing the build
failures at
this point.
Obviously everything works on Debian, so I can't reproduce
the FTBFS and
debug it here.
Well, we've been down this road before where things work in Debian and don't work
in Slackware. :) And as we saw only a few days ago, I could well have something configured
that is causing the builds to gag.
I would make sure that TQT_REAL_TQT is always set for
each
compiled file,
as the build will fail in the manner shown if TQT_REAL_TQT
is not set.
You're skipping some steps here. :) Make sure TQT_REAL_TQT is set where? Where and how
do I check?
Darrell
9:43 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
You're skipping some steps here. :) Make sure
TQT_REAL_TQT is set where?
Make sure that it is set to 1 via a #define
Where and how do I check?
One way would be to select a failing C++ file and insert the following
block after all the #include statements:
#ifdef TQT_REAL_TQT
#error TQT_REAL_TQT is SET
#else
#error TQT_REAL_TQT is NOT set
#endif
Tim
24 Jan
24 Jan
9:53 a.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
You're
skipping some steps here.
:) Make sure TQT_REAL_TQT is set where?
Make sure that it is set to 1 via a #define
Where and how do I check?
One way would be to select a failing C++ file and insert the
following
block after all the #include statements:
#ifdef TQT_REAL_TQT
#error TQT_REAL_TQT is SET
#else
#error TQT_REAL_TQT is NOT set
#endif
10:30 a.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
You're
skipping some steps here.
:) Make sure TQT_REAL_TQT is set where?
Make sure that it is set to 1 via a #define
Where and how do I check?
One way would be to select a failing C++ file and insert the
following
block after all the #include statements:
#ifdef TQT_REAL_TQT
#error TQT_REAL_TQT is SET
#else
#error TQT_REAL_TQT is NOT set
#endif
10:47 a.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
dcopclient.cpp:2288 contains the following:
#include <dcopclient.moc>
So the failure is in that moc file. I don't pretend to
understand moc files (yet), but I believe the moc files are
created by the qt3 compiler.
kstyle.cpp:2370 contains #include "kstyle.moc". So once
again the problem is a moc file.
I can manually edit these moc files to add a "T" prefix to any undeclared
"Q" functions referenced in the error messages. Then manually runmake again
(outside my build script) and the errors stop. Of course, I then run into a new set of
similar errors. I can repeat this process with success but there is no way to automate the
process.
I think I have narrowed the problem to how the moc files are being created. I don't
know whether that is related to TQT_REAL_TQT.
Darrell
11:06 a.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
On Tue, 24 Jan 2012 10:47:27 -0800 (PST)
Darrell Anderson <humanreadable(a)yahoo.com> wrote:
Do you use the
right moc ? I don't know how the new TQt3 works but if
the qt3 moc is used and nothing is done after that the generated .moc
file will use Q* classes rather than TQ* classes.
dcopclient.cpp:2288 contains the following:
#include <dcopclient.moc>
So the failure is in that moc file. I don't pretend to
understand moc files (yet), but I believe the moc files are
created by the qt3 compiler.
kstyle.cpp:2370 contains #include "kstyle.moc". So once
again the problem is a moc file.
I can manually edit these moc files to add a "T" prefix to any
undeclared "Q" functions referenced in the error messages. Then
manually runmake again (outside my build script) and the errors stop.
Of course, I then run into a new set of similar errors. I can repeat
this process with success but there is no way to automate the process.
I think I have narrowed the problem to how the moc files are being
created. I don't know whether that is related to TQT_REAL_TQT.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read
list messsages on the Web archive:
http://trinity-devel.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
12:47 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
On Tue, 24 Jan 2012 10:47:27 -0800 (PST)
Darrell Anderson <humanreadable(a)yahoo.com> wrote:
Do you use the
right moc ? I don't know how the new TQt3 works but if
the qt3 moc is used and nothing is done after that the generated .moc
file will use Q* classes rather than TQ* classes.
I have attached my dcopclient.moc file, generated today in a build from
GIT. It would be interesting to see a diff between this file and your
file; could you post one?
Thanks!
Tim
dcopclient.cpp:2288 contains the following:
#include <dcopclient.moc>
So the failure is in that moc file. I don't pretend to
understand moc files (yet), but I believe the moc files are
created by the qt3 compiler.
kstyle.cpp:2370 contains #include "kstyle.moc". So once
again the problem is a moc file.
I can manually edit these moc files to add a "T" prefix to any
undeclared "Q" functions referenced in the error messages. Then
manually runmake again (outside my build script) and the errors stop.
Of course, I then run into a new set of similar errors. I can repeat
this process with success but there is no way to automate the process.
I think I have narrowed the problem to how the moc files are being
created. I don't know whether that is related to TQT_REAL_TQT.
2:24 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
Do you use the
right moc ? I don't know how the new
TQt3 works but if
the qt3 moc is used and nothing is done after
that the
generated .moc
> file will use Q* classes rather than TQ* classes. I have attached my dcopclient.moc file, generated
today in a
build from
GIT. It would be interesting to see a diff between
this file and your
file; could you post one?
Here you go!
http://humanreadable.nfshost.com/trinity/build_logs/dcopclient.moc
Darrell
2:26 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
Do you use the right moc ? I don't know how the
new
TQt3 works but if
the qt3 moc is used and nothing is done after
that the
generated .moc
> file will use Q* classes rather than TQ* classes. I have attached my dcopclient.moc file, generated
today in a
build from
GIT. It would be interesting to see a diff between
this file and your
file; could you post one?
Here you go!
http://humanreadable.nfshost.com/trinity/build_logs/dcopclient.moc
2:40 p.m.
New subject: [trinity-devel] tdelibs FTBFS with tqt3
Well that doesn't look right. :-) Can you also
post
your tmoc and
tqt-replace-stream files (and also verify that there is only
one of each
file on your system)?
http://humanreadable.nfshost.com/trinity/build_logs/tmoc
http://humanreadable.nfshost.com/trinity/build_logs/tqt-replace
http://humanreadable.nfshost.com/trinity/build_logs/tqt-replace-stream
Only one of all three installed.
Darrell
4688
days inactive
4689
days old
28 comments
4 participants
participants (4)
-
/dev/ammo42 -
Calvin Morrison -
Darrell Anderson -
Timothy Pearson