I could not find this package ("kile-kde3"). Am I missing something or has it been removed?

It was never added for public download to the PPA due to the FTBFS (I don't have control over that, it a Launchpad rule).  If you want to work on the problem, I will be glad to send you the source code--just let me know!

I'd be interested in taking a look at this.  I couldn't find the tips.cpp file in the kile source packages in intrepid (2.0.1) or in the official kile packages (2.0.1, 2.0.2, 2.0.3).  I don't have an x86_64 architecture to test on, but would cross compile to get it built cleanly.

I have uploaded the source here: http://apt.pearsoncomputing.net/kile.uncompiled.tar.gz

As far as I can tell, it fails to build on all platforms, not just amd64.

If you get it working, just send the source back to me and I will upload to the PPA.

Thanks!

Thanks. I've also tried to build kile with gcc 4.3.2, but I got the same compiling error.

Sorry, but I'm not going to search for a solution for this bug, because for me it doesn't matter if I'm using kile or kate. Even the compilation feature of kile is not as good as a perfect makefile. And I like to use inotify_wait to run an automatic compilation after one of the documents changed, which is not possible in kile, I think.

I am confused now.  I have no problems at all with the source that you uploaded (without any modifications to it).  This is all I do
	wget http://apt.pearsoncomputing.net/kile.uncompiled.tar.gz
	tar -zxvf kile.uncompiled.tar.gz
	cd kile.uncompiled/kile-2.0.1
	dpkg-buildpackage
and this produces a deb package (in kile.uncopiled) without any errors concerning tips.cpp (no tips.cpp is ever compiled).  The package then installs cleanly with dpkg -i, and runs fine (I only opened an existing project, compiled and viewed the result).  Tips in English work too.  Are there any other build commands or targets that are expected by launchpad ppa?  Is there an easy way to reduce my local build environment to just what is available on launchpad (using a chroot jail).  I'm not an expert on debian packaging, as you can see...

This problem with tips.cpp was actually encountered before:
In https://bugs.launchpad.net/ubuntu/+source/kile/+bug/110779 a patch 07_remove_tips_cpp.diff was added, but this was included upstream in the 2.0 series (see Changelog of the ubuntu kile package).  The only thing the patch does is remove the tips.cpp file right after it is created by preparetips.  This still happens in the Makefiles that are included in your uploaded source archive, so no tips.cpp should ever exist long enough to be compiled.

(In reply to comment #6)
> I am confused now.  I have no problems at all with the source that you uploaded
> (without any modifications to it).  This is all I do
>     wget http://apt.pearsoncomputing.net/kile.uncompiled.tar.gz
>     tar -zxvf kile.uncompiled.tar.gz
>     cd kile.uncompiled/kile-2.0.1
>     dpkg-buildpackage
> and this produces a deb package (in kile.uncopiled) without any errors
> concerning tips.cpp (no tips.cpp is ever compiled).  The package then installs
> cleanly with dpkg -i, and runs fine (I only opened an existing project,
> compiled and viewed the result).  Tips in English work too.  Are there any
> other build commands or targets that are expected by launchpad ppa?  Is there
> an easy way to reduce my local build environment to just what is available on
> launchpad (using a chroot jail).  I'm not an expert on debian packaging, as you
> can see...
> 
> This problem with tips.cpp was actually encountered before:
> In https://bugs.launchpad.net/ubuntu/+source/kile/+bug/110779 a patch
> 07_remove_tips_cpp.diff was added, but this was included upstream in the 2.0
> series (see Changelog of the ubuntu kile package).  The only thing the patch
> does is remove the tips.cpp file right after it is created by preparetips. 
> This still happens in the Makefiles that are included in your uploaded source
> archive, so no tips.cpp should ever exist long enough to be compiled.

I don't understand it either.  It worked for me as well, but look at what happens when the PPA builds it: http://launchpadlibrarian.net/20627427/buildlog_ubuntu-intrepid-i386.kile-kde3_1%3A2.0.2-0ubuntu1_FAILEDTOBUILD.txt.gz

It seems that the problem is in the following blurb from your FTBFS log (I didn't get those errors, and dismissed them when I looked at the FTBFS log earlier).

---
XGETTEXT=/usr/bin/kde-xgettext EXTRACTATTR=/usr/bin/extractattr sh ./admin/cvs.sh extract-messages
./src/kile
./admin/cvs.sh: 651: kde-config: not found
./admin/cvs.sh: 651: kde-config: not found
error while opening "/include/kde.pot" for reading: No such file or directory
make exit code: 2
for file in po/*pot; do \
		sed "s/charset=CHARSET/charset=UTF-8/" -i $file; \
	done
sed: can't read po/*pot: No such file or directory
make: [common-install-prehook-impl] Error 2 (ignored)
---

The script admin/cvs.sh expects kde-config in the $PATH to determine the KDE prefix, which is used to find the location of kde.pot (for the environment variable $kdepotpath).  But kde-config is installed under the /usr/kde3 prefix... so it's not found.  Unsetting the kde3 prefix from $PATH reproduces exactly the launchpad error.

admin/cvs.sh goes on to call 'make messages' in src/kile which generates the tips.cpp file, and then tries to run $XGETTEXT with argument $kdepotpath.  Normally as next command tips.cpp would be deleted again, but make fails because it can't find any kde.pot and it does not get to deleting tips.cpp.  Thus tips.cpp fails compilation.


Now, as a solution I introduced an environment variable kdeconfig in admin/cvs.sh.  If kde-config is not found in the path, it just hardwires it to the /usr/kde3/bin location.  It will then find kde.pot, xgettext will succeed and tips.cpp will be deleted.

See the attached patch for admin/cvs.sh.  When applied (and without kde-config in the $PATH) it now succeeds.  I didn't test this on launchpad, but I expect it should work (but that's what they all say ;-) ).

Created attachment 1 [details]
07_kde-config.diff

Patch improves search for kde-config in admin/cvs.sh.

Thank you for the patch--kile is now built properly by the PPA.