[FTBFS] cone 0.74-1 (Hardy) fails to build on Gutsy box

Bug #187019 reported by Pawel Tecza

This bug report was converted into a question: question #24120: [FTBFS] cone 0.74-1 (Hardy) fails to build on Gutsy box.

2
Affects Status Importance Assigned to Milestone
cone (Ubuntu)
Invalid
Undecided
Daniel Schwitzgebel

Bug Description

Binary package hint: cone

I'm trying to build Hardy source package of cone 0.74-1 on my Gutsy box,
but no success.

At first, I was missing g++ package, so my `dpkg-buildpackage -us -uc -rfakeroot`
command failed like below:

[...]
checking for C++ compiler default output file name...
configure: error: C++ compiler cannot create executables
See `config.log' for more details.
configure: error: ./configure failed for curses
make: *** [config.status] Error 1

BTW, could you please add g++ package to Build-Depends: field of debian/control file?
I think it can be helpful for another people who want to build and test the latest
version of Cone on Ubuntu box.

Now I have package g++-4.1 installed, but I still can't build Cone. Below is a piece
of output of dpkg-buildpackage tool:

dpkg-buildpackage: source package is cone
dpkg-buildpackage: source version is 0.74-1
dpkg-buildpackage: source changed by Varun Hiremath <email address hidden>
dpkg-buildpackage: host architecture i386
dpkg-buildpackage: source version without epoch 0.74-1
 fakeroot debian/rules clean
test -x debian/rules
test "`id -u`" = 0
for i in ./unicode/config.guess ./config.guess ./unicode/config.sub ./config.sub ./cone/config.rpath ./config.rpath ; do \
                if test -e $i.cdbs-orig ; then \
                        mv $i.cdbs-orig $i ; \
                fi ; \
        done
/usr/bin/make -C . -k distclean
make[1]: Entering directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74'
Making distclean in cone
make[2]: Entering directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74/cone'
make[2]: *** No rule to make target `distclean'.
make[2]: Leaving directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74/cone'
[...]
touch debian/stamp-autotools-files
/usr/bin/make -C .
make[1]: Entering directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74'
echo "0.74" | cmp -s - coneversion && exit 0; echo "0.74" >coneversion
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
/usr/bin/make all-recursive
make[2]: Entering directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74'
Making all in unicode
make[3]: Entering directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74/unicode'
make[3]: *** No rule to make target `all'. Stop.
make[3]: Leaving directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74/unicode'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/ptecza/Ubuntu/Packages/cone/cone-0.74'
make: *** [debian/stamp-makefile-build] Error 2

If you want I can send you the full log of dpkg-buildpackage utility.

Now I don't have idea how to resolve the problem. Maybe something is missing
in debian/rules file? It's the shortest rules file I have ever seen :)

I've also tried to build Debian source package of cone 0.74-2. It has short rules file
too, but it builds successfully.

Changed in cone:
assignee: nobody → schwitzd
Changed in cone:
status: New → Invalid
Revision history for this message
Pawel Tecza (ptecza) wrote : Re: [Bug 187019] Re: [FTBFS] cone 0.74-1 (Hardy) fails to build on Gutsy box

On Cz, 2008-02-07 at 19:44 +0000, Daniel Schwitzgebel wrote:
> ** Changed in: cone (Ubuntu)
> Status: New => Invalid
>
> ** bug changed to question:
> https://answers.edge.launchpad.net/ubuntu/+source/cone/+question/24120

Question? What is the question? Sorry, but I don't understand your change.

For me it's just bug report, because a Debian source package for the same version
of cone builds successfully on my Gutsy box, but the Ubuntu source package fails.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.