Bug#948396: New glibc broke existing app due to historic stack alignment

2020-01-08 Thread Petr Vandrovec
Florian Weimer wrote on 1/7/2020 9:31 PM: * Petr Vandrovec: As far as I can tell, while x86-64 ABI requires stack to be aligned on entry to the functions, x86 ABI does not have any such requirement, and so glibc should align stack itself if it wants to use XMM instructions that require aligned

Bug#948396: New glibc broke existing app due to historic stack alignment

2020-01-07 Thread Petr Vandrovec
Package: libc6-i386 Version: 2.29-8 Since updating my system today our build system binaries started crashing. Upon further investigation problem is that __mktime_internal code in libc6-i386 now started using 'movaps' instruction without aligning stack on 16 byte boundary. As far as I can tell,

Bug#533067: libc6-dev-i386 broken?

2009-06-15 Thread Petr Vandrovec
Aurelien Jarno wrote: There is no bug in libc6-dev-i386. In that case where are i386 libraries? libc6-dev-i386 contains only headers, so all attempts to build anything fail due to missing libc_nonshared.a, libc.so, libm.so, and others: gwy:/# dpkg -L libc6-dev-i386 /. /usr /usr/share

Bug#519774: libc6: causes many programs not to be able to resolve dns addresses

2009-03-15 Thread Petr Vandrovec
Hello, it seems that DNS resolver is grossly confused, and sends two DNS requests on same socket back to back (strace below is from 'lynx http://www.jeep.com'). In first one DNS server responded only to second packet sent by resolver, and resolve failed (after that mdns was tried, and

Recompiling libc6-2.1.3 with linux-2.4.x headers

2000-07-20 Thread Petr Vandrovec
. Thanks, Petr Vandrovec [EMAIL PROTECTED]