public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* libstdc++ 2.9.0
@ 1998-10-11 19:05 Gerald Gutierrez
  1998-10-12  3:06 ` Wojtek Slusarczyk
  1998-10-12 20:53 ` Carlo Wood
  0 siblings, 2 replies; 3+ messages in thread
From: Gerald Gutierrez @ 1998-10-11 19:05 UTC (permalink / raw)
  To: EGCS List

Hi all.

This may be a little off topic, but I thought the people in this list
will be most knowledgeable in this area. Please email me replies.

I've been trying to install libstdc++-2.9.0 on top of libstdc++-2.8.0
while I was upgrading to egcs 1.1. As it turns out, this is a problem
under RH5.1 because many packages do not have dependencies on libstdc++
as a package, but on libstdc++.so.2.8 as a file. Trying to upgrade
libstdc++, then, breaks a lot of dependencies :

# rpm -Uvh libstdc++-2.9.0-1.i386.rpm 
failed dependencies:
        libstdc++ = 2.8.0 is needed by libstdc++-devel-2.8.0-8
        libstdc++.so.2.8 is needed by groff-1.11a-6
        libstdc++.so.2.8 is needed by qt-1.40-1rh51
        libstdc++.so.2.8 is needed by qt-devel-1.40-1rh51
        libstdc++.so.2.8 is needed by lyx-0.12.0-3
        libstdc++.so.2.8 is needed by ical-2.2-7
        libstdc++.so.2.8 is needed by fvwm2-2.0.47-1

I don't want to force the installation because then the dependencies are
broken and I don't know what havoc may ensue. 

What am I supposed to do ?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: libstdc++ 2.9.0
  1998-10-11 19:05 libstdc++ 2.9.0 Gerald Gutierrez
@ 1998-10-12  3:06 ` Wojtek Slusarczyk
  1998-10-12 20:53 ` Carlo Wood
  1 sibling, 0 replies; 3+ messages in thread
From: Wojtek Slusarczyk @ 1998-10-12  3:06 UTC (permalink / raw)
  To: Gerald Gutierrez; +Cc: EGCS List

On Sun, 11 Oct 1998, Gerald Gutierrez wrote:

Hi Gerald,

> # rpm -Uvh libstdc++-2.9.0-1.i386.rpm 
> failed dependencies:
>         libstdc++ = 2.8.0 is needed by libstdc++-devel-2.8.0-8
>         libstdc++.so.2.8 is needed by groff-1.11a-6
>         libstdc++.so.2.8 is needed by qt-1.40-1rh51
>         libstdc++.so.2.8 is needed by qt-devel-1.40-1rh51
>         libstdc++.so.2.8 is needed by lyx-0.12.0-3
>         libstdc++.so.2.8 is needed by ical-2.2-7
>         libstdc++.so.2.8 is needed by fvwm2-2.0.47-1

1. % rpm -e libstdc-devel
2. % rpm -Uvh libstdc++-2.9.0-1.i386.* --nodeps
3. % rpm -Uvh groff-1.11a-6.src.rpm (!) ; vi /usr/src/rpm/SPECS/groff*
   (change Version 6 to Version 7); rpm -bb /usr/src/rpm/SPECS/groff*;
   rpm -Uvh /usr/src/rpm/RPMS/i386/groff*

or just: rpm --rebuild groff*.src.rpm; 
rpm -Uvh /usr/src/rpm/i386/groff* --force

4. rpm -e qt-devel
   (rpm -Uvh qt-1.40*.src.rpm ....  or just: rpm --rebuild qt-*.src.rpm;
    rpm -Uvh --force /usr/src/rpm/RPMS/i386/qt-*

5. etc, etc ...

regards,

Wojciech Slusarczyk (091)4494148
Technical University of Szczecin
PGP KeyServer pgpkeys.mit.edu


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: libstdc++ 2.9.0
  1998-10-11 19:05 libstdc++ 2.9.0 Gerald Gutierrez
  1998-10-12  3:06 ` Wojtek Slusarczyk
@ 1998-10-12 20:53 ` Carlo Wood
  1 sibling, 0 replies; 3+ messages in thread
From: Carlo Wood @ 1998-10-12 20:53 UTC (permalink / raw)
  To: Gerald Gutierrez; +Cc: egcs

Alternatively, you just install libstdc++-2.9 NEXT to libstdc++-2.8
They perfectly coexist.

The only important thing to do when installing egcs-1.1 as default
compiler is to make sure that the link libstdc++.so points to
libstdc++-2.9 :).

