From: Thomas <spiralman@softhome.net>
To: gcc-help@gcc.gnu.org
Subject: Re: c++ linking probs after gcc 3.0.3 upgrade
Date: Fri, 08 Feb 2002 08:31:00 -0000 [thread overview]
Message-ID: <courier.3C63FC00.000053DE@softhome.net> (raw)
In-Reply-To: <5.1.0.14.0.20020206230345.00aa39c8@popmail.inwind.it>
ok, i might try checking what glibc i need. but the thing is, these
problems im having dont seem to be related to libc (in my uninformed
opinion). i thought that libc was c only, not c++, and all the problems im
having are with c++ specific things. even if libc does have c++ functions in
it __builtin_delete should be a function of a compiler. isnt it whats added
to the destructor of a class when you dont explicitly delete a member fo that
class that you created with new? so, i guess my question is, is this a libc
problem or not, and if not, what is it a problem with. the main reason im
having problems is i dont really know where to look for something that is
misconfigured or whatever...
thanks
thomas
spiralman@softhome.net
On Wednesday 06 February 2002 04:07, you wrote:
> At 17.58 05/02/2002 (GMT -0600), Thomas wrote:
> >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 don't know what's the minimum version of glibc you need to build GCC.
> There's a page on the site devoted to all the successful GCC builds,
> pointing to the posts of who managed to do so. So you might have a look if
> there's anything related to Slackware 7.1.
> Anyway, I think glibc 2.2.3 or newer will be fine.
>
> >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
>
> HTH
> fwyzard
next prev parent reply other threads:[~2002-02-08 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 15:59 Thomas
2002-02-06 15:27 ` Andrea 'Fyre Wyzard' Bocci
2002-02-08 8:31 ` Thomas [this message]
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.3C63FC00.000053DE@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).