Bug 173144 - #include <string.h> should be added to socketclient.cpp, dbushandler.cpp and socketserver.cpp
Summary: #include <string.h> should be added to socketclient.cpp, dbushandler.cpp and ...
Status: RESOLVED NOT A BUG
Alias: None
Product: kdesrc-build
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Solaris
: NOR normal
Target Milestone: ---
Assignee: Michael Pyne
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-19 15:07 UTC by Yevgeniy
Modified: 2009-01-02 21:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Yevgeniy 2008-10-19 15:07:19 UTC 
Version:            (using Devel)
Compiler:          GNU gcc (GCC) 4.3.2 
OS:                Solaris
Installed from:    Compiled sources

When building kdesupport from svn source (SVN 19-Oct-2008 revision 873351) I get following errors:

1.
kdesupport/strigi/src/daemon/socketclient.cpp: In member function 'int SocketClient::open()':
kdesupport/strigi/src/daemon/socketclient.cpp:53: error: 'strerror' was not declared in this scope
kdesupport/strigi/src/daemon/socketclient.cpp:58: error: 'memset' was not declared in this scope
kdesupport/strigi/src/daemon/socketclient.cpp:62: error: 'strncpy' was not declared in this scope
kdesupport/strigi/src/daemon/socketclient.cpp:69: error: 'strerror' was not declared in this scope

2.
kdesupport/strigi/src/daemon/dbus/dbuscpp/dbushandler.cpp:108: error: 'memset' was not declared in this scope

3.
kdesupport/strigi/src/daemon/socketserver.cpp:62: error: 'strncpy' was not declared in this scope
kdesupport/strigi/src/daemon/socketserver.cpp:109: error: 'strerror' was not declared in this scope

OS: Solaris x86, SunOS 5.11 (Solaris Express Community Edition Build 99)
compiler: gcc version 4.3.2
Comment 1 Michael Pyne 2009-01-02 21:42:14 UTC 
The compiler error you refer to appears to have been fixed by adding #include <cstring> to the affected files.

However, kdesvn-build is not the appropriate product to report compile errors against (the script just builds KDE, the compile would have failed with or without kdesvn-build's help).

Compile errors should normally be reported to the kde-devel mailing list for future reference.