I disabled the -j4 flag.
I don't understand why the -j4 flag works with Slackware and the stock 3.5.10 but not Trinity. Compiling KDE is slow enough already. :(
I tried again and the build failed. This time without the -j4 flag the failure message referred to menutab_impl.cpp.
Attached is a log.
Hello,
There is initial work for arts cmake script. Now arts is compilable, but for
the moment is no support for ALSA, VORBIS etc.
Problems:
1) In mcoputils.cc must be inserted #include <limits.h>
2) ALSA support refuse to compile, because this error:
[ 68%] Building CXX object flow/CMakeFiles/artsflow.dir/audioioalsa9.cc.o
/home/serghei/projects/trinity/dependencies/arts/flow/audioioalsa9.cc: In
member function 'int Arts::AudioIOALSA::setPcmParams(snd_pcm_t*)':
/home/serghei/projects/trinity/dependencies/arts/flow/audioioalsa9.cc:543:
error: invalid conversion from 'int' to 'unsigned int*'
/home/serghei/projects/trinity/dependencies/arts/flow/audioioalsa9.cc:543:
error: initializing argument 3 of 'int
snd_pcm_hw_params_set_rate_near(snd_pcm_t*, snd_pcm_hw_params_t*, unsigned
int*, int*)'
/home/serghei/projects/trinity/dependencies/arts/flow/audioioalsa9.cc:565:
error: invalid conversion from 'int' to 'snd_pcm_uframes_t*'
/home/serghei/projects/trinity/dependencies/arts/flow/audioioalsa9.cc:565:
error: initializing argument 3 of 'int
snd_pcm_hw_params_set_period_size_near(snd_pcm_t*, snd_pcm_hw_params_t*,
snd_pcm_uframes_t*, int*)'
/home/serghei/projects/trinity/dependencies/arts/flow/audioioalsa9.cc:570:
error: invalid conversion from 'int' to 'unsigned int*'
/home/serghei/projects/trinity/dependencies/arts/flow/audioioalsa9.cc:570:
error: initializing argument 3 of 'int
snd_pcm_hw_params_set_periods_near(snd_pcm_t*, snd_pcm_hw_params_t*, unsigned
int*, int*)'
make[2]: *** [flow/CMakeFiles/artsflow.dir/audioioalsa9.cc.o] Error 1
make[1]: *** [flow/CMakeFiles/artsflow.dir/all] Error 2
make: *** [all] Error 2
If anybody knows how to fix it, please tell me.
--
Serghei
> Try adding #include <stdlib.h> directly above the
> previous added #include
> statement.
Same exact failure. Seems there is something wrong with main.cpp.
Hello,
I found that tqt.h is modified only at install stage. If I define USE_QT3
before compilation, the compilation stop with this error:
tqinputcontext.h:32:27: error: qinputcontext.h: No such file or directory
This is intended behaviour? If yes, for what purpose is designed in this way?
--
Serghei
I'm attaching a new log for building kdebase.
I can build arts and kdelibs.
I think I discovered why the builds on the virtual machine were so much slower. I was using a single processor kernel rather than smp. I'll fix that and hopefully that eliminates that particular problem.
I have yet to figure out why nothing compiles in the chroot environment.
Darrell
Attached is a log of the failed kdebase build.
The follwing message appears several times:
TEPty.h:43: error: invalid use of incomplete type 'struct KPty'
Another message:
/usr/include/kprocess.h:34: error: forward declaration of 'struct KPty'
I checked /usr/include and kprocess.h is installed from my previous kdelibs svn package.
Darrell
I'm stumped. The problem is with my chroot environment.
I spent the past few hours whittling away at both the chroot environment and the virtual machine trying to find the difference. Currently, as far as package installations go, the two machines are identical.
Granted, although sandboxed, the chroot is not perfectly isolated like the virtual machine. Something is confusing the build process in the chroot environment that the virtual machine can't see. A chroot environment is not supposed to be able to see above/outside its internal root level. Thus I don't know what the chroot environment sees that the virtual machine can't.
I can build in the virtual machine but as I mentioned previously, the build process is slower than on physical hardware. I wanted the chroot environment so I could use the physical hardware and build faster.
I'll see how far I get rebuilding arts and kdelibs in the virtual machine. Then I'll try kdebase with your changes from a couple of days ago. I'll keep troubleshooting with the chroot environment too.
With that said, I am attaching a new log of the failed arts build in the chroot environment. Perhaps something there might provide you a clue where I can troubleshoot or what might cause arts to fail in one environment but not the other.
Oops. I forgot to attach the log!
