From: Michael Still <mikal@stillhq.com>
To: Robert Spanton <rob@xgoat.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Yaaarrgghh - help me, please!
Date: Sun, 12 May 2002 13:35:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0205130633430.12913-100000@localhost.localdomain> (raw)
In-Reply-To: <008d01c1f9d3$f915dda0$0a00000a@zarquin>
On Sun, 12 May 2002, Robert Spanton wrote:
> I'm trying to port the C++ libraries to my own os, yet there appears to be
> one barrier. This appears to be the file called "libc.a". I have looked
> around for a while to try and find out what this file actually contains and
> how g++ uses it.
libc.a is the statically linkable version of your c library. This library
implements all the standard things you get for free with c and c++ -- for
instance printf, fopen, et cetera.
> Does anyone out there know (of a list - as there are probably loads) what
> functions I need to put into my own libc.a file?
Implementing this is a _big_ job. Have a hunt on the gnu.org website for
the glibc manual -- last time I checked it was something like 600 pages.
Cheers,
Mikal
--
Michael Still (mikal@stillhq.com) UMT+10hrs
prev parent reply other threads:[~2002-05-12 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 9:42 Robert Spanton
2002-05-12 13:35 ` Michael Still [this message]
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=Pine.LNX.4.30.0205130633430.12913-100000@localhost.localdomain \
--to=mikal@stillhq.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rob@xgoat.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).