10 More Discussions You Might Find Interesting
1. Proxy Server
pardon the ed URL refs but I'm not allowed to post URLs yet.
and the misspelling in the original thread title, which I can't edit even in 'advanced'
greetings all, posting this here rather than in Web Development since I suspect this is rather AIX-specific and will need some arcane knowledge,... (2 Replies)
Discussion started by: maraixadm
2 Replies
2. AIX
dears
i am trying to install the autoconf-2.63-1.aix6.1.noarch.rpm but its shows the below error message .
P700_dev/svn/dependencies>rpm -i autoconf-2.63-1.aix6.1.noarch.rpm
error: failed dependencies:
m4 is needed by autoconf-2.63-1
P700_dev/svn/dependencies> (6 Replies)
Discussion started by: thecobra151
6 Replies
3. Red Hat
Would you please give us the definition and usage of RPMs in linux?
thanks to reply.... (1 Reply)
Discussion started by: jaydul
1 Replies
4. Red Hat
Hello,
I am just a newbie and have very recently started building rpms, i build a very simple rpm that packaged 3 files and everything worked very smoothly. However to be very honest i am not very much clear with what is the difference between %install and %files section.
I mean like we... (0 Replies)
Discussion started by: Rohit Bhanot
0 Replies
5. Shell Programming and Scripting
How to make RPM not write to RPM database if RPM fails to deploy?
IE I create an rpm spec file that contains the following
if
then
exit 1
fi
My rpm will fail at deployment, but if I do rpm -qa , I can see the rpm in the rpm db (3 Replies)
Discussion started by: 3junior
3 Replies
6. Red Hat
Can any one help me to know the command option that will update all rpms
Thanks in advance.. (2 Replies)
Discussion started by: RajendraKumar
2 Replies
7. SuSE
Hi,
I have got few RPM's from rpmfind.net ( mainly gcc ).
But it seems to be src files instead of the image.
so I think we have to build the src files according to target machine using rpmbuild.
Can any one help me with
1) Various options of rpm build that have to be taken care
2)... (3 Replies)
Discussion started by: Sivaswami
3 Replies
8. Linux
Hi,
I need to install an rpm file,but I only have '.src.rpm' version of it. I want to convert it to a binary rpm.
so I tried this
rpm --rebuild somethin.src.rpm
But I am gettin '--rebuild:Invalid option' as output
Is there another way to rebuild source rpm.?
Thanks in... (2 Replies)
Discussion started by: eamani_sun
2 Replies
9. Linux
Hey,
I've a problem installing a package. rpm -ivh brings the errors:
libjvm.so is needed by
libverify.so is needed by
But I have installed the Java SDK like requested and the files are on the disk. But I have no idea how to find out, why rpm cann't find them.
I have also... (2 Replies)
Discussion started by: mod
2 Replies
10. UNIX for Dummies Questions & Answers
Ok, this is probably a real simple question....I have RH 7.1 and i wanted to know do I have to install the RPM packages for software or can i use the binaries and do make ...make install.
?? (6 Replies)
Discussion started by: macdonto
6 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)