I have RedHat 5.0, and use egcs-1.1b without problems.
My links are as follows:

-r-xr-xr-x   1 root     root       394489 May  7 20:20 /usr/lib/libstdc++.so.2.8.0
-r-xr-xr-x   1 root     root      1025339 Oct 15  1997 /usr/lib/libstdc++.so.2.7.2.8
lrwxrwxrwx   1 root     root           20 Aug 17 03:05 /usr/lib/libstdc++.so.2.7.2 -> libstdc++.so.2.7.2.8
lrwxrwxrwx   1 root     root           18 Aug 17 03:05 /usr/lib/libstdc++.so.2.8 -> libstdc++.so.2.8.0
-rw-r-----   1 root     root       334110 Sep  7 17:13 /usr/local/egcs/lib/libstdc++.a
lrwxrwxrwx   1 root     root           18 Sep  7 17:13 /usr/local/egcs/lib/libstdc++.so -> libstdc++.so.2.9.0
-r-xr-xr-x   1 root     root       408751 Sep  7 17:13 /usr/local/egcs/lib/libstdc++.so.2.9.0
lrwxrwxrwx   1 root     root           18 Sep  7 17:13 /usr/local/egcs/lib/libstdc++.so.2.9 -> libstdc++.so.2.9.0
lrwxrwxrwx   1 root     root           19 Aug 17 03:00 /usr/i486-linux-libc5/lib/libstdc++.so.27 -> libstdc++.so.27.1.4
-rwxr-xr-x   1 root     root       841780 May  6 05:54 /usr/i486-linux-libc5/lib/libstdc++.so.27.1.4


| On Sun, 11 Oct 1998, Gerald Gutierrez wrote:
| 
| Hi Gerald,
| 
| > # rpm -Uvh libstdc++-2.9.0-1.i386.rpm 
| > failed dependencies:
| >         libstdc++ = 2.8.0 is needed by libstdc++-devel-2.8.0-8
| >         libstdc++.so.2.8 is needed by groff-1.11a-6
| >         libstdc++.so.2.8 is needed by qt-1.40-1rh51
| >         libstdc++.so.2.8 is needed by qt-devel-1.40-1rh51
| >         libstdc++.so.2.8 is needed by lyx-0.12.0-3
| >         libstdc++.so.2.8 is needed by ical-2.2-7
| >         libstdc++.so.2.8 is needed by fvwm2-2.0.47-1
| 
| 1. % rpm -e libstdc-devel
| 2. % rpm -Uvh libstdc++-2.9.0-1.i386.* --nodeps
| 3. % rpm -Uvh groff-1.11a-6.src.rpm (!) ; vi /usr/src/rpm/SPECS/groff*
|    (change Version 6 to Version 7); rpm -bb /usr/src/rpm/SPECS/groff*;
|    rpm -Uvh /usr/src/rpm/RPMS/i386/groff*
| 
| or just: rpm --rebuild groff*.src.rpm; 
| rpm -Uvh /usr/src/rpm/i386/groff* --force
| 
| 4. rpm -e qt-devel
|    (rpm -Uvh qt-1.40*.src.rpm ....  or just: rpm --rebuild qt-*.src.rpm;
|     rpm -Uvh --force /usr/src/rpm/RPMS/i386/qt-*
| 
| 5. etc, etc ...
| 
| regards,
| 
| Wojciech Slusarczyk (091)4494148
| Technical University of Szczecin
| PGP KeyServer pgpkeys.mit.edu

-- 
 Carlo Wood  <carlo@runaway.xs4all.nl>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~1998-10-12 20:53 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-10-11 19:05 libstdc++ 2.9.0 Gerald Gutierrez
1998-10-12  3:06 ` Wojtek Slusarczyk
1998-10-12 20:53 ` Carlo Wood

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).