about summary refs log tree commit diff
path: root/ports/ChangeLog
Commit message (Collapse)AuthorAgeFilesLines
* rename configure.in to configure.acMike Frysinger2013-10-301-0/+5
| | | | | | | Autoconf has been deprecating configure.in for quite a long time. Rename all our configure.in and preconfigure.in files to .ac. Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* Move entries to correct port ChangeLog files.Joseph Myers2013-10-181-11/+0
|
* fix changelog dateAlan Modra2013-10-041-1/+1
|
* PowerPC floating point little-endian [1 of 15]Alan Modra2013-10-041-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | http://sourceware.org/ml/libc-alpha/2013-08/msg00081.html This is the first of a series of patches to ban ieee854_long_double and the ieee854_long_double macros when using IBM long double. union ieee854_long_double just isn't correct for IBM long double, especially when little-endian, and pretending it is OK has allowed a number of bugs to remain undetected in sysdeps/ieee754/ldbl-128ibm/. This changes the few places in generic code that use it. * stdio-common/printf_size.c (__printf_size): Don't use union ieee854_long_double in fpnum union. * stdio-common/printf_fphex.c (__printf_fphex): Likewise. Use signbit macro to retrieve sign from long double. * stdio-common/printf_fp.c (___printf_fp): Use signbit macro to retrieve sign from long double. * sysdeps/ieee754/ldbl-128ibm/printf_fphex.c: Adjust for fpnum change. * sysdeps/ieee754/ldbl-128/printf_fphex.c: Likewise. * sysdeps/ieee754/ldbl-96/printf_fphex.c: Likewise. * sysdeps/x86_64/fpu/printf_fphex.c: Likewise. * math/test-misc.c (main): Don't use union ieee854_long_double. ports/ * sysdeps/ia64/fpu/printf_fphex.c: Adjust for fpnum change.
* hppa: add fanotify_markMike Frysinger2013-09-021-0/+7
| | | | | | | | | | | | | | | | | | | Another example of all the 64bit arches getting the definition via a common file, but the 32bit ones all adding it by themselves and hppa was missed. I'm not entirely sure about the usage of GLIBC_2.19 symbols here. We'd like to backport this so people can use it, but it means we'd be releasing a glibc-2.17/glibc-2.18 with a GLIBC_2.19 symbol in it. But maybe it won't be a big deal since you'd only get that 2.19 ref if you actually used the symbol ? There hasn't been a glibc release where hppa worked w/out a bunch of patches, so in reality there's only two distros that matter -- Gentoo and Debian. Reported-by: Jeroen Roovers <jer@gentoo.org> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
* Update miscellaneous copyright dates.Joseph Myers2013-01-021-0/+4
|
* Change sources.redhat.com references to sourceware.org.Joseph Myers2012-12-061-1/+7
|
* Ports-related README updates.Joseph Myers2012-12-051-0/+3
|
* Split my last ChangeLog entry into respective arch-specific filesSiddhesh Poyarekar2012-10-021-11/+0
|
* Fix clone flag name in comment to CLONE_CHILD_CLEARTID.Siddhesh Poyarekar2012-10-021-0/+11
|
* Remove ports files no longer relevant now included in libc repository.Joseph Myers2012-07-031-0/+6
|
* Move all files into ports/ subdirectory in preparation for merge with glibc glibc-2.16-ports-before-mergeJoseph Myers2012-07-011-0/+73