From: Thomas <spiralman@softhome.net>
To: gcc-help@gcc.gnu.org
Subject: c++ linking probs after gcc 3.0.3 upgrade
Date: Tue, 05 Feb 2002 15:59:00 -0000 [thread overview]
Message-ID: <courier.3C607164.00005408@softhome.net> (raw)
ok, i upgraded to gcc 3.0.3, first by compiling from source, and then i got a
bunch of undefined references to functions and whatnot in iostream.h (endl,
cout, etc). then i installed the gcc 3.0.3 slackware package (im running
slackware 7.1, but ive upgraded it a lot), and now i get all those errors,
plus undefined references to "__builtin_delete" and the like. im assuming im
linking to the wrong librarys or something, but im not sure. do i have to
install a new version of libc? i remember reading the gcc 3.x cant compile
libc. i tried doing a "make uninstall" in my source tree, but i get an error
that that isnt supported in that tree.
if you need more info, just tell me
thanks in advance
thomas
spiralman@softhome.net
next reply other threads:[~2002-02-05 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 15:59 Thomas [this message]
2002-02-06 15:27 ` Andrea 'Fyre Wyzard' Bocci
2002-02-08 8:31 ` Thomas
2002-02-09 1:43 ` Thomas
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=courier.3C607164.00005408@softhome.net \
--to=spiralman@softhome.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).