tde-devels

devels@trinitydesktop.org

3805 discussions

Re: [trinity-devel] Building kdebase (failed)
by Darrell Anderson 03 Sep '10

03 Sep '10

> Try adding #include <stdlib.h> directly above the > previous added #include > statement. Same exact failure. Seems there is something wrong with main.cpp.

2 1

Re: [trinity-devel] Building kdebase (failed)
by Darrell Anderson 03 Sep '10

03 Sep '10

> Oops, I meant kdebase/kcontrol/kicker/menutab_impl.h Made the change. The build again failed. :( Attached is a new log.

2 3

tqt - cmake script done
by Serghei Amelian 02 Sep '10

02 Sep '10

Hello, In this moment cmake script for TQt is done (at least it work for me) and can be tested. -- Serghei

1 0

tqt.h confusion
by Serghei Amelian 02 Sep '10

02 Sep '10

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

2 8

Re: [trinity-devel] Building kdebase (failed)
by Darrell Anderson 02 Sep '10

02 Sep '10

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

2 3

Building kdebase (failed)
by Darrell Anderson 02 Sep '10

02 Sep '10

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

2 16

Re: [trinity-devel] Building arts (failed)
by Darrell Anderson 02 Sep '10

02 Sep '10

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!

1 0

tqtinterface compilation problem
by Serghei Amelian 01 Sep '10

01 Sep '10

Hello, I tried to compile tqtinterface, in this way: svn co svn://anonsvn.kde.org/home/kde/branches/trinity/dependencies/tqtinterface cd tqtinterface make -f admin/Makefile.common ./configure make Sources are compiled fine, but libtqt.so.4.2.0 is not created, only libtqt.la -- Serghei

2 12

Re: [trinity-devel] Building kdebase
by Darrell Anderson 31 Aug '10

31 Aug '10

I am attaching a log of the kdebase build attempt. In addition to the failure, please look at the following configure messages: ================================================== acinclude.m4:6591: warning: underquoted definition of _LT_AC_TRY_LINK ================================================== unknown icon type in kate/pics/Makefile.in (sessionchooser.png) ================================================== checking linux/cdrom.h usability... no checking linux/cdrom.h presence... yes configure: WARNING: linux/cdrom.h: present but cannot be compiled configure: WARNING: linux/cdrom.h: check for missing prerequisite headers? configure: WARNING: linux/cdrom.h: see the Autoconf documentation configure: WARNING: linux/cdrom.h: section "Present But Cannot Be Compiled" configure: WARNING: linux/cdrom.h: proceeding with the preprocessor's result configure: WARNING: linux/cdrom.h: in the future, the compiler will take precedence checking for linux/cdrom.h... yes ================================================== A header file exists at /usr/include/linux/cdrom.h

3 16

Re: [trinity-devel] tqtinterface compilation problem
by Darrell Anderson 31 Aug '10

31 Aug '10

--- On Mon, 8/30/10, Serghei Amelian <serghei(a)thel.ro> wrote: > From: Serghei Amelian <serghei(a)thel.ro> > Subject: Re: [trinity-devel] tqtinterface compilation problem > To: trinity-devel(a)lists.pearsoncomputing.net > Date: Monday, August 30, 2010, 6:12 PM > Actually --enable-qt4 is not recognized by configure script > at all. I tried > with plain "./configure", without parameters. > > > If you are compiling for Qt3, then something might be > amiss in your build > > setup. Please make sure you have all Qt > development headers installed, > > and if you don't mind posting the full output of the > commands you listed > > above I may be able to shed more light on the > problem. > > I using gentoo and I have already KDE-3 installed, so my > QT-3 setup is fine, I > think. > > I attached folowing files: > > log1.txt is output of "make -f admin/Makefile.common" > log2.txt is output of "./configure" > log3.txt is output of "make" > > Also, I attached config.log > > I'm not sure what meaning the message "You are attempting > to compile Trinity > without the Trinity Qt Interface installed. Please > install > libtqtinterface-dev and try again!" I discovered the hard way that trying to build the Trinity packages with KDE 3.5.10 installed will cause many headaches. I created a virtual machine without KDE installed and I built tqtinterface there. You still need qt3 installed. Also, you need to rebuild the make files with each package. Much is changed with Trinity include files and these make files need to be rebuilt. On my system I run the following commands in my build scripts: cp -Rp /usr/lib/build/libtool.m4 admin/libtool.m4.in cp -Rp /usr/lib/build/ltmain.sh admin/ltmain.sh make -f admin/Makefile.common Locations might be different for Gentoo. I'm attaching the build script I used to create a tqtinterface package for Slackware. Hopefully that provides some ideas of what you need in Gentoo. I hope that helps. Darrell

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels