Trouble with strerror_r

[Peter S. Mazinger]

On Mon, 12 Dec 2005, Joshua ChaitinPollak wrote:

> Hi,
> 
> I'm having trouble with strerror_r, specifically trying to compile  
> CommonCpp. I found someone having exactly the same problem over a  
> year ago, but when he wrote to the list he didn't get any responses:
> 
> http://www.uclibc.org/lists/uclibc/2004-November/010526.html
> 
> I'm compiling on x86, not arm, but the end result is the same:

build env? buildroot+ uClibc-0.9.28/svn ?

> 
> In file included from
> /home/buri/uclibc/gcc-3.3.x/toolchain_arm/arm-linux-uclibc/lib/../arm- 
> linux-uclibc/sys-include/sys/un.h:38,
>                    from ../include/cc++/config.h:731,

wonder about the include path cc++ ?

>                    from thread.cpp:41:
> /home/buri/uclibc/gcc-3.3.x/toolchain_arm/arm-linux-uclibc/lib/../arm- 
> linux-uclibc/sys-include/string.h:273:
> error: parse
>      error before `char'
> 
> The relevant line of string.h, 273, is:

I don't know which uClibc has it at that line, .28 (line 294) and svn (line 288)
If you are trying uClibc older than .28, retry first w/ .28

Peter

> 
> extern char *__REDIRECT (strerror_r,
>                            (int __errnum, char *__buf, size_t buflen)
> __THROW, _glibc_strerror_r);
> 
> And immediate above that spot it mentions uclibc.
> 
> Is this a uclibc bug, or a commoncpp bug, and how can I fix it?
> 
> Thanks for any help,
> 
> Josh
> 
> 
> 
> 

-- 
Peter S. Mazinger <ps dot m at gmx dot net>           ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08  BB6E C389 975E A5F0 59F2