Mer/Build/Common Problems - Revision history

imported_>amigadave: {{Mer}}

2010-09-22T09:33:32Z

← Older revision		Revision as of 09:33, 22 September 2010
Line 1:		Line 1:
			{{Mer}}

	=Common Problems encountered building for Mer on OBS=		=Common Problems encountered building for Mer on OBS=

Line 59:		Line 61:
	CFLAGS="-Wall -g -O2" ./configure --prefix=/usr --disable-static		CFLAGS="-Wall -g -O2" ./configure --prefix=/usr --disable-static
	configure: error: cannot find install-sh or install.sh in . ./.. ./../..		configure: error: cannot find install-sh or install.sh in . ./.. ./../..


	~~[[Category:Mer]]~~

imported_>amigadave: drop dead links

2010-08-30T15:16:58Z

drop dead links

← Older revision		Revision as of 15:16, 30 August 2010
Line 12:		Line 12:

	* expansion error		* expansion error
	The build can not begin, because required packages are either missing or not explicitly defined. ~~[[Mer/Build/Common Problems/Expansion Error Diagnosis\|Expansion Error Diagnosis]]~~		The build can not begin, because required packages are either missing or not explicitly defined.

	* blocked		* blocked
Line 36:		Line 36:

	* broken		* broken
	The sources either contain no build description (eg specfile) or a source link does not work. ~~[[Mer/Build/Common Problems/Broken Diagnosis\|Broken Diagnosis]]~~		The sources either contain no build description (eg specfile) or a source link does not work.

	* unknown		* unknown

imported_>guaka: Category:Mer

2009-10-26T18:01:50Z

Category:Mer

← Older revision		Revision as of 18:01, 26 October 2009
Line 59:		Line 59:
	CFLAGS="-Wall -g -O2" ./configure --prefix=/usr --disable-static		CFLAGS="-Wall -g -O2" ./configure --prefix=/usr --disable-static
	configure: error: cannot find install-sh or install.sh in . ./.. ./../..		configure: error: cannot find install-sh or install.sh in . ./.. ./../..


			[[Category:Mer]]

imported_>lbt: removed extra Documentation/ in paths

2009-05-04T09:43:26Z

removed extra Documentation/ in paths

← Older revision		Revision as of 09:43, 4 May 2009
Line 8:		Line 8:

	* failed		* failed
	The package does not build successfully. No packages have been created. Packages that depend on this package will be built using any previously created packages, if they exist. [[Mer~~/Documentation~~/Build/Common Problems/Failed Diagnosis\|Failed Diagnosis]]		The package does not build successfully. No packages have been created. Packages that depend on this package will be built using any previously created packages, if they exist. [[Mer/Build/Common Problems/Failed Diagnosis\|Failed Diagnosis]]


	* expansion error		* expansion error
	The build can not begin, because required packages are either missing or not explicitly defined. [[Mer~~/Documentation~~/Build/Common Problems/Expansion Error Diagnosis\|Expansion Error Diagnosis]]		The build can not begin, because required packages are either missing or not explicitly defined. [[Mer/Build/Common Problems/Expansion Error Diagnosis\|Expansion Error Diagnosis]]

	* blocked		* blocked
Line 36:		Line 36:

	* broken		* broken
	The sources either contain no build description (eg specfile) or a source link does not work. [[Mer~~/Documentation~~/Build/Common Problems/Broken Diagnosis\|Broken Diagnosis]]		The sources either contain no build description (eg specfile) or a source link does not work. [[Mer/Build/Common Problems/Broken Diagnosis\|Broken Diagnosis]]

	* unknown		* unknown

imported_>lbt: Mer/Documentation/Build/Common Problems moved to Mer/Build/Common Problems: don't need spurious Documentation

2009-05-04T09:41:52Z

Mer/Documentation/Build/Common Problems moved to Mer/Build/Common Problems: don't need spurious Documentation

