This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: more cancellation work

From: Steven Munroe <sjmunroe at us dot ibm dot com>
To: libc-hacker <libc-hacker at sources dot redhat dot com>
Date: Thu, 17 Jul 2003 11:36:21 -0500
Subject: Re: more cancellation work
Organization: IBM Linux Developement
Reply-to: sjmunroe at vnet dot ibm dot com

Found that glibc cvs will not build -enable-add-ons=linuxthreads any more
because of cancelation changes made to misc/syslog.c 

syslog.c:238: warning: implicit declaration of function `__libc_cleanup_push'
syslog.c:238: warning: implicit declaration of function `__libc_cleanup_push'
syslog.c:238: warning: implicit declaration of function `__libc_cleanup_push'
/home/sjmunroe/work/build-23/libc.so.6: undefined reference to
`__libc_cleanup_push'
/home/sjmunroe/work/build-23/libc.so.6: undefined reference to
`__libc_cleanup_push'

the __libc_cleanup_push and __libc_cleanup_pop macros are defined in:

nptl/sysdeps/pthread/bits/libc-lock.h

but not in:

linuxthreads/sysdeps/pthread/bits/libc-lock.h

What is the intent for this? Should linuxthreads just noop these macros or are
there equalent cleanup function fo linuxthreads?


-- 
Steven Munroe
sjmunroe@us.ibm.com
Linux on PowerPC-64 Development
GLIBC for PowerPC-64 Development

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]