Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/glibc/ports-2.12.1/200-fadvise64_64.patch
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Dec 27 12:45:22 2012 +0100 (2012-12-27)
changeset 3152 b286c7993be5
permissions -rw-r--r--
scripts/addToolsVersion: properly handle .in vs. .in.2

While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).

Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.

So, for each tool, we need to explicitly know what file to munge.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> 
     1 ripped from Debian

     2 

     3  sysdeps/unix/sysv/linux/posix_fadvise.c |   13 +++++++++++++

     4  1 file changed, 13 insertions(+)

     5 

     6 diff -durN glibc-2.12.1.orig/sysdeps/unix/sysv/linux/posix_fadvise.c glibc-2.12.1/sysdeps/unix/sysv/linux/posix_fadvise.c

     7 --- glibc-2.12.1.orig/sysdeps/unix/sysv/linux/posix_fadvise.c	2003-08-17 02:36:22.000000000 +0200

     8 +++ glibc-2.12.1/sysdeps/unix/sysv/linux/posix_fadvise.c	2009-11-13 00:50:03.000000000 +0100

     9 @@ -35,6 +35,19 @@

    10      return INTERNAL_SYSCALL_ERRNO (ret, err);

    11    return 0;

    12  #else

    13 +# ifdef __NR_fadvise64_64

    14 +  INTERNAL_SYSCALL_DECL (err);  

    15 +  int ret = INTERNAL_SYSCALL (fadvise64_64, err, 6, fd,

    16 +			      __LONG_LONG_PAIR ((long) (offset >> 31),

    17 +						(long) offset),

    18 +			      __LONG_LONG_PAIR ((long) (len >> 31),

    19 +						(long) len),

    20 +			      advise);

    21 +  if (INTERNAL_SYSCALL_ERROR_P (ret, err))

    22 +    return INTERNAL_SYSCALL_ERRNO (ret, err);

    23 +  return 0;

    24 +# else

    25    return ENOSYS;

    26 +# endif

    27  #endif

    28  }
crosstool-ng