From: "Manuel Coutinho" <manuel.coutinho@edisoft.pt>
To: "'ali hagigat'" <hagigatali@gmail.com>, <gcc-help@gcc.gnu.org>
Subject: RE: -nostdlib option!
Date: Mon, 07 Feb 2011 12:44:00 -0000 [thread overview]
Message-ID: <F23B6199756D4C37A0CE5D8B4AD493AB@WIN5IN206U17AR> (raw)
In-Reply-To: <AANLkTikApDR9rprmXweh67Fju2NFgp7G+qKwsUJrD8bh@mail.gmail.com>
Hi
Other mechanism: supply your own memset, memcpy, etc.
If you do this, the linker will know which memset, memcpy, etc to use and
will not complaint about not using libc.
Regards
Manuel Coutinho
-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of ali hagigat
Sent: 07 February 2011 11:04
To: gcc-help@gcc.gnu.org
Subject: -nostdlib option!
I have copied part of gcc manual:
------------------------------------
Do not use the standard system startup files or libraries when
linking. No startup files and only the libraries you specify will be
passed to the linker. The compiler may generate calls to "memcmp",
"memset", "memcpy" and "memmove". These entries are usually resolved
by entries in libc. These entry points should be supplied through
some other mechanism when this option is specified.
------------------------------------
What is some other mechanism? How can i use -nostdlib?
next prev parent reply other threads:[~2011-02-07 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:18 ali hagigat
2011-02-07 11:21 ` Drasko DRASKOVIC
2011-02-07 12:44 ` Manuel Coutinho [this message]
2011-02-07 14:43 ` ali hagigat
2011-02-07 15:22 ` Kai Ruottu
2011-02-07 16:20 ` Manuel Coutinho
2011-02-07 16:48 ` Drasko DRASKOVIC
2011-02-07 17:57 ` Manuel Coutinho
[not found] ` <4D59BEDC.9000606@yahoo.com>
2011-02-15 9:50 ` ali hagigat
2011-02-15 10:28 ` Axel Freyn
2011-02-15 12:13 ` Jonathan Wakely
2011-02-16 10:05 ` Axel Freyn
2011-02-15 14:56 ` Thomas Martitz
2011-02-15 15:52 ` Ian Lance Taylor
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=F23B6199756D4C37A0CE5D8B4AD493AB@WIN5IN206U17AR \
--to=manuel.coutinho@edisoft.pt \
--cc=gcc-help@gcc.gnu.org \
--cc=hagigatali@gmail.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).