All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc missing limits.h
Date: Mon, 23 Jun 2008 14:22:25 +0200	[thread overview]
Message-ID: <485F9581.2040204@cetrtapot.si> (raw)

Hi,

I've found a way for uClibc to find headers that are not in the $(shell $CC -print-file-name=include), but in $(shell $CC -print-file-name=include)-fixed.
According to http://sourceware.org/ml/libc-alpha/2007-03/msg00017.html LIBC should also look in other gcc provided header directories (eg. include-fixed) instead only relying on 'include' to contain all correct headers.

Below is uClibc patch for this (tested on cris).

Best regards,
Hinko
-- 
?ETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar at cetrtapot.si
Http: www.cetrtapot.si

-------------- next part --------------
A non-text attachment was scrubbed...
Name: uClibc-0.9.29-use-gcc-include-fixed-dir.patch
Type: text/x-patch
Size: 461 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080623/85c66671/attachment.bin 

             reply	other threads:[~2008-06-23 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 12:22 Hinko Kocevar [this message]
2008-06-23 13:16 ` [Buildroot] uClibc missing limits.h 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
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=485F9581.2040204@cetrtapot.si \
    --to=hinko.kocevar@cetrtapot.si \
    --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 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.