Re: fadvise gclibc vs uclibc

2008-09-09 Thread Bernhard Reutner-Fischer
Hi, On Mon, Sep 08, 2008 at 05:35:24PM -0400, Corinna Schultz wrote: >I noticed this difference between glibc and uclibc, in the fadvise >code (I'm trying to track down a bug on a ppc32 machine). > >Why the difference in the number of arguments? I don't know too much >about the system call mec

Re: reentrant functions

2008-09-09 Thread Bernhard Reutner-Fischer
On Sun, Jun 08, 2008 at 02:18:03PM +0200, Bernd Schmidt wrote: > Bernhard Fischer wrote: >> Just to make sure i understand correctly: >> >> - If a reentrant function exists then you want the non-reentrant func to >> be optional (via a central knob). >> - If non-reentrant funcs are off then they a

Re: fadvise gclibc vs uclibc

2008-09-09 Thread Carmelo AMOROSO
Bernhard Reutner-Fischer wrote: > Hi, > > On Mon, Sep 08, 2008 at 05:35:24PM -0400, Corinna Schultz wrote: >> I noticed this difference between glibc and uclibc, in the fadvise >> code (I'm trying to track down a bug on a ppc32 machine). >> >> Why the difference in the number of arguments? I don

Re: svn commit: trunk/uClibc/libc/stdio

2008-09-09 Thread Carmelo AMOROSO
Carmelo AMOROSO wrote: > Carmelo AMOROSO wrote: >> [EMAIL PROTECTED] wrote: >>> Author: vda >>> Date: 2008-04-09 12:51:18 -0700 (Wed, 09 Apr 2008) >>> New Revision: 21683 >>> >>> Log: >>> Factor out the core of vprintf() into separate function >>> vprintf_internal, so that: >>> * vprintf() does loc

Re: [PATCH] locale test fix.

2008-09-09 Thread Carmelo AMOROSO
Carmelo Amoroso wrote: > Bernhard Reutner-Fischer wrote: >> On Fri, Jul 11, 2008 at 02:12:51PM +0200, Carmelo AMOROSO wrote: >>> Filippo ARCIDIACONO wrote: Hi all, The following patch solve several locale multibyte tests failures. It has been tested and works fine. The patch ap

extern_inline macro [was: Re: svn commit: trunk/uClibc: include libc/sysdeps/linux/common/bits]

2008-09-09 Thread Bernhard Reutner-Fischer
On Tue, Sep 09, 2008 at 05:06:58AM -0700, [EMAIL PROTECTED] wrote: >Author: carmelo >Date: 2008-09-09 05:06:58 -0700 (Tue, 09 Sep 2008) >New Revision: 23365 > >Log: >Hush compiler for extern inline warnings by using >__extern_inline macro, this also makes gcc 4.3 happy. >(Taken from NPTL branch)

Re: extern_inline macro [was: Re: svn commit: trunk/uClibc: include libc/sysdeps/linux/common/bits]

2008-09-09 Thread Carmelo AMOROSO
Bernhard Reutner-Fischer wrote: > On Tue, Sep 09, 2008 at 05:06:58AM -0700, [EMAIL PROTECTED] wrote: >> Author: carmelo >> Date: 2008-09-09 05:06:58 -0700 (Tue, 09 Sep 2008) >> New Revision: 23365 >> >> Log: >> Hush compiler for extern inline warnings by using >> __extern_inline macro, this also m

uClibc-0.9.29 Compilation error for mips32

2008-09-09 Thread Gurminder
Hi, I tried compiling uClibc-0.9..29 for MIPS32 Big endian arch. Cross Compiler used - mips-linux-gcc 3.4.4 Host Distro - Fedora Core 4 Kernel Headers used = mips-linux-2.6.15 First Error I get is AS lib/crti.o libc/sysdeps/linux/mips/crti.S:109:2: invalid preprocessing directive #APP

Re: reentrant functions

2008-09-09 Thread Bernhard Reutner-Fischer
On Tue, Sep 09, 2008 at 12:45:39PM +0200, Bernhard Reutner-Fischer wrote: >On Sun, Jun 08, 2008 at 02:18:03PM +0200, Bernd Schmidt wrote: >> Bernhard Fischer wrote: >>> Just to make sure i understand correctly: >>> >>> - If a reentrant function exists then you want the non-reentrant func to >>> b

Re: "libc/stdlib/malloc/calloc.c: No such file or directory" with blackfin-toolchain-uclibc-default ([EMAIL PROTECTED])

2008-09-09 Thread Carmelo AMOROSO
gargs wrote: > Hi > > I am cross compiling a program that is known to work on various other > uClinux platforms, to target blackfin. > > When I compile using the blackfin-toolchain-uclibc-default > ([EMAIL PROTECTED]), and debug the code using gdb, before the segmentation > fault, I get num

Re: [PATCH] sh4: use optimized asm version of memcpy - add config option to support backward copying

2008-09-09 Thread Carmelo AMOROSO
Paul Mundt wrote: > On Mon, May 28, 2007 at 02:44:47PM +0200, Carmelo Amoroso wrote: >>> I've updated the previous patch to keep into account both suggestions >>> made by Mike and Paul. >>> A brief explanation of the changes follows: >>> >> did you have time to look at this ? >> >> If accepted, ma