+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>.
+
1998-03-24 Ulrich Drepper <drepper@cygnus.com>
* elf/ldsodesf.h: New file.
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.
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
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).
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.
-/* Copyright (C) 1991, 92, 93, 94, 95, 96, 97 Free Software Foundation, Inc.
+/* Copyright (C) 1991,92,93,94,95,96,97,98 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
#define _NETINET_IN_H 1
#include <features.h>
-#include <inttypes.h>
+#include <stdint.h>
#include <sys/socket.h>
#include <sys/types.h>
#endif
#define IN6_IS_ADDR_UNSPECIFIED(a) \
- ((((uint32_t *) (a))[0] == 0) && ((uint32_t *) (a))[1] == 0) && \
- (((uint32_t *) (a))[2] == 0) && ((uint32_t *) (a))[3] == 0))
+ (((uint32_t *) (a))[0] == 0 && ((uint32_t *) (a))[1] == 0 && \
+ ((uint32_t *) (a))[2] == 0 && ((uint32_t *) (a))[3] == 0)
#define IN6_IS_ADDR_LOOPBACK(a) \
- ((((uint32_t *) (a))[0] == 0) && ((uint32_t *) (a))[1] == 0) && \
- (((uint32_t *) (a))[2] == 0) && ((uint32_t *) (a))[3] == htonl (1)))
+ (((uint32_t *) (a))[0] == 0 && ((uint32_t *) (a))[1] == 0 && \
+ ((uint32_t *) (a))[2] == 0 && ((uint32_t *) (a))[3] == htonl (1))
#define IN6_IS_ADDR_MULTICAST(a) (((u_int8_t *) (a))[0] == 0xff)
-/* Copyright (C) 1992, 1994, 1997 Free Software Foundation, Inc.
+/* Copyright (C) 1992, 1994, 1997, 1998 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
int fd;
int level;
int optname;
- void *optval;
+ const void *optval;
size_t optlen;
{
error_t err = HURD_DPORT_USE (fd, __socket_setopt (port,