From: Jonathan Larmour <jlarmour@redhat.com>
To: Ron Kundla <rkundla@nband.com>
Cc: "eCos Mailing List (E-mail)" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Build error under current x86 - have you seen this?
Date: Tue, 24 Jul 2001 19:22:00 -0000 [thread overview]
Message-ID: <3B5E2D5A.30B15CA8@redhat.com> (raw)
In-Reply-To: <C91EB7099291D3118E7600A0C9E91B297B52E6@gonband.nband.com>
Ron Kundla wrote:
>
> The part I am concerned about is the undefined reference to '__builtin_new'
> from the stream.inl file. I have looked at fdopen and there is a call to a
> C++ function that does a 'set_position', which coincides with the above
> error.
Are you using gcc 3 by any chance? If so, don't (yet).
If you are using something earlier, it should have been resolved by a
__builtin_new symbol in libgcc in your i386-elf-gcc.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/
prev parent reply other threads:[~2001-07-24 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-24 17:20 Ron Kundla
2001-07-24 19:22 ` Jonathan Larmour [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=3B5E2D5A.30B15CA8@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=rkundla@nband.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).