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@talk21.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: problem with iostream
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200003251857.TAA25498@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <20000401000000.irfIP4XVfb1uSJeMvqb4t1e3TIiRvkfMci8xVJLKtlo@z> (raw)
In-Reply-To: <20000324111140.IFSD24016.t21mta03-app.talk21.com@t21mtaV-lrs>

> hello, i have just upgraded to the latest version of redhat linux
> and suddenly my g++ compiled programs fall over.

From your description, it was not clear whether the old binaries
stopped working on the new system, or whether binaries created on the
new system with the new compiler would break.

Also, it is not clear to me whether you have installed the latest
redhat version "from scratch", or overwritten your previous
installation. It may well be that there were still some old files
lying around which should have been removed but weren't.

To investigate this further, please try the following commands:

ldd <your compiled program>
g++ -o <output file> <your source file> -v --trace-includes

From looking at such output, it might be possible to tell what went
wrong. In case of ldd, please check whether any of the libraries are
symbolic links, and look up the files behind the symbolic links. Also,
for each of those, invoke

rpm -qf <library name>

and report the names of the RPM packages where these files
originate. It would also help if you let us know the exact version of
redhat linux you are using, instead of saying it is "the latest" one.

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-24  3:11 martin.berger
2000-03-25 11:03 ` Martin v. Loewis [this message]
2000-04-01  0:00   ` Martin v. Loewis
2000-04-01  0:00 ` martin.berger
2000-03-26 12:18 Martin Berger
2000-03-26 13:24 ` 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=200003251857.TAA25498@loewis.home.cs.tu-berlin.de \
    --to=martin@loewis.home.cs.tu-berlin.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=martin.berger@talk21.com \
    /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).