RE: Linking with uClibc-0.9.32-rc3 on mipsel is sensitive to sharedlibraries link order

2011-04-14 Thread Filippo ARCIDIACONO
> -Original Message- > From: uclibc-boun...@uclibc.org > [mailto:uclibc-boun...@uclibc.org] On Behalf Of Maksim Rayskiy > Sent: Wednesday, April 13, 2011 11:07 PM > To: uclibc@uclibc.org > Subject: Linking with uClibc-0.9.32-rc3 on mipsel is > sensitive to sharedlibraries link order >

Re: Linking with uClibc-0.9.32-rc3 on mipsel is sensitive to shared libraries link order

2011-04-14 Thread Carmelo AMOROSO
On 4/13/2011 11:06 PM, Maksim Rayskiy wrote: > Hello, > > It has been reported against uClibc-0.9.32-rc1 that when linking an > executable with shared libraries on mipsel platform depending on the > order of the libraries in the linker command line you may end up with > an application which hangs

`utime(2)' marked as legacy under linux

2011-04-14 Thread Giuseppe Scrivano
Hello, AFAICS the use of `utime(2)' is discouraged under Linux and it is not even available unless UCLIBC_SUSV4_LEGACY is defined; in fact it is suggested to use `utimes(2)'. POSIX.1-2001 does the very opposite: `utimes(2)' is marked as legacy and it suggests use the use of `utime(2)' [1]. Am I

Re: `utime(2)' marked as legacy under linux

2011-04-14 Thread Peter Mazinger
IIRC SuSv4 changed it's opinion and removed legacy from it Peter Original-Nachricht > Datum: Thu, 14 Apr 2011 16:00:20 +0200 > Von: Giuseppe Scrivano > An: uclibc@uclibc.org > Betreff: `utime(2)\' marked as legacy under linux > Hello, > > AFAICS the use of `utime(2)' is discou

Re: `utime(2)' marked as legacy under linux

2011-04-14 Thread Bernhard Reutner-Fischer
Giuseppe Scrivano wrote: Hello, AFAICS the use of `utime(2)' is discouraged under Linux and it is not even available unless UCLIBC_SUSV4_LEGACY is defined; in fact it is suggested to use `utimes(2)'. POSIX.1-2001 does the very opposite: `utimes(2)' is marked as legacy and it suggests use the u

Re: [git commit] resolv: fix res_close not to hang with ipv6

2011-04-14 Thread Bernhard Reutner-Fischer
Carmelo Amoroso wrote: >On 13/04/11 10:26, Bernhard Reutner-Fischer wrote: >> >Just noted that the git commit subject does not specifies he head >(master,prelink, future etc) as before. >It was a nice feature. Hm, master was never prefixed as opposed to branches. Are you sure that this does n

Re: `utime(2)' marked as legacy under linux

2011-04-14 Thread Giuseppe Scrivano
Thanks for your comments. Is the following patch ok? Cheers, Giuseppe >From f9b2362086445622536d6521dccd236175121899 Mon Sep 17 00:00:00 2001 From: Giuseppe Scrivano Date: Thu, 14 Apr 2011 17:44:23 +0200 Subject: [PATCH] utime: do not mark as obsolescent. --- Makefile.in

Re: Linking with uClibc-0.9.32-rc3 on mipsel is sensitive to shared libraries link order

2011-04-14 Thread Maksim Rayskiy
Carmelo, The test case is quite simple. The following code #include #include int main(int argc, char *argv[]) { pthread_cond_t cond; printf("begin\n"); pthread_cond_init(&cond, NULL); printf("end\n"); return 0; } Works when compiled as: mipsel-linux-

RE: patch to fix build issue in uClibc testsuite

2011-04-14 Thread Jian Peng
Thank you, Bernhard. I came across a discussion on similar issue at http://www.mail-archive.com/uclibc@uclibc.org/msg04245.html I like to understand what is the purpose of $(KERNEL_HEADERS). In my case, KERNEL_HEADERS was used to point to what my own kernel header files (may be slightly differ