From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc missing limits.h
Date: Wed, 9 Jul 2008 13:38:45 +0200 [thread overview]
Message-ID: <20080709113845.GB27321@mx.loc> (raw)
In-Reply-To: <48746EC3.2020008@cetrtapot.si>
On Wed, Jul 09, 2008 at 09:54:43AM +0200, Hinko Kocevar wrote:
>Bernhard Fischer wrote:
>> On Thu, Jul 03, 2008 at 09:05:06AM +0200, Hinko Kocevar wrote:
>>>> Removing "-nostdinc" from CFLAGS in "uClibc-0.9.29/Rules.mak"
>>>> allows the ARM compilation to continue,
>>> But is this OK?
>>
>> no.
>
>Looking at the gcc manual "-nostdinc" causes compiler to omit the standard include directories:
>Or we could use "-isystem" flag:
No, better pull the fix that we have in uClibc-trunk, short of using the
trunk in the first place.
>PS.: Now I know what -I=dir stands for :)
heh ;)
next prev parent reply other threads:[~2008-07-09 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 12:22 [Buildroot] uClibc missing limits.h Hinko Kocevar
2008-06-23 13:16 ` Bernhard Fischer
2008-06-24 11:14 ` Hinko Kocevar
2008-07-02 8:59 ` Hinko Kocevar
2008-07-02 18:22 ` Ulf Samuelsson
2008-07-03 7:05 ` Hinko Kocevar
2008-07-03 8:05 ` Bernhard Fischer
2008-07-09 7:54 ` Hinko Kocevar
2008-07-09 11:38 ` Bernhard Fischer [this message]
2008-07-11 7:15 ` Hinko Kocevar
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=20080709113845.GB27321@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/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