Very Computer

> Hi

> I've seen postings relating to this problem, but I haven't
> seen a good solution yet.

> When I try to make kdelibs-2.2.1 and kdebase-2.2.1 the
> compilation fails with multiple missing moc files
> for example:
> favicons.cpp:37: favicons.moc: No such file or directory
> make[3]: *** [favicons.lo] Error 1
> make[3]: Leaving directory `/home/rdc/kdebase-2.2.1/libkonq/favicons'

> I have been able to install kdelibs by manually making every single
> necessary moc file by grepping on the Makefile in a directory for
> moc files and calling make on them. This is obviously a very
> tedious and time-consuming process and I don't want to have to
> repeat it to install kdebase.

> moc seems to be ok (i.e. installed correctly), since 'make <file>.moc'
> successfully creates the moc file.

> In 'config.cache' this line seems to be ok
> kde_cv_path_moc=${kde_cv_path_moc='/usr/lib/qt/bin/moc'}
> In Makefile (top level) this line seems to be ok
> MOC = /usr/lib/qt/bin/moc

> I have tried 'make -f Makefile.cvs' as suggested by a previous poster
> but that has not worked and I have pretty much run out of ideas apart
> from writing a shell script to manually and recursively make all the
> moc files before I compile.

> My system is RedHat Linux/2.4.9 and Qt version 2.3.1

> > When I try to make kdelibs-2.2.1 and kdebase-2.2.1 the
> > compilation fails with multiple missing moc files
> > for example:
> > favicons.cpp:37: favicons.moc: No such file or directory
> > make[3]: *** [favicons.lo] Error 1
> > make[3]: Leaving directory `/home/rdc/kdebase-2.2.1/libkonq/favicons'

> Wild guess:

> Do you have: "$QTDIR/bin" in your PATH?

> Does: "which moc" return the path to "moc"?

> JRT

>> > When I try to make kdelibs-2.2.1 and kdebase-2.2.1 the
>> > compilation fails with multiple missing moc files
>> > for example:
>> > favicons.cpp:37: favicons.moc: No such file or directory
>> > make[3]: *** [favicons.lo] Error 1
>> > make[3]: Leaving directory `/home/rdc/kdebase-2.2.1/libkonq/favicons'

>> Wild guess:

>> Do you have: "$QTDIR/bin" in your PATH?

>> Does: "which moc" return the path to "moc"?

>> JRT

>'which moc' gives me /bin/moc which is a symlink to
>/usr/local/qt/bin/moc.
>/usr/local/qt itself is a symlink to ./qt-2.3.1 .
>One thing that I don't understand
>is why ./configure asks me to change $QTDIR to be the
>kdebase source directory, instead of the qt directory
>itself. If I set QTDIR to be /usr/local/qt, then 'which
>moc' returns /usr/local/qt/bin/moc.

>The long and the short of this is that I don't think
>my problem is a path issue.

> > > When I try to make kdelibs-2.2.1 and kdebase-2.2.1 the
> > > compilation fails with multiple missing moc files
> > > for example:
> > > favicons.cpp:37: favicons.moc: No such file or directory
> > > make[3]: *** [favicons.lo] Error 1
> > > make[3]: Leaving directory `/home/rdc/kdebase-2.2.1/libkonq/favicons'

> > Wild guess:

> > Do you have: "$QTDIR/bin" in your PATH?

> > Does: "which moc" return the path to "moc"?

> > JRT

> 'which moc' gives me /bin/moc which is a symlink to
> /usr/local/qt/bin/moc.
> /usr/local/qt itself is a symlink to ./qt-2.3.1 .
> One thing that I don't understand
> is why ./configure asks me to change $QTDIR to be the
> kdebase source directory, instead of the qt directory
> itself. If I set QTDIR to be /usr/local/qt, then 'which
> moc' returns /usr/local/qt/bin/moc.

> The long and the short of this is that I don't think
> my problem is a path issue.

> > > > When I try to make kdelibs-2.2.1 and kdebase-2.2.1 the
> > > > compilation fails with multiple missing moc files
> > > > for example:
> > > > favicons.cpp:37: favicons.moc: No such file or directory
> > > > make[3]: *** [favicons.lo] Error 1
> > > > make[3]: Leaving directory `/home/rdc/kdebase-2.2.1/libkonq/favicons'

> > > Wild guess:

> > > Do you have: "$QTDIR/bin" in your PATH?

> > > Does: "which moc" return the path to "moc"?

> > > JRT

> > 'which moc' gives me /bin/moc which is a symlink to
> > /usr/local/qt/bin/moc.
> > /usr/local/qt itself is a symlink to ./qt-2.3.1 .
> > One thing that I don't understand
> > is why ./configure asks me to change $QTDIR to be the
> > kdebase source directory, instead of the qt directory
> > itself. If I set QTDIR to be /usr/local/qt, then 'which
> > moc' returns /usr/local/qt/bin/moc.

> > The long and the short of this is that I don't think
> > my problem is a path issue.

> To me, the above indicates a path problem.  Perhaps the link is
> confusing: "configure".

> I would remove the link ("/bin/moc") and add: "/usr/local/qt-2.3.1/bin"
> to your path:

> PATH=$PATH:/usr/local/qt-2.3.1/bin
> export PATH

> AND, you *must* have QTDIR=/usr/local/qt-2.3.1

> remove: "config.cache" and "config.log" and try it again.

> Also, did you build Qt-2.3.1 from source?  You will need to register:
> "/usr/local/qt-2.3.1/lib" with LD.  Add the path to the:
> "/etc/ld.so.conf" file and run: "ldconfig"

> JRT