OpenE2K/glibc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

* include/libc-symbols.h: Fix comment typo.

Browse Source 
From Peter Kjellerstedt <peter.kjellerstedt@axis.com>.
This commit is contained in:
Roland McGrath 2006-02-24 03:27:16 +00:00
parent 0f289b2a11
commit 5536dfcbb8
2 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
ChangeLog
View File

@ -1,5 +1,8 @@
2006-02-23 Roland McGrath <roland@redhat.com>
* include/libc-symbols.h: Fix comment typo.
From Peter Kjellerstedt <peter.kjellerstedt@axis.com>.
* sysdeps/unix/sysv/linux/i386/fchownat.c: Diddle code so that "fail"
label is always used.

7
include/libc-symbols.h
View File

@ -1,6 +1,7 @@
/* Support macros for making weak and strong aliases for symbols,
and for using symbol sets and linker warnings with GNU ld.
Copyright (C) 1995-1998,2000-2003,2004, 2005 Free Software Foundation, Inc.
Copyright (C) 1995-1998,2000-2003,2004,2005,2006
Free Software Foundation, Inc.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
@ -502,7 +503,7 @@ for linking")
}
libc_hidden_weak (foo)
Simularly for global data. If references to foo within libc.so should
Similarly for global data. If references to foo within libc.so should
always go to foo defined in libc.so, then in include/foo.h you add:
libc_hidden_proto (foo)
@ -517,7 +518,7 @@ for linking")
int foo = INITIAL_FOO_VALUE;
libc_hidden_data_weak (foo)
If foo is normally just an alias (strong or weak) of some other function,
If foo is normally just an alias (strong or weak) to some other function,
you should use the normal strong_alias first, then add libc_hidden_def
or libc_hidden_weak: