On 04/03/2010 11:13 AM, Natanael Copa wrote:
> which means that stdout ends up with the error indicator set for some
> reason. I suspect this is a bug in uclibc-nptl.
>
> Interestingly enough, redirecting stdout to a file made the build complete.
>
> Any ideas on how to trace this down?
Does thi
On Sun, Apr 4, 2010 at 4:42 PM, Austin Foxley wrote:
> On 04/03/2010 11:13 AM, Natanael Copa wrote:
>> which means that stdout ends up with the error indicator set for some
>> reason. I suspect this is a bug in uclibc-nptl.
>>
>> Interestingly enough, redirecting stdout to a file made the build co
_res is moved to .bss section with hidden attribute in 0.9.31. I get
around this issue by removing attribute_hidden.
libc/inet/resolv.c
/*struct __res_state _res __attribute__((section (".bss"))) attribute_hidden;*/
struct __res_state _res __attribute__((section (".bss")));
On Wed, Apr 7, 2010 a
On Sun, Apr 4, 2010 at 4:42 PM, Austin Foxley wrote:
> On 04/03/2010 11:13 AM, Natanael Copa wrote:
>> which means that stdout ends up with the error indicator set for some
>> reason. I suspect this is a bug in uclibc-nptl.
>>
>> Interestingly enough, redirecting stdout to a file made the build co
On Wed, Apr 7, 2010 at 11:04 AM, Natanael Copa wrote:
> On Sun, Apr 4, 2010 at 4:42 PM, Austin Foxley wrote:
>> On 04/03/2010 11:13 AM, Natanael Copa wrote:
>>> which means that stdout ends up with the error indicator set for some
>>> reason. I suspect this is a bug in uclibc-nptl.
>>>
>>> Intere
On Wed, Apr 7, 2010 at 11:34 AM, Natanael Copa wrote:
> On Wed, Apr 7, 2010 at 11:04 AM, Natanael Copa
> wrote:
>> On Sun, Apr 4, 2010 at 4:42 PM, Austin Foxley wrote:
>>> On 04/03/2010 11:13 AM, Natanael Copa wrote:
which means that stdout ends up with the error indicator set for some
>>>
> But I still get write error in the 0.9.31 and nptl environments.
>
> So I suppose I need to start bisect? scares me since i belive there
> are other broken stuff along the way..
feels like im talking to myself...
I started bisect
first commit that actually builds is
85ae389a56a20f0313001dcc433
On Wed, Apr 7, 2010 at 3:30 PM, Natanael Copa wrote:
> Let me see if i can dig deeper with some manualy patching
Ok, I have a rough estimate where the bug was introduced: between
3e8067a62725780222fa90f2945f1d5599a5cdd6 and
1a21daadde12abfbb148b0bf07b26fbb56aa410a
Last working commit was b13
On Wed, Apr 07, 2010 at 11:04:54AM +0200, Natanael Copa wrote:
>On Sun, Apr 4, 2010 at 4:42 PM, Austin Foxley wrote:
>> On 04/03/2010 11:13 AM, Natanael Copa wrote:
>>> which means that stdout ends up with the error indicator set for some
>>> reason. I suspect this is a bug in uclibc-nptl.
>>>
>>>
On Wed, Apr 7, 2010 at 11:20 PM, Bernhard Reutner-Fischer
wrote:
> On Wed, Apr 07, 2010 at 11:04:54AM +0200, Natanael Copa wrote:
>>On Sun, Apr 4, 2010 at 4:42 PM, Austin Foxley wrote:
>>> On 04/03/2010 11:13 AM, Natanael Copa wrote:
which means that stdout ends up with the error indicator s
On Wed, Apr 7, 2010 at 11:20 PM, Bernhard Reutner-Fischer
wrote:
> Does it still happen if you build master with LT_OLD and O0 (i.e. DODEBUG
> set)?
Enabling runtime assertions did give an interesting result:
make: libc/stdio/_stdio.c: 326: _stdio_validate_FILE: Assertion
`stream->__modeflags =
On Thu, Apr 8, 2010 at 8:40 AM, Natanael Copa wrote:
> On Wed, Apr 7, 2010 at 11:20 PM, Bernhard Reutner-Fischer
> wrote:
>> Does it still happen if you build master with LT_OLD and O0 (i.e. DODEBUG
>> set)?
>
> Enabling runtime assertions did give an interesting result:
>
> make: libc/stdio/_st
> -Original Message-
> From: uclibc-boun...@uclibc.org [mailto:uclibc-boun...@uclibc.org] On
> Behalf Of Natanael Copa
> Sent: den 9 april 2010 10:08
> To: Bernhard Reutner-Fischer
> Cc: uclibc@uclibc.org
> Subject: Re: problems with gnu make and stdout with uclibc np
Peter Kjellerstedt wrote:
Unless it has changed in the last years, there are no expressed
guarantees regarding API and ABI stability for the 0.x.y releases of
uClibc. AFAIK the stable API/ABI is intended for the 1.0.0 release.
And with the upcoming integration of the NPTL support, I do not see
2010/4/12 Timo Teräs :
> Peter Kjellerstedt wrote:
>>
>> Unless it has changed in the last years, there are no expressed guarantees
>> regarding API and ABI stability for the 0.x.y releases of uClibc. AFAIK the
>> stable API/ABI is intended for the 1.0.0 release. And with the upcoming
>> integratio
15 matches
Mail list logo