AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2024-12-22 02:40:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update.

Browse Source 
1998-04-21  Ulrich Drepper  <drepper@cygnus.com>

	* ptlongjmp.c: Add prorotypes for __libc_siglongjmp and
	__libc_longjmp.
This commit is contained in:
Ulrich Drepper 1998-04-21 09:43:11 +00:00
parent 8619129f3f
commit f12944ec15
5 changed files with 765 additions and 729 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

743
FAQ
View File

File diff suppressed because it is too large Load Diff

716
FAQ.in
View File

File diff suppressed because it is too large Load Diff

5
linuxthreads/ChangeLog
View File

@ -1,3 +1,8 @@
1998-04-21 Ulrich Drepper <drepper@cygnus.com>
* ptlongjmp.c: Add prorotypes for __libc_siglongjmp and
__libc_longjmp.
1998-04-20 14:55 Ulrich Drepper <drepper@cygnus.com>
* Makefile (libpthread-routines): Add ptlongjmp and spinlock.

8
linuxthreads/ptlongjmp.c
View File

@ -19,6 +19,14 @@
#include "pthread.h"
#include "internals.h"
/* These functions are not declared anywhere since they shouldn't be
used at another place but here. */
extern void __libc_siglongjmp (sigjmp_buf env, int val)
__attribute__ ((noreturn));
extern void __libc_longjmp (sigjmp_buf env, int val)
__attribute__ ((noreturn));
static void pthread_cleanup_upto(__jmp_buf target)
{
pthread_descr self = thread_self();

22
manual/install.texi
View File

@ -103,6 +103,20 @@ sources. To use them, unpack them into your source tree, and give
If you do not wish to use some add-on package that you have present in
your source tree, give this option a list of the add-ons that you
@emph{do} want used, like this: @samp{--enable-add-ons=crypt,linuxthreads}
@item --with-headers=DIRECTORY
Search only DIRECTORY and the C compiler's private directory for header
files not found in the libc sources. @file{/usr/include} will not be
searched if this option is given. On Linux, DIRECTORY should be the
kernel's private include directory (usually
@file{/usr/src/linux/include}).
This option is primarily of use on a system where the headers in
@file{/usr/include} come from an older version of glibc. Conflicts can
occasionally happen in this case. Note that Linux libc5 qualifies as an
older version of glibc. You can also use this option if you want to
compile glibc with a newer set of kernel headers than the ones found in
@file{/usr/include}.
@end table
You should not build the library in the same directory as the sources,
@ -150,12 +164,18 @@ Some of the machine-dependent code for some machines uses extensions in
the GNU C compiler, so you may need to compile the library with GCC.
(In fact, all of the existing complete ports require GCC.)
To build the library and related programs, type @code{make}. This will
produce a lot of output, some of which may look like errors from
@code{make} (but isn't). Look for error messages from @code{make}
containing @samp{***}. Those indicate that something is really wrong.
The compilation process takes several hours even on fast hardware;
expect at least two hours for the default configuration on i586 for
Linux. For Hurd times are much longer. All current releases of GCC
have a problem which causes them to take several minutes to compile
certain files in the iconvdata directory. Do not panic if the compiler
appears to hang.
To build and run some test programs which exercise some of the library
facilities, type @code{make check}. This will produce several files
with names like @file{@var{program}.out}.