From: Fredrik Hederstierna <fredrik@wespot.com>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] newlib includes
Date: Tue, 16 Sep 2003 11:12:00 -0000 [thread overview]
Message-ID: <3F66F138.C69993D2@wespot.com> (raw)
In-Reply-To: <20030915144920.48cecd8b.jani@iv.ro>
Newlib + eCos question:
I have built my GCC with newlib, but how can I control if I would like to
use any newlib-functions with my own code?
E.g. I know there is optimized versions of libm and libc functions, but
eCos implements same function, and I would like to use the newlib version
of e.g. sin(), strcat() etc.
Do I have to switch completly to newlib or can I pick up just parts of it
and link it with my eCos code?
Best Regards,
/Fredrik
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2003-09-16 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 16:39 [ECOS] Question on PCI DMA memory kevin_lemay
[not found] ` <008e01c37b7e$08b0dc10$d8496fa6@PredNotebook>
2003-09-15 11:48 ` [ECOS] Question on FIS Pred
2003-09-15 12:04 ` Jani Monoses
2003-09-16 11:12 ` Fredrik Hederstierna [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=3F66F138.C69993D2@wespot.com \
--to=fredrik@wespot.com \
--cc=ecos-discuss@sources.redhat.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).