04-09-2020
Hi,
AIX is not any different from ANY other operating system when handling open source software - you are forever buried in dependency hell, because just because you see a certain library on the system does not mean it is in exactly the version the given package is asking for. So making one tool work might break another. It often helps to just install the libraries in the very latest versions you can find. Most rpms can be downloaded from IBM itself, or from various other web sources that provide rpms for AIX, for example
here. You can always force install with
--nodeps option, but its unlikely that your software works afterwards without finding the correct libraries required.
10 More Discussions You Might Find Interesting
1. 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
2. Solaris
Hi All,
Where do I find/download this font package 'FONT_FAMILY_SANS_SERIF-FONT_STYLE_NORMAL-14' and how to install it ?
When I run an osi utility (ftamtool) it shows me this error:
##FTAM Tool : XView ERROR
XView warning: Impossible de charger le jeu de caractères 'FONT_FAMILY_SANS_SERI... (0 Replies)
Discussion started by: andryk
0 Replies
3. Red Hat
Dear Friends ,
I am using RHEL 5 server . In Linux when I am going to install 'mod_ssl' rpm then I got the following error :
# rpm -ivh mod_ssl-2.2.3-6.el5.i386.rpm --aid --force
warning: mod_ssl-2.2.3-6.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed... (5 Replies)
Discussion started by: shipon_97
5 Replies
4. UNIX for Dummies Questions & Answers
Hi everyone,
Hope u doing good.
I am trying to installl WebSphere Application Server(WAS) ND package, i got problem at initial level
I hope, the problem is with Mozilla browzer. Can anyone trobleshoot the problem
An error occurred while starting the launchpad for a WebSphere Application ... (0 Replies)
Discussion started by: sarfraz
0 Replies
5. BSD
Hey all I'm having a little trouble installing a MySQL database. This is what I tried...
export PKG_PATH=ftp://mirror.planetunix.net/pub/OpenBSD/4.9/packages/`machine -a`
pkg_add -v mysql-server mysql-client
and this is what I get
Unknown element: @rcscript /etc/rc.d/mysqld in... (1 Reply)
Discussion started by: desreguard
1 Replies
6. Red Hat
Hello All,
I was trying to install one rpm and it failed due to missing dependencies, when I try to look at the dependencies and try to install them it is asking for 100+ dependencies, did any one ever face this problem? how can we fix this?
rpm -ivh /var/tmp/erlang-R15B-02.1.el6.x86_64.rpm... (0 Replies)
Discussion started by: lovesaikrishna
0 Replies
7. Linux
Hi all,
i'm trying to upgrade pandorafms to the new version 4.0.3-130118,
actually i have installed on my machine the version 3.0.0-8.1.el5,
the error i'm getting when trying to update its the following
rpm -Uvh pandorafms_agent_unix-4.0.3-130118.noarch.rpm
error: Failed dependencies:
... (1 Reply)
Discussion started by: charli1
1 Replies
8. Red Hat
I'm trying to package the latest Oracle JDK (1.7.0_51) into an RPM. Packaging works fine but when i try to install via rpm -Uvh xxx.rpm, i get the following:
#sudo rpm -ivh Sun_JDK7-1.7.0-51.x86_64.rpm
error: Failed dependencies:
libavcodec.so.52()(64bit) is needed by Sun_JDK7-1.7.0-51.x86_64... (3 Replies)
Discussion started by: asc123321
3 Replies
9. Linux
Hi,
While installing perl5.14 on my Linux box its failing with c compiler issue.
below is the error message.
Use which C compiler?
./trygcc: line 10: cc: command not found
Uh-oh, the C compiler 'cc' doesn't seem to be working.
./trygcc: line 25: gcc: command not found
./checkcc:... (11 Replies)
Discussion started by: muzaffar.k
11 Replies
10. HP-UX
Hi,
I need to use the tool "meminfo" in the server, however am not able to as it says the package is not found.
I am also not able to find the package in the "HPUX Porting and Archive center".
Please guide on how to install this package?
Thanks,
Aigini (1 Reply)
Discussion started by: anaigini45
1 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)