From: Benjamin Krill <ben@codiert.org>
To: "David H. Lynch Jr" <dhlii@comcast.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: compiling withoug glibc
Date: Mon, 12 Mar 2007 07:42:49 +0100 [thread overview]
Message-ID: <20070312064248.GA31115@codiert.org> (raw)
In-Reply-To: <45F4D72F.8010101@comcast.net>
Hey,
did you try the options "-nostdlib -nostdinc"?
cheers
ben
* David H. Lynch Jr | 2007-03-11 23:29:35 [-0500]:
>
> I have several projects that need to be built using GCC but
>absolutely no external libraries, headers etc.
> not glibc, not uClibc, nothing.
>
> I also need to do this under both windows and Linux.
>
> I have been somewhat successful by renaming directories inside the
>crosscompiler subdirectory so that gcc, ... can't find any standard
>libraries etc.
>
> But I can not get this to work uniformly accross platforms, and I
>can not trivially reverse it when I do need glibc.
>
> I have the vaguest clue that doing this has something to do with
>triggering gcc to run through different peices of the "specs" file,
> but what I can find of documentation is opaque too me.
>
> A clue would be greatly appreciated.
>
>
>
>
>
>--
>Dave Lynch DLA Systems
>Software Development: Embedded Linux
>717.627.3770 dhlii@dlasys.net http://www.dlasys.net
>fax: 1.253.369.9244 Cell: 1.717.587.7774
>Over 25 years' experience in platforms, languages, and technologies too numerous to list.
>
>"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
>Albert Einstein
>
>_______________________________________________
>Linuxppc-embedded mailing list
>Linuxppc-embedded@ozlabs.org
>https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
[ Benjamin Krill ][ ben(@)codiert(.)org ][ http://codiert.org ]
prev parent reply other threads:[~2007-03-12 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 4:29 compiling withoug glibc David H. Lynch Jr
2007-03-12 6:42 ` Grant Likely
2007-03-12 6:42 ` Benjamin Krill [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=20070312064248.GA31115@codiert.org \
--to=ben@codiert.org \
--cc=dhlii@comcast.net \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.