10 More Discussions You Might Find Interesting
1. Red Hat
I wish to install inotify-tools-3.20.1-2.4.x86_64.rpm on Linux and fire inotifywait command.
Initially i was looking for "inotify-tools-3.xx.tar.gz" as instructed here http://jensd.be/248/linux/use-inotify-tools-on-centos-7-or-rhel-7-to-watch-files-and-directories-for-events
I have... (9 Replies)
Discussion started by: mohtashims
9 Replies
2. Red Hat
Hi
In opensuse we have this nice version control variable I use much when designing rpm spec files:
rpm --showrc | grep suse_version
%if 0%{?suse_version} > 0 && 0%{?suse_version} < 1700
-14: suse_version 1140But I do not find anything close to this in rhel/centos
The only way... (0 Replies)
Discussion started by: mortenb
0 Replies
3. Red Hat
Hi,
I would like to know is it possible to install rpm along its depedable rpm from mounted .iso image on Redhat Linux
while installing rpm it is showing so many depandancy, so I would like to know with single command wheather it will take all depedable rpm from mounted iso image. (1 Reply)
Discussion started by: manoj.solaris
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
Using Redhat version 6.0, I need nmap so I have downloaded. But it requires many other dependencies, when I try to install it. See below err.msg. Is there any other way to get this installed, or I need to download each of the dependencies.
rpm -Uhv nmap-5.51-2-mdv2011.0.x86_64.rpm... (3 Replies)
Discussion started by: samnyc
3 Replies
5. Red Hat
Hi,
I have install tcl and then expect but I am getting below ouput while trying which expect
which expect
/usr/bin/which: no expect in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin)
I have copied both in... (6 Replies)
Discussion started by: manish_1678
6 Replies
6. UNIX for Dummies Questions & Answers
Hello,
Please give me stepwise instruction on installing Apache and PHP on linux.
Thanks
sheen (6 Replies)
Discussion started by: sheen
6 Replies
7. Shell Programming and Scripting
Hi everyone
I have just joined a software developing team. I am new to unix. Basically
we are developing a product, the problem is when the end user will install this package we would like to install the datbase associated with our product using RPM.
Can it be done?
how secure it is?
and... (0 Replies)
Discussion started by: atul.saxena
0 Replies
8. UNIX for Dummies Questions & Answers
Ok when i try to run the install the is what i get
How can i fix this can anyone help (8 Replies)
Discussion started by: Blackrose
8 Replies
9. UNIX for Dummies Questions & Answers
I am trying to install this driver: http://www.asus.com/support/download/selectftp.aspx?l1_id=1&l2_id=15&l3_id=15&m_id=1&f_name=5702_558.zip~zaqwedc hoping it will correct my problem with my ethernet card. I am following the instructions in the text file that came with download...
it says to... (7 Replies)
Discussion started by: Minnesota Red
7 Replies
10. UNIX for Dummies Questions & Answers
Hey everybody. Its been awhile since I last posted but in short I am now in posession of RedHat Linux 7.0 which I got from a book called the RedHat 7 Bible. As this is not an official distribution I cannot get product support from RedHat so I decided to try here.
I have three computers. I... (2 Replies)
Discussion started by: TheGoof
2 Replies
build(1) General Commands Manual build(1)
NAME
build - build SuSE Linux RPMs in a chroot environment
SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm]
build --help
build --verify
DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc-
tory 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.
build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec-
tion of default packages are used. Note that 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, build will use this file and all other files in the directory for building the package. If
a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current
directory.
OPTIONS
--clean
remove the build system and reinitialize it from scratch.
--no-init
skip the build system initialization and start with build immediately.
--list-state
list rpms that would be used to create a fresh build root. Does not create the build root or perform a build.
--rpms path1:path2:path3...
Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari-
able.
--arch arch1:arch2:arch3...
What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify
this option.
--root buildroot
Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable.
--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.
--norootforbuild
--help Print a short help text.
--verify
verify the files in an existing build system.
.spec FILE OPTIONS
The build command interprets some special control comments in the specfile:
# norootforbuild
# needsrootforbuild
build uses either user root or user 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 abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to
deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec-
tively.
# needsbinariesforbuild
provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root.
ENVIRONMENT
BUILD_ROOT
The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default.
BUILD_RPMS
Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value
which will do the trick if you have the SuSE Linux DVD mounted.
BUILD_RPM_BUILD_STAGE
The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip-
tions. "-ba" is the default. You can use this to add more options to RPM.
SEE ALSO
rpm(1),
Maximum RPM:
http://www.rpm.org/max-rpm/
cross distribution packaging:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to
SUSE packaging standards and guidelines:
http://en.opensuse.org/Packaging
(c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)
