[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Use of uninitialized value in qt-copy/bin/syncqt line 337.
From:       Michael Pyne <mpyne () kde ! org>
Date:       2011-06-09 1:14:26
Message-ID: 2930778.elVoXcoEKY () midna
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday, June 08, 2011 15:26:00 Nick Savoiu wrote:
> Hi,
> 
> Long time KDE3 user trying to get up to speed with KDE4. I've stayed away
> from it so far as I found building it from sources (like I did for KDE3)
> much more daunting.
> 
> I'm building trunk using kdesrc-build on RedHat Enterprise Linux 4.5 64bit
> and running into the following
> 
> [tahoe:kdesrc-build-1.13]$ ./kdesrc-build --no-src
> Script started processing at Wed Jun  8 14:26:10 2011
> <<<  Build Process  >>>
> Building qt-copy (1/26)
>         Preparing build system for qt-copy.
>         Removing files in build directory for qt-copy
>         Old build system cleaned, starting new build system.
>         LGPL license selected for Qt.  See
> /scr/tahoe-s1/nos/prjs/kdesrc-build-1.13/dwnld//qt-copy/LICENSE.LGPL
>         Running configure...
> Use of uninitialized value in utime at
> /scr/tahoe-s1/nos/prjs/kdesrc-build-1.13/dwnld/qt-copy/bin/syncqt line 337.
> Use of uninitialized value in utime at
> /scr/tahoe-s1/nos/prjs/kdesrc-build-1.13/dwnld/qt-copy/bin/syncqt line 337.
> 
> It's my first time using kdesrc-build so I'm not sure why the error message.

The error message itself comes from Qt's syncqt script, which is being run by 
configure to setup the qt-copy build directory.

It /is/ possible that the Qt devs are using a Perl feature not supported on 
RHEL 4.5 (I'm honestly not sure what version of Perl that corresponds to).

kdesrc-build itself requires Perl 5.10 in the next release, although kdesrc-
build 1.13 should work for the most part for what you're doing.

The kdesrc-buildrc-sample file is modified every so often in git [1], so you 
may want to examine the current sample rc file to see what the changes are 
versus the one in 1.13.

Given that you used to run KDE 3, KDE 4's build system is different in that it 
uses CMake, but mostly in that many of the major KDE modules have been split 
down to the major component, library, and application level in git. As an 
example, kdebase has become kde-runtime (for non-library runtime 
dependencies), kde-workspace (containing the standard Plasma desktop), and 
kde-baseapps (standard kde applications like dolphin and konqueror). 
Noticeably absent from that list is konsole, which is now its own separate git 
module.

To help with the extra complexity that the split entails, the modules are 
organized on projects.kde.org into some hierarchical grouping. For instance, 
the applications formerly in kdeedu can be found in 
https://projects.kde.org/projects/kde/kdeedu. That data is also exposed in an 
XML format which kdesrc-build and some other KDE tools can use. The way 
kdesrc-build supports this is to allow for selecting a given component from 
projects.kde.org (in this case, "kde/kdeedu", or just plain "kdeedu" if you're 
not worried about other components having that name anywhere), and kdesrc-
build will recursively checkout and build the subprojects in that group. This 
uses the module-set feature, and you can see some examples in the kdesrc-
buildrc-sample in git master.

Most of this might be moot if you're not able to get the library dependencies 
installed though, which is the most likely source of trouble if you get CMake 
failures.

I hope this helps.

Regards,
 - Michael Pyne

[1] http://quickgit.kde.org/?p=kdesrc-build.git&a=tree
["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]