https://bugs.kde.org/show_bug.cgi?id=374196

--- Comment #3 from Ralf Habacker <ralf.habac...@freenet.de> ---
(In reply to David Faure from comment #1)
> Is this with -j or something? kssld has nothing to do with kio_trash.

build log without any -j follows:

make[2]: Entering directory '/home/abuild/rpmbuild/BUILD/kio-5.29.0/build'
[ 68%] Building CXX object
src/ioslaves/trash/CMakeFiles/kio_trash.dir/kio_trash_win.cpp.obj
cd /home/abuild/rpmbuild/BUILD/kio-5.29.0/build/src/ioslaves/trash &&
/usr/bin/i686-w64-mingw32-g++   -DKCOREADDONS_LIB -DQT_CORE_LIB -DQT_DBUS_LIB
-DQT_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_SIGNALS_SLOTS_KEYWORDS
-DQT_NO_URL_CAST_FROM_STRING -DQT_USE_FAST_OPERATOR_PLUS
-DQT_USE_QSTRINGBUILDER -DQT_XML_LIB -DTRANSLATION_DOMAIN=\"kio5\" -DUNICODE
-DWIN32_LEAN_AND_MEAN -DWINVER=0x0600 -D_CRT_NONSTDC_NO_DEPRECATE
-D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_SCL_SECURE_NO_WARNINGS
-D_UNICODE -D_USE_MATH_DEFINES -D_WIN32_IE=0x0600 -D_WIN32_WINNT=0x0600
-Dkio_trash_EXPORTS @CMakeFiles/kio_trash.dir/includes_CXX.rsp
-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2
-fstack-protector -funwind-tables -fasynchronous-unwind-tables -DNDEBUG
-fno-stack-protector -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align
-Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -pedantic
-fvisibility=hidden -fno-keep-inline-dllexport   -o
CMakeFiles/kio_trash.dir/kio_trash_win.cpp.obj -c
/home/abuild/rpmbuild/BUILD/kio-5.29.0/src/ioslaves/trash/kio_trash_win.cpp
/home/abuild/rpmbuild/BUILD/kio-5.29.0/src/ioslaves/trash/kio_trash_win.cpp:26:27:
fatal error: kiotrashdebug.h: No such file or directory
 #include "kiotrashdebug.h"
                           ^   
> As to the kio_trash_win.cpp error, isn't there a kiotrashdebug.h in the same
> source dir? Is -I. missing somehow?

in kio 5.29 source there is no kiotrashdebug.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to