public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Tom Browder" <tom3@fwb.asi.srs.com>
To: <gcc-help@gnu.org>
Subject: Link Error
Date: Tue, 13 Aug 2002 06:54:00 -0000	[thread overview]
Message-ID: <000001c242d1$ce6be210$cb01000a@srsez2mh0xn85s> (raw)

I compile a program on host A (Linux, i386) with g++-3.1.1.  I copy it
to machine B and attempt to execute it and get the following message:

makebar: /usr/local/lib/libstdc++.so.4: no version information available
required by makebar)

I recompile the same program on host B (Linux, i386) with g++-3.1.1 and
it works fine.

What is happening, please?

Thanks.

Tom Browder



             reply	other threads:[~2002-08-13 13:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13  6:54 Tom Browder [this message]
2002-08-13  7:16 ` Ish Rattan
2002-08-13  7:30   ` Tom Browder
2002-08-13  7:59     ` Ish Rattan
     [not found] <AANLkTiniPnQ-ioijpQXhMC1ygSqNSZsEGW2O-OVS5Qa8@mail.gmail.com>
2010-08-12 10:18 ` Link error Andrew Haley
  -- strict thread matches above, loose matches on Subject: below --
2009-04-01 13:23 link error Duan Wang
2009-04-01 13:42 ` Axel Freyn
2008-08-15 20:39 Link error Vardhan, Sundara (GE Infra, Energy)
2008-07-24 21:03 Vardhan, Sundara (GE Infra, Energy)
2008-07-24 23:55 ` Rob Sherry
2008-07-25 13:32   ` Vardhan, Sundara (GE Infra, Energy)
2008-07-28 11:41     ` Andrew Haley
2008-07-28 12:14       ` Vardhan, Sundara (GE Infra, Energy)
2008-07-28 13:26         ` Andrew Haley
2008-07-29  8:56           ` Ralf Wildenhues
2008-07-29 11:49             ` Andrew Haley
2008-07-29 13:43               ` Vardhan, Sundara (GE Infra, Energy)
2008-07-24 10:04 Vardhan, Sundara (GE Infra, Energy)
2005-10-21 20:22 link error Moon Hwang
2005-10-21 23:08 ` Brian Dessent
2002-10-17  8:11 Link error HKOELMAN
2001-06-05 14:22 link error Alex Fridman

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='000001c242d1$ce6be210$cb01000a@srsez2mh0xn85s' \
    --to=tom3@fwb.asi.srs.com \
    --cc=gcc-help@gnu.org \
    /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).