public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: martin.berger@orange.net
Cc: gcc-help@gcc.gnu.org
Subject: Re: problem with iostream
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200003262120.XAA12368@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <20000401000000.YvSV38PjjKCXWwm_hQTxqIPxiXkgvaYLK-nyOdgXBsM@z> (raw)
In-Reply-To: <000801bf9760$9bd75ba0$e801bc3e@default>

> i have overwritten my previous (2 year old) installation.  i suspect
> that your analysis is correct. alas i am not familiar enough with the
> g++ library system to work out which files are the troublemakers.
> (btw: is there an easily accessible description of the structure
> of g++ and its libraries, or do i have to read the code/man pages to
> get the picture?)

There is no easy description, because the matter is not very easy.  I
noticed that a number of things have gone wrong. Could you please let
me know what RPM packages related to g++ you have installed? You get a
list by doing

rpm -qa|grep gcc

This won't print all, you also need

rpm -qa|grep libstd

You can use RPM to get a description of these packages, and to look
what files they contain.

*In particular*, you should have a libstdc++-devel package
installed. Please make sure you do, and report its package name as
well as the names of the other packages. Also, please report the exact
location where you got the packages from (if you got them from a
CD-ROM, please report the version numbers printed on the CD-ROM
label).

>   libm.so.6 =3D> /lib/libm.so.6 (0x40018000)
>   libc.so.6 =3D> /lib/libc.so.6 (0x40035000)
>   /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x40000000)

That is not right - your compiler should have linked a shared version
of libstdc++ (unless you added -static). Please add -Wl,--verbose to
the compiler line and report the output of the linker. In particular,
look for the place where it gets libstdc++.a from, and check whether
there is a libstdc++.so nearby - there should be.

>   #include <...> search starts here:
>    /usr/local/include/g++

This is also not right. Please do 

  rpm -qf  /usr/local/include/g++

and report which package this directory came from. For egcs 2.91.66,
the include directory should be called g++-2.

>    /usr/local/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/include

??? Are you sure the gcc installation came from a redhat package???
RedHat never installed gcc into /usr/local, AFAIK. Where did this
compiler come from? Please do

rpm -qf /usr/local/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/cc1plus

and report its output.

Regards,
Martin

  reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-26 12:18 Martin Berger
2000-03-26 13:24 ` Martin v. Loewis [this message]
2000-04-01  0:00   ` Martin v. Loewis
2000-04-01  0:00 ` Martin Berger
  -- strict thread matches above, loose matches on Subject: below --
2000-03-24  3:11 martin.berger
2000-03-25 11:03 ` Martin v. Loewis
2000-04-01  0:00   ` Martin v. Loewis
2000-04-01  0:00 ` martin.berger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200003262120.XAA12368@loewis.home.cs.tu-berlin.de \
    --to=martin@loewis.home.cs.tu-berlin.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=martin.berger@orange.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).