← Older revision	Revision as of 09:41, 4 May 2009
(No difference)

imported_>lbt: Mer/Documentation/Build/CommonProblems moved to Mer/Documentation/Build/Common Problems: I'm scared of GA

2009-05-03T17:11:29Z

Mer/Documentation/Build/CommonProblems moved to Mer/Documentation/Build/Common Problems: I'm scared of GA

← Older revision	Revision as of 17:11, 3 May 2009
(No difference)

imported_>lbt: Diagnosing build problems

2009-05-03T17:11:00Z

Diagnosing build problems

← Older revision		Revision as of 17:11, 3 May 2009
Line 8:		Line 8:

	* failed		* failed
	The package does not build successfully. No packages have been created. Packages that depend on this package will be built using any previously created packages, if they exist.		The package does not build successfully. No packages have been created. Packages that depend on this package will be built using any previously created packages, if they exist. [[Mer/Documentation/Build/Common Problems/Failed Diagnosis\|Failed Diagnosis]]


	* expansion error		* expansion error
	The build can not begin, because required packages are either missing or not explicitly defined.		The build can not begin, because required packages are either missing or not explicitly defined. [[Mer/Documentation/Build/Common Problems/Expansion Error Diagnosis\|Expansion Error Diagnosis]]

	* blocked		* blocked
	This package waits for other packages to be built. These can be in the same or other projects.		This package waits for other packages to be built. These can be in the same or other projects. Typically you just need to wait.

	* scheduled		* scheduled
	A package has been marked for building, but the build has not started yet.		A package has been marked for building, but the build has not started yet. Again, just wait.

	* building		* building
	The package is currently being built.		The package is currently being built. Smile and wait.

	* dispatching		* dispatching
Line 35:		Line 36:

	* broken		* broken
	The sources either contain no build description (eg specfile) or a source link does not work.		The sources either contain no build description (eg specfile) or a source link does not work. [[Mer/Documentation/Build/Common Problems/Broken Diagnosis\|Broken Diagnosis]]

	* unknown		* unknown

imported_>lbt: draft

2009-05-03T17:05:22Z

draft

New page

=Common Problems encountered building for Mer on OBS=

==Diagnosing a problem==
First of all look at the status information

* succeeded
Package has built successfully and can be used to build further packages.

* failed
The package does not build successfully. No packages have been created. Packages that depend on this package will be built using any previously created packages, if they exist.

* expansion error
The build can not begin, because required packages are either missing or not explicitly defined.

* blocked
This package waits for other packages to be built. These can be in the same or other projects.

* scheduled
A package has been marked for building, but the build has not started yet.

* building
The package is currently being built.

* dispatching
A package is being copied to a build host. This is an intermediate state before building.

* finished
The package has been built, but has not yet been picked up by the server. This is an intermediate state prior to 'succeeded' or 'failed'.

* disabled
The package has been disabled from building in project or package metadata.

* excluded
The package build has been disabled in package build description (for example in the .spec file) or does not provide a matching build description for the target.

* broken
The sources either contain no build description (eg specfile) or a source link does not work.

* unknown
The scheduler has not yet evaluated this package. Should be a short intermediate state for new packages.

==Non-Problems==
Some things are known issues that (AFAWK) don't affect the build:
* qemu broken pipes

==Specifics==

dh_clean
dpkg-source -b BUILD
dpkg-source: warning: source directory 'BUILD' is not <sourcepackage>-<upstreamversion> 'bomberman-1.0 '
dpkg-source: info: using source format `1.0'
dpkg-source: info: building bomberman in bomberman_1.0.tar.gz
dpkg-source: info: building bomberman in bomberman_1.0.dsc
debian/rules build
dh_testdir
# Add here commands to configure the package.
CFLAGS="-Wall -g -O2" ./configure --prefix=/usr --disable-static
configure: error: cannot find install-sh or install.sh in . ./.. ./../..