0

Hi,

can anyone please help me to find out a solution for the below mentioned problem??
While installing oracle 11g in linux on a remote desktop, failed dependencies occured when installing rpm packages
[i want a soluion withou using yum software]

[root@TomcatServer Server]# rpm -Uvh gcc-4.*
warning: gcc-4.1.2-44.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:cpp = 4.1.2-44.el5 is needed by gcc-4.1.2-44.el5.x86_64

Edited by Priyanka_9

2
Contributors
2
Replies
12
Views
2 Years
Discussion Span
Last Post by hiren2927
0

A. Check the machine is installed gcc
In the terminal enter: gcc: rpm -q gcc
Before installing the return result is:
[Root @ localhost gcc] # rpm -q gcc
package gcc is not installed
The results are returned after the installation:
[Root @ localhost /] # rpm -q gcc
gcc-4.1.2-44.el5
If you can use yum:

Installation gcc compiler (can compile C program)

yum install gcc

Install g ++ (before installation can compile C ++ programs)

yum install gcc-c ++
If you can not use yum:
Second, download the required packages:
1.kernel-headers-2.6.18-128.el5.i386.rpm
2.glibc-common-2.5-34.i386.rpm
3.glibc-2.5-34.i386.rpm
4.glibc-headers-2.5-34.i386.rpm
5.glibc-devel-2.5-34.i386.rpm
6.cpp-4.1.2-44.el5.i386.rpm
7.libgomp-4.3.2-7.el5.i386.rpm
8.libgcc-4.1.2-44.el5.i386.rpm
9.gcc-4.1.2-44.el5.i386.rpm
Below is needed to install g ++ package, I did not succeed to install
10.libstdc ++ - devel-4.1.2-44.el5.i386.rpm
11.gcc-c ++ - 4.1.2-44.el5.i386.rpm
Most packages http://xiaolong0211.iteye.com/blog/758269 page can be downloaded directly onto the bottom,
glibc-common-2.5-34.i386.rpm Download package is ftp://ftp.tu-chemnitz.de/.SAN0/pub/linux/scientific/53/i386/SL/repodata/repoview/glibc-common -0-2.5-34.html ,
Download glibc-2.5-34.i386 package is http://rpm.pbone.net/index.php3/stat/4/idpl/12883715/dir/startcom_5/com/glibc-2.5-34.i386.rpm. html ,
I'll upload some packages later.
The focus of these packages into a folder, such as: / opt / gcc
III. To begin the installation
1. Go to the root user (su -)
2. Go to the folder where the files package (cd / opt / gcc)
3. Run the following command:
rpm -ivh ./kernel-headers-2.6.18-128.el5.i386.rpm
rpm -ivh --force glibc-common-2.5-34.i386.rpm
rpm -ivh --force glibc-2.5-34.i386.rpm (rpm -ivh --force rpmpackage.rpm able to force the installation of a piece of software)
rpm -ivh glibc-headers-2.5-34.i386.rpm
.......
From 1 in accordance with the above - the order of> 10 to install on the line
IV. Some cases may occur during installation
1. There is no use of root privileges:
In the terminal enter: rpm -ivh --force glibc-2.5-34.i386.rpm displays the following information,
warning: glibc-common-2.5-34.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 652e84dc
error: can not create transaction lock on /var/lib/rpm/__db.000
Use the root user (su -)
2. The system of some package than the package you want to install the update
eg: [root @ localhost gcc] # rpm -ivh cpp-4.1.2-44.el5.i386.rpm states the following:
A new is ....... and ........... probably means a package to install the update now than we would want to install,
No need to install, but now the package but not installed, would not be able to resolve dependencies, there is no way to install other packages, resulting in the earliest software can not be installed.
Solutions are as follows:
Enter the root user: rpm -e softWareName (eg: rpm -e cpp-4.1.2-44.el5 or rpm -e --allmatches cpp-4.1.2-44.el5),
Then reinstall the package
3. Some package does not solve the problem if you rely on input rpm -ivh ./xxxxx.rpm following message appears,
eg: [root @ localhost gcc] # rpm -ivh cpp-4.1.2-44.el5.i386.rpm
warning: ./glibc-headers-2.5-34.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:
glibc = 2.5-34 is needed by glibc-headers-2.5-34.i386
That is before you install glibc-headers-2.5.34.i386.rpm package, you should first install the glibc-2.5.-34.rpm package, google search at the appropriate package installed on the line.
4. Some packages require the mandatory installation rpm -ivh ./xxxxx.rpm appear if you enter the following information:
eg: [root @ localhost gcc] # rpm -ivh cpp-4.1.2-44.el5.i386.rpm
file / usr / bin / cpp from install of cpp-4.1.2-44.el5.i386 conflicts with file from package cpp-4.1.2-46.el5.i386
file /usr/libexec/gcc/i386-redhat-linux/4.1.1/cc1 from install of cpp-4.1.2-44.el5.i386 conflicts with file from package cpp-4.1.2-46.el5.i386
file /usr/share/man/man1/cpp.1.gz from install of cpp-4.1.2-44.el5.i386 conflicts with file from package cpp-4.1.2-46.el5.i386
At this point it should be modified to order:
[Root @ localhost gcc] # rpm -ivh --force cpp-4.1.2-44.el5.i386.rpm
5. If a package is installed successfully installed successfully usually states the following:
[Root @ localhost Server] # rpm -ivh ./kernel-headers-2.6.18-128.el5.i386.rpm
warning: ./kernel-headers-2.6.18-128.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing ... ########################################### [100% ]
1: kernel-headers ########################################### [100 %]
........
V. problem I encountered
1. The following two are installed g ++ package, I did not succeed to install
libstdc ++ - devel-4.1.2-44.el5.i386.rpm
gcc-c ++ - 4.1.2-44.el5.i386.rpm
When you run the libstdc ++ - devel-4.1.2-44.el5.i386.rpm when prompted:
[Root @ localhost gcc] # rpm -ivh ./libstdc++-devel-4.1.2-44.el5.i386.rpm
warning: ./libstdc++-devel-4.1.2-44.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:
libstdc ++ = 4.1.2-44.el5 is needed by libstdc ++ - devel-4.1.2-44.el5.i386
I did not find libstdc ++ online - 4.1.2-44.el5.rpm package ( , Who has made a chant), we do not yet installed g ++
2. If use yum like, this installed a retHat5.4 not registered, you should install a fedora, can simply get the problem must not be complicated

References:
http://xiaolong0211.iteye.com/blog/758269
http://my.oschina.net/duxuefeng/blog/29115
http://www.jb51.net/os/RedHat/1266.html
http://blog.csdn.net/zgbsoap/article/details/411646

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.