Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] uClibc missing limits.h
Date: Thu, 3 Jul 2008 10:05:57 +0200	[thread overview]
Message-ID: <20080703080557.GA29943@mx.loc> (raw)
In-Reply-To: <486C7A22.8000604@cetrtapot.si>

On Thu, Jul 03, 2008 at 09:05:06AM +0200, Hinko Kocevar wrote:
>Ulf Samuelsson wrote:
>> 
>> 
>>> Hinko Kocevar wrote:
>>>> Bernhard Fischer wrote:
>>>>> On Mon, Jun 23, 2008 at 02:22:25PM +0200, Hinko Kocevar wrote:
>>>>>> 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).
>>>>> Well, that's not really correct since the default search path already
>>>>> should to be
>>>>> $target_triple/$ver/include \
>>>>> $target_triple/$ver/include-fixed \
>>>>>
>> 
>> Removing "-nostdinc" from CFLAGS in "uClibc-0.9.29/Rules.mak"
>> allows the ARM compilation to continue,
>
>But is this OK?

no.
>
>> but it again bombs since the function "testandset" has multiple
>> definitions.
>> Detected in libc_pthread_init.c and rpc_thread.c.
>> It is "first defined" in "forward.c"
>
>I guess this would be the problem in uClibc-0.9.29/libpthread/linuxthreads.old/sysdeps/arm/pt-machine.h.
>
>Dirty hack (works on cris arch), change:
># define PT_EI extern inline
>
>to
>
># define PT_EI static inline

Already fixed in svn trunk.

  reply	other threads:[~2008-07-03  8:05 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 [this message]
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=20080703080557.GA29943@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