10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
#cat hwlock-full.dep
libx11-6 >= 1.4.4
libz1 >= 1.2.7
libtinfo5 >= 5.9
libxcb1 >= 1.8.1
numactl >= 2.0.8+rc4
libpixman-1-0 >= 0.29.2
libxml2 >= 2.7.8
libxext6 >= 1.3.1
libxrender1 >= 0.9.7
libfreetype6 >= 2.4.9
libxcb-render0 >= 1.8.1
libcairo2 >= 1.12.14
libc6 >= 2.15
libxcb-shm0... (7 Replies)
Discussion started by: yanglei_fage
7 Replies
2. Shell Programming and Scripting
Gurus,
I came across a typical requirement where the input is like-
TRANS FIRM
DEPT CUST
TRANS CUST
TRANS DEPT
FIRM CUST
& the expected Output is-
CUST
DEPT
FIRM
TRANS
This is basically a dependency list for processing the tables where
FIRM is feeding data to TRANS... (3 Replies)
Discussion started by: kapeeljoshi
3 Replies
3. Emergency UNIX and Linux Support
hello,
can anyone help in changing the executable dependency on a certain shared library. eg, .. say i am having an executable by name utest. when i run UNIX ldd command on it then it shows the libraries on which it depends as follows:
ldd release/utest
release/utest needs:
... (4 Replies)
Discussion started by: skyineyes
4 Replies
4. HP-UX
I'm building on a HP-UX ia64 system. During building, I'm getting an error
ld: Can't find dependent library "libnnz10.so"
Nowhere in my makefile do I link with this library. This library is there in the directory /databases/oracle10.2.0_64BIT/lib. I'm having two source files ora8ibulk.cpp... (1 Reply)
Discussion started by: old_as_a_fossil
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I had a make file, something like that,
all:
cd dir1; make
cd dir2; make
the problem is the makefile under dir2 need some objs from dir1, so I need to set some dependency let dir2 run only after the dir1 run is done.
how to set the dependency?
Thanks.
peter (2 Replies)
Discussion started by: laopi
2 Replies
6. Programming
Hello,
I'm creating an add-on for a large piece of software written in Fortran. In my directory I reference subroutines in other directories, which in turn reference more subroutines.
I'm running into trouble because on occasion the developers of the main software change some sub calls.
... (2 Replies)
Discussion started by: kudude
2 Replies
7. Infrastructure Monitoring
Hi,
I want to install net-snmp-devel package but i have following dependecy problem.
It's very odd, i don't get it. One of packages is depended on the other one, the other one is depended on the previous one as well. :S :S
Could you help me please?
Here are the steps:
# ls -l
total... (4 Replies)
Discussion started by: oduth
4 Replies
8. Solaris
Hi all
am new to solaris ............
i installed amanda client pkg that time am getting lots of dependency problem..........
is there any Yum server like things in solaris
Regards '
prAn (8 Replies)
Discussion started by: pran
8 Replies
9. Linux
Hi,
This has been extremely frustrating, and I need help figuring this one out!
I am running Fedora 7 on computer A, and am VNCing into it from my Mac using Chicken of the VNC. For Sarah, everything works fine. However for Bob, the toolbar along the top is missing and every... (0 Replies)
Discussion started by: user23
0 Replies
10. UNIX for Dummies Questions & Answers
how to find all the processes associated with a given process in unix,is there any command for this. (3 Replies)
Discussion started by: laddu
3 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)