rpmbuild - Build RPM Package(s)


   rpmbuild {-ba|-bb|-bp|-bc|-bi|-bl|-bs} [rpmbuild-options] SPECFILE ...

   rpmbuild {-ta|-tb|-tp|-tc|-ti|-tl|-ts} [rpmbuild-options] TARBALL ...

   rpmbuild {--rebuild|--recompile} SOURCEPKG ...

   rpmbuild --showrc

    [--buildroot DIRECTORY] [--clean] [--nobuild]
    [--rmsource] [--rmspec] [--short-circuit]
    [--noclean] [--nocheck]
    [--target PLATFORM]


   rpmbuild  is used to build both binary and source software packages.  A
   package consists of an archive of files and meta-data used  to  install
   and  erase  the  archive  files. The meta-data includes helper scripts,
   file  attributes,  and  descriptive  information  about  the   package.
   Packages  come  in  two varieties: binary packages, used to encapsulate
   software to be installed, and source packages,  containing  the  source
   code and recipe necessary to produce binary packages.

   One of the following basic modes must be selected: Build Package, Build
   Package from Tarball, Recompile Package, Show Configuration.

   These options can be used in all the different modes.

   -?, --help
          Print a longer usage message then normal.

          Print a single line containing the version number of  rpm  being

          Print  as little as possible - normally only error messages will
          be displayed.

   -v     Print verbose information - normally routine  progress  messages
          will be displayed.

   -vv    Print lots of ugly debugging information.

   --rcfile FILELIST
          Each  of  the  files  in  the  colon  separated FILELIST is read
          sequentially by rpm for  configuration  information.   Only  the
          first  file  in the list must exist, and tildes will be expanded
          to   the   value   of   $HOME.    The   default   FILELIST    is

   --pipe CMD
          Pipes the output of rpm to the command CMD.

   --dbpath DIRECTORY
          Use the database in  DIRECTORY  rather  than  the  default  path

   --root DIRECTORY
          Use the file system tree rooted at DIRECTORY for all operations.
          Note that this means the database within DIRECTORY will be  used
          for  dependency  checks  and  any  scriptlet(s)  (e.g.  %post if
          installing, or %prep if building, a package) will be run after a
          chroot(2) to DIRECTORY.

   -D, --define='MACRO EXPR'
          Defines MACRO with value EXPR.

   The general form of an rpm build command is

   rpmbuild -bSTAGE|-tSTAGE [      rpmbuild-options
    ] FILE ...

   The  argument  used  is  -b  if  a spec file is being used to build the
   package  and  -t  if  rpmbuild  should  look  inside  of  a   (possibly
   compressed)  tar  file  for  the  spec  file  to  use.  After the first
   argument, the next character (STAGE) specifies the stages  of  building
   and packaging to be done and is one of:

   -ba    Build binary and source packages (after doing the %prep, %build,
          and %install stages).

   -bb    Build a binary package  (after  doing  the  %prep,  %build,  and
          %install stages).

   -bp    Executes  the  "%prep"  stage  from the spec file. Normally this
          involves unpacking the sources and applying any patches.

   -bc    Do the "%build" stage from the spec file (after doing the  %prep
          stage).  This generally involves the equivalent of a "make".

   -bi    Do  the  "%install"  stage  from  the spec file (after doing the
          %prep  and  %build  stages).   This   generally   involves   the
          equivalent of a "make install".

   -bl    Do  a  "list check".  The "%files" section from the spec file is
          macro expanded, and checks are made to  verify  that  each  file

   -bs    Build just the source package.

   The following options may also be used:

   --buildroot DIRECTORY
          When  building  a  package,  override  the  BuildRoot  tag  with
          directory DIRECTORY.

          Remove the build tree after the packages are made.

          Do not execute any build stages. Useful  for  testing  out  spec

          Do not execute %clean build stage even if present in spec.

          Do not execute %check build stage even if present in spec.

          Do not verify build dependencies.

          Remove the sources after the build (may also be used standalone,
          e.g. "rpmbuild --rmsource foo.spec").

          Remove  the  spec  file  after  the  build  (may  also  be  used
          standalone, eg. "rpmbuild --rmspec foo.spec").

          Skip  straight to specified stage (i.e., skip all stages leading
          up to the specified stage).  Only valid with -bc, -bi, and  -bb.
          Useful  for local testing only.  Packages built this way will be
          marked  with  an  unsatisfiable  dependency  to  prevent   their
          accidental use.

   --target PLATFORM
          When  building the package, interpret PLATFORM as arch-vendor-os
          and set  the  macros  %_target,  %_target_cpu,  and  %_target_os

   There are two other ways to invoke building with rpm:

   rpmbuild --rebuild|--recompile SOURCEPKG ...

   When  invoked this way, rpmbuild installs the named source package, and
   does a prep, compile and install.  In addition, --rebuild builds a  new
   binary  package.  When  the build has completed, the build directory is
   removed (as in --clean) and the the  sources  and  spec  file  for  the
   package are removed.

   The command

   rpmbuild --showrc

   shows the values rpmbuild will use for all of the options are currently
   set in rpmrc and macros configuration file(s).


   rpmrc Configuration

   Macro Configuration




   rpmbuild --help - as rpm supports  customizing  the  options  via  popt
   aliases  it's  impossible  to  guarantee  that  what's described in the
   manual matches what's available.

   http://www.rpm.org/ <URL:http://www.rpm.org/>


   Marc Ewing <marc@redhat.com>
   Jeff Johnson <jbj@redhat.com>
   Erik Troan <ewt@redhat.com>


Personal Opportunity - Free software gives you access to billions of dollars of software at no cost. Use this software for your business, personal use or to develop a profitable skill. Access to source code provides access to a level of capabilities/information that companies protect though copyrights. Open source is a core component of the Internet and it is available to you. Leverage the billions of dollars in resources and capabilities to build a career, establish a business or change the world. The potential is endless for those who understand the opportunity.

Business Opportunity - Goldman Sachs, IBM and countless large corporations are leveraging open source to reduce costs, develop products and increase their bottom lines. Learn what these companies know about open source and how open source can give you the advantage.

Free Software

Free Software provides computer programs and capabilities at no cost but more importantly, it provides the freedom to run, edit, contribute to, and share the software. The importance of free software is a matter of access, not price. Software at no cost is a benefit but ownership rights to the software and source code is far more significant.

Free Office Software - The Libre Office suite provides top desktop productivity tools for free. This includes, a word processor, spreadsheet, presentation engine, drawing and flowcharting, database and math applications. Libre Office is available for Linux or Windows.

Free Books

The Free Books Library is a collection of thousands of the most popular public domain books in an online readable format. The collection includes great classical literature and more recent works where the U.S. copyright has expired. These books are yours to read and use without restrictions.

Source Code - Want to change a program or know how it works? Open Source provides the source code for its programs so that anyone can use, modify or learn how to write those programs themselves. Visit the GNU source code repositories to download the source.


Study at Harvard, Stanford or MIT - Open edX provides free online courses from Harvard, MIT, Columbia, UC Berkeley and other top Universities. Hundreds of courses for almost all major subjects and course levels. Open edx also offers some paid courses and selected certifications.

Linux Manual Pages - A man or manual page is a form of software documentation found on Linux/Unix operating systems. Topics covered include computer programs (including library and system calls), formal standards and conventions, and even abstract concepts.