aboutsummaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1998-03-24 10:25:31 +0000
committerUlrich Drepper <drepper@redhat.com>1998-03-24 10:25:31 +0000
commit4d42000c41c216157909df3cd33bd6d1387b22ed (patch)
tree09a89a5c67616887c1a1b9b2672c64a17b6389e4 /FAQ.in
parenta853022cc32c8286018294e08cd4990ffcaf1d2b (diff)
downloadglibc-4d42000c41c216157909df3cd33bd6d1387b22ed.zip
glibc-4d42000c41c216157909df3cd33bd6d1387b22ed.tar.gz
glibc-4d42000c41c216157909df3cd33bd6d1387b22ed.tar.bz2
Update.
1998-03-22 NIIBE Yutaka <gniibe@mri.co.jp> * inet/netinet/in.h (IN6_IS_ADDR_UNSPECIFIED, IN6_IS_ADDR_LOOPBACK): Fix paren. 1998-03-24 Ulrich Drepper <drepper@cygnus.com> * sysdeps/mach/hurd/setsockopt.c (setsockopt): Make OPTVAL parameter const. Reported by UCHIYAMA Yasushi <uch@nop.or.jp>.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in21
1 files changed, 18 insertions, 3 deletions
diff --git a/FAQ.in b/FAQ.in
index bbfbe98..18ef198 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -556,7 +556,7 @@ ftp://ftp.kernel.org/pub/linux/utils/net/NIS/ypbind-3.3-glibc3.diff.
RPC: Unable to receive; errno = Connection refused" when using NIS.
{TK} You need a ypbind version which is 64bit clean. Some versions
-are not 64bit clean. A 64bit clean implemention is ypbind-mt. For
+are not 64bit clean. A 64bit clean implementation is ypbind-mt. For
ypbind 3.3, you need the patch from ftp.kernel.org (See the previous
question). I don't know about other versions.
@@ -624,7 +624,7 @@ problem.
2.8.1 (or more recent versions). libg++ 2.7.2 (and the Linux Versions
2.7.2.x) doesn't work very well with the GNU C library due to vtable thunks.
If you're upgrading from glibc 2.0.x to 2.1 you have to recompile
-libstc++ since the library compiled for 2.0 is not compatible due to the new
+libstdc++ since the library compiled for 2.0 is not compatible due to the new
Large File Support (LFS) in version 2.1.
? Source and binary incompatibilities, and what to do about them
@@ -869,7 +869,7 @@ to do so. For example constructs of the form:
enum {foo
#define foo foo
}
-are useful for debugging purpuses (you can use foo with your debugger
+are useful for debugging purposes (you can use foo with your debugger
that's why we need the enum) and for compatibility (other systems use
defines and check with #ifdef).
@@ -885,6 +885,21 @@ standards with feature flags).
The GNU C library is conforming to ANSI/ISO C - if and only if you're
only using the headers and library functions defined in the standard.
+?? I can't access some functions anymore. nm shows that they do
+ exist but linking fails nevertheless.
+
+{AJ} With the introduction of versioning in glibc 2.1 it is possible
+to export only those identifiers (functions, variables) that are
+really needed by application programs and by other parts of glibc.
+This way a lot of internal interfaces are now hidden. nm will still
+show those identifiers but marking them as internal. ISO C states
+that identifiers beginning with an underscore are internal to the
+libc. An application program normally shouldn't use those internal
+interfaces (there are exceptions, e.g. __ivaliduser). If a program
+uses these interfaces, it's broken. These internal interfaces might
+change between glibc releases or dropped completely.
+
+
? Miscellaneous
?? After I changed configure.in I get `Autoconf version X.Y.