public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
To: gcc-help@gcc.gnu.org
Subject: Re: Using gcc
Date: Sat, 24 Dec 2005 20:00:00 -0000	[thread overview]
Message-ID: <43ADA8CD.2870FE2B@dessent.net> (raw)
In-Reply-To: <20051224.113905.26478.226609@webmail27.lax.untd.com>

"jjwdeck@juno.com" wrote:

>         Checking the documentation for a version of gcc close to this one gave me now clue as to how to resolve the linker error.  I ended up searching  /usr/lib for __gxx_personality_v0 to find libstdc++.a which so happened to define the reference.  Where do I find documentation that will tell me how to get started doing a compile in this situation?  Also what is this 'personality' type of name the linker needs?

You shouldn't have to specify any of that kind of junk.  It should just
work.  But you didn't include the exact command(s) you used to compile
and link and without that info it's pretty hard to assist you.

The kind of error that you're seeing is often caused by trying to link
by calling 'ld' directly instead of using the 'gcc' command, or trying
to link C++ code by calling 'gcc' instead of 'g++'.  You should always
link with 'gcc', unless you have any C++ code in which case you should
compile and link with 'g++'.  By doing this the necessary internal
library bits will always be added automatically.

Brian

  reply	other threads:[~2005-12-24 20:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-24 19:40 jjwdeck
2005-12-24 20:00 ` Brian Dessent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-28 20:40 Thai Dang Vu
2002-03-28 20:40 Mariappan, MaharajanX
2002-03-28 20:30 Francisco Mendez
2001-09-14  8:39 charles scott
2001-09-14  9:14 ` Claudio Bley
2001-09-14  9:28 ` 홍근식

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=43ADA8CD.2870FE2B@dessent.net \
    --to=brian@dessent.net \
    --cc=gcc-help@gcc.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).