Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tree: bbec7e32b4
Fetching contributors…

Cannot retrieve contributors at this time

170 lines (165 sloc) 4.968 kb
.de TQ \"follow a TP item with several TQ items to define several
. \"entities with one shared description.
.TP \\$1
.TH build 1 "(c) 1997-2008 SuSE Linux AG Nuernberg, Germany"
build \- build SuSE Linux RPMs in a chroot environment
.B build
.RB [ --clean | --no-init]
.RB [ --rpms
.IR path1 : path2 : ... ]
.RB [ --arch
.IR arch1 : arch2 : ... ]
.RB [ --root
.IR buildroot ]
.RB [ specfile | srcrpm ]
.B build
.B --help
.B build
.B --verify
\fBbuild\fR is a tool to build SuSE Linux RPMs in a safe and clean way.
.B build
will install a minimal SuSE Linux as build system into some directory
and will chroot to this system to compile the package.
This way you don't risk to corrupt your working system (due to a broken spec
file for example), even if the package does not use BuildRoot.
.B build
searches the spec file for a
.I BuildRequires:
line; if such a line is found, all the specified rpms are installed.
Otherwise a selection of default packages are used. Note that
.B build
doesn't automatically resolve missing dependencies, so the specified
rpms have to be sufficient for the build.
If a spec file is specified on the command line,
.B build
will use this file and all other files in the directory for building
the package. If a srcrpm is specified,
.B build
automatically unpacks it for the build.
If neither is given,
.B build
will use all the specfiles in the current directory.
.B --clean
remove the build system and reinitialize it from scratch.
.B --no-init
skip the build system initialization and start with build immediately.
.B --list-state
list rpms that would be used to create a fresh build root.
Does not create the build root or perform a build.
.BI "\-\-rpms " path1 : path2 : path3\fR...\fP
Where build can find the SuSE Linux RPMs needed to create the
build system. This option overrides the BUILD_RPMS environment
.BI "\-\-arch " arch1 : arch2 : arch3\fR...\fP
What architectures to select from the RPMs.
.B build
automatically sets this to a sensible value for your host if you
don't specify this option.
.BI "\-\-repo " url_or_dir
Also use the specified repository to create the build system.
The repositories may be either of type rpmmd, yast2 (susetags),
or a simple directory. Multiple --repo options may be given.
As a special form, 'zypp://reponame' can be used to specify
a system repository. 'zypp://' selects all enabled system
repositories. This is also the default if BUILD_RPMS is not
set and no --rpms or --repo option is used.
.BI "\-\-root " buildroot
Specifies where the build system is set up. Overrides the
BUILD_ROOT enviroment variable.
.B --useusedforbuild
Tell build not to do dependency expansion, but to extract the
list of packages to install from "# usedforbuild" lines or, if none
are found, from all "BuildRequires" lines. This option is useful
if you want to re-build a package from a srcrpm with exactly the
same packages used for the srcrpm build.
.B --norootforbuild
.B --help
Print a short help text.
.B --verify
verify the files in an existing build system.
.BI "\-\--dist " distribution
Set the distribution. If this option is not given, build tries to
calculate the distribution by looking at the rpm package used in the
The specified distribution can either be a string
like "11.2" or "sles9", or the pathname of the build configuration to
.B build
command interprets some special control comments in the specfile:
.B # norootforbuild
.B # needsrootforbuild
.B build
uses either user
.I root
or user
.I abuild
in the build system to do the build. For non-SUSE distros as well as
since SUSE 10.2, the default build user is
.I abuild.
For 10.2 and before, the default build user is
.I root.
These two flags in the spec file allow to deviate from the defaults
and force-set the build user to
.I abuild
.I root
.RI "(for " "#\ norootforbuild" " and " "#\ needsrootforbuild" " respectively."
.B # needsbinariesforbuild
provide the binary rpms that have been used to set up the build root
.I /.build.binaries
within the build root.
The directory where build should install the chrooted build system.
"/var/tmp/build-root" is used by default.
Where build can find the SuSE Linux RPMs. build needs them to create the
build system.
The rpm build stage (-ba, -bb, ...). This is just passed through to
rpm, check the rpm manpage for a complete list and descriptions.
"-ba" is the default.
You can use this to add more options to RPM.
.BR rpm (8),
.BR "Maximum RPM":
.BR "cross distribution packaging":
.BR "openSUSE packaging standards and guidelines":
Jump to Line
Something went wrong with that request. Please try again.