Launchpad itself

amd64 building fails for no apparent reason

Asked by Morten Kjeldgaard

I am not sure if this is a bug in launchpad, or with my package, but it seems very odd. I uploaded the source package to the queue. The package built fine on i386, but it failed on amd64. However, I cannot understand what happens. This is the log for the i386 build, that worked:

make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/build/buildd/clipper-2.0.3'
make[2]: Leaving directory `/build/buildd/clipper-2.0.3'
make[1]: Leaving directory `/build/buildd/clipper-2.0.3'
mkdir -p doc/html
doxygen Doxyfile.ccp4
Warning: Tag `USE_WINDOWS_ENCODING' at line 64 of file Doxyfile.ccp4 has become obsolete.
To avoid this warning please update your configuration file using "doxygen -u"
.
[Here the doxygen markup is processed, and I have removed several hundred lines of output]
.
.
Error: Tag file `doxy.core.tag' does not exist or is not a file. Skipping it...
/build/buildd/clipper-2.0.3/clipper/phs/phs_io.h:1 Warning: the name `lib/phs_io.h' supplied as the second argument in the \file statement is not an input file

[Doxygen processing is finished.]

dh_testdir
dh_testroot
... and the rest of the building proceeds and builds the packages. Now the amd64 log:

make[3]: Nothing to be done for `install-data-am'.
make[3]: Leaving directory `/build/buildd/clipper-2.0.3'
make[2]: Leaving directory `/build/buildd/clipper-2.0.3'
make[1]: Leaving directory `/build/buildd/clipper-2.0.3'
dh_testdir
dh_testroot
#dh_installchangelogs ChangeLog
dh_installdocs
cp: cannot stat `doc/html': No such file or directory
dh_installdocs: command returned error code 256
make: *** [binary-arch] Error 1
******************************************************************************
Build finished at 20071008-1432

The doxygen building is skipped, thus the doc/html directory is not generated and the build fails. It's as if the binary-indep target is never built in rules, but the binary target depends on it.

Is something special going on in the amd64 builder?

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Christian Reis (kiko) said : 		#1

On Tue, Oct 09, 2007 at 02:57:17PM -0000, Morten Kjeldgaard wrote:
> make[3]: Nothing to be done for `install-data-am'.
> make[3]: Leaving directory `/build/buildd/clipper-2.0.3'
> make[2]: Leaving directory `/build/buildd/clipper-2.0.3'
> make[1]: Leaving directory `/build/buildd/clipper-2.0.3'
> dh_testdir
> dh_testroot
> #dh_installchangelogs ChangeLog
> dh_installdocs
> cp: cannot stat `doc/html': No such file or directory
> dh_installdocs: command returned error code 256
> make: *** [binary-arch] Error 1

This is almost surely a bug in your package. If the doxygen building is
skipped, then why is dh_installdocs depending on the existence of the
html subdirectory?

> The doxygen building is skipped, thus the doc/html directory is not generated and the build fails. It's as if the binary-indep target is never built in rules, but the binary target depends on it.
>
> Is something special going on in the amd64 builder?

Not on this level, not that I can imagine. Have you tried asking other
packagers for help?

Revision history for this message
Morten Kjeldgaard (mok0) said : 		#2

> This is almost surely a bug in your package. If the doxygen building is
> skipped, then why is dh_installdocs depending on the existence of the
> html subdirectory?

Doxygen building isn't supposed to be skipped. It's not skipped in the i386 build, and debian/rules is the same (of course).

Revision history for this message
Launchpad Janitor (janitor) said : 		#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Celso Providelo (cprov) said : 		#4

dh_installdocs is not skipped in i386, because that's the architecture where arch-indep binaries are built.

It's indeed a packaging issue and you will probably spot it locally if you build only arch-specific binaries (`debuild -B`).

Can you help with this problem?

Provide an answer of your own, or ask Morten Kjeldgaard for more information if necessary.

To post a message you must log in.