AuroraMiddleware/glibc
1
0
Fork 0
mirror of https://sourceware.org/git/glibc.git synced 2025-01-03 00:10:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update.

Browse Source 
1999-07-25  Jakub Jelinek  <jj@ultra.linux.cz>

	* sysdeps/sparc/sparc32/sparcv8/Makefile: -mv8 is deprecated, use
	-mcpu=v8.
	* sysdeps/sparc/sparc32/sparcv9/Makefile: Likewise.
	* sysdeps/sparc/sparc64/Makefile: Make %g7 register available for
	libc's private use (as assembly routine clobber it anyway).

1999-07-26  Andreas Jaeger  <aj@arthur.rhein-neckar.de>

	* README.template (configurations): The crypt add-on has a new
	ftp site.
	* manual/install.texi (Installation): Likewise.
This commit is contained in:
Ulrich Drepper 1999-07-27 02:07:01 +00:00
parent 252ff6b676
commit f05f5ca385
10 changed files with 57 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
ChangeLog
View File

@ -1,3 +1,17 @@
1999-07-25 Jakub Jelinek <jj@ultra.linux.cz>
* sysdeps/sparc/sparc32/sparcv8/Makefile: -mv8 is deprecated, use
-mcpu=v8.
* sysdeps/sparc/sparc32/sparcv9/Makefile: Likewise.
* sysdeps/sparc/sparc64/Makefile: Make %g7 register available for
libc's private use (as assembly routine clobber it anyway).
1999-07-26 Andreas Jaeger <aj@arthur.rhein-neckar.de>
* README.template (configurations): The crypt add-on has a new
ftp site.
* manual/install.texi (Installation): Likewise.
1999-07-26 Ulrich Drepper <drepper@cygnus.com> 1999-07-26 Ulrich Drepper <drepper@cygnus.com>
* time/time.h: Add forward for struct sigevent. Unix98 maybe * time/time.h: Add forward for struct sigevent. Unix98 maybe

4
FAQ
View File

@ -640,8 +640,8 @@ functions together with glibc.
The functions are available, as an add-on (see question 1.11). People in the US The functions are available, as an add-on (see question 1.11). People in the US
may get it from the same place they got GNU libc from. People outside the may get it from the same place they got GNU libc from. People outside the
US should get the code from ftp.funet.fi [128.214.248.6] in the directory US should get the code from ftp.gwdg.de [134.76.11.100] in the directory
pub/gnu/funet, or another archive site outside the USA. The README explains pub/linux/glibc, or another archive site outside the USA. The README explains
how to install the sources. how to install the sources.
If you already have the crypt code on your system the reason for the failure If you already have the crypt code on your system the reason for the failure

4
FAQ.in
View File

@ -458,8 +458,8 @@ functions together with glibc.
The functions are available, as an add-on (see ?addon). People in the US The functions are available, as an add-on (see ?addon). People in the US
may get it from the same place they got GNU libc from. People outside the may get it from the same place they got GNU libc from. People outside the
US should get the code from ftp.funet.fi [128.214.248.6] in the directory US should get the code from ftp.gwdg.de [134.76.11.100] in the directory
pub/gnu/funet, or another archive site outside the USA. The README explains pub/linux/glibc, or another archive site outside the USA. The README explains
how to install the sources. how to install the sources.
If you already have the crypt code on your system the reason for the failure If you already have the crypt code on your system the reason for the failure

50
INSTALL
View File

@ -20,9 +20,10 @@ change in the future. Get it from the same place you got the main
bundle; the file is `glibc-linuxthreads-VERSION.tar.gz'. Support for bundle; the file is `glibc-linuxthreads-VERSION.tar.gz'. Support for
the `crypt' function is distributed separately because of United States the `crypt' function is distributed separately because of United States
export restrictions. If you are outside the US or Canada, you must get export restrictions. If you are outside the US or Canada, you must get
`crypt' support from a site outside the US, such as `ftp.ifi.uio.no'. `crypt' support from a site outside the US, such as `ftp.gwdg.de'.
(Most non-US mirrors of `ftp.gnu.org' will have it too.) The file you `ftp.gwdg.de' has the crypt distribution in `pub/linux/glibc'. (Most
need is `glibc-crypt-VERSION.tar.gz'. non-US mirrors of `ftp.gnu.org' will have it too.) The file you need
is `glibc-crypt-VERSION.tar.gz'.
You will need recent versions of several GNU tools: definitely GCC You will need recent versions of several GNU tools: definitely GCC
and GNU Make, and possibly others. *Note Tools for Compilation::, and GNU Make, and possibly others. *Note Tools for Compilation::,
@ -41,6 +42,10 @@ at the top level of the source tree. In the scenario above, you'd type
$ ../glibc-2.1.0/configure ARGS... $ ../glibc-2.1.0/configure ARGS...
Please note that even if you're building in a separate build
directory, the compiliation needs to modify a few files in the source
directory, especially some files in the manual subdirectory.
`configure' takes many options, but you can get away with knowing only `configure' takes many options, but you can get away with knowing only
two: `--prefix' and `--enable-add-ons'. The `--prefix' option tells two: `--prefix' and `--enable-add-ons'. The `--prefix' option tells
configure where you want glibc installed. This defaults to configure where you want glibc installed. This defaults to
@ -82,7 +87,7 @@ will be used, and CFLAGS sets optimization options for the compiler.
given with no list, it enables all the add-on packages it finds. given with no list, it enables all the add-on packages it finds.
If you do not wish to use some add-on package that you have 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 present in your source tree, give this option a list of the
add-ons that you _do_ want used, like this: add-ons that you *do* want used, like this:
`--enable-add-ons=crypt,linuxthreads' `--enable-add-ons=crypt,linuxthreads'
`--with-binutils=DIRECTORY' `--with-binutils=DIRECTORY'
@ -98,10 +103,6 @@ will be used, and CFLAGS sets optimization options for the compiler.
Use this option if your computer lacks hardware floating-point Use this option if your computer lacks hardware floating-point
support and your operating system does not emulate an FPU. support and your operating system does not emulate an FPU.
`--disable-static'
Don't build static libraries. Static libraries aren't that useful
these days, but we recommend you build them in case you need them.
`--disable-shared' `--disable-shared'
Don't build shared libraries even if we could. Not all systems Don't build shared libraries even if we could. Not all systems
support shared libraries; you need ELF support and (currently) the support shared libraries; you need ELF support and (currently) the
@ -168,7 +169,11 @@ Instead, edit the generated `Makefile' and uncomment the line
# PARALLELMFLAGS = -j 4 # PARALLELMFLAGS = -j 4
You can change the `4' to some other number as appropriate for your You can change the `4' to some other number as appropriate for your
system. system. Instead of changing the `Makefile', you could give this option
directly to `make' and call it as, e.g. `make PARALLELMFLAGS=-j4'. If
you're building in the source directory, you've got to use the latter
approach since in this case no new `Makefile' is generated which you
can change.
To build and run some test programs which exercise some of the To build and run some test programs which exercise some of the
library facilities, type `make check'. This should complete library facilities, type `make check'. This should complete
@ -202,10 +207,10 @@ or you will end up with a mixture of header files from both libraries,
and you won't be able to compile anything. You may also need to and you won't be able to compile anything. You may also need to
reconfigure GCC to work with the new library. The easiest way to do reconfigure GCC to work with the new library. The easiest way to do
that is to figure out the compiler switches to make it work again that is to figure out the compiler switches to make it work again
(`-Wl,-dynamic-linker=/lib/ld-linux.so.2' should work on Linux systems) (`-Wl,--dynamic-linker=/lib/ld-linux.so.2' should work on Linux
and use them to recompile gcc. You can also edit the specs file systems) and use them to recompile gcc. You can also edit the specs
(`/usr/lib/gcc-lib/TARGET/VERSION/specs'), but that is a bit of a black file (`/usr/lib/gcc-lib/TARGET/VERSION/specs'), but that is a bit of a
art. black art.
You can install glibc somewhere other than where you configured it You can install glibc somewhere other than where you configured it
to go by setting the `install_root' variable on the command line for to go by setting the `install_root' variable on the command line for
@ -299,14 +304,14 @@ build the GNU C library:
Perl is not required, but it is used if present to test the Perl is not required, but it is used if present to test the
installation. We may decide to use it elsewhere in the future. installation. We may decide to use it elsewhere in the future.
If you change any of the `configure.in' files you will also need If you change any of the `configure.in' files you will also need
* GNU `autoconf' 2.12 or higher * GNU `autoconf' 2.12 or higher
and if you change any of the message translation files you will need and if you change any of the message translation files you will need
* GNU `gettext' 0.10.35 or later * GNU `gettext' 0.10.35 or later (version 0.10.35 is a alpha release
and available via ftp from alpha.gnu.org/gnu)
You may also need these packages if you upgrade your source tree using You may also need these packages if you upgrade your source tree using
patches, although we try to avoid this. patches, although we try to avoid this.
@ -402,7 +407,7 @@ installed there.
library on your system against the new library for the sake of new code, library on your system against the new library for the sake of new code,
but keep the old libraries around for old binaries to use. This is but keep the old libraries around for old binaries to use. This is
complicated and difficult. Consult the Glibc2 HOWTO at complicated and difficult. Consult the Glibc2 HOWTO at
<http://www.imaxx.net/~thrytis/glibc> for details. `http://www.imaxx.net/~thrytis/glibc' for details.
You cannot use `nscd' with 2.0 kernels, due to bugs in the You cannot use `nscd' with 2.0 kernels, due to bugs in the
kernel-side thread support. `nscd' happens to hit these bugs kernel-side thread support. `nscd' happens to hit these bugs
@ -417,6 +422,13 @@ errors and omissions in this manual. If you report them, they will get
fixed. If you don't, no one will ever know about them and they will fixed. If you don't, no one will ever know about them and they will
remain unfixed for all eternity, if not longer. remain unfixed for all eternity, if not longer.
It is a good idea to check first that the problem was not reported
before. Bugs are documented in two places: The file `BUGS' describes a
number of well known bugs and the bug tracking system has a WWW
interface at `http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl'. The
WWW interface gives you access to open and closed reports. The closed
reports normally include a patch or a hint on solving the problem.
To report a bug, first you must find it. Hopefully, this will be the To report a bug, first you must find it. Hopefully, this will be the
hard part. Once you've found a bug, make sure it's really a bug. A hard part. Once you've found a bug, make sure it's really a bug. A
good way to do this is to see if the GNU C library behaves the same way good way to do this is to see if the GNU C library behaves the same way
@ -441,9 +453,9 @@ you haven't installed it, will be in your build directory. Send your
test case, the results you got, the results you expected, and what you test case, the results you got, the results you expected, and what you
think the problem might be (if you've thought of anything). `glibcbug' think the problem might be (if you've thought of anything). `glibcbug'
will insert the configuration information we need to see, and ship the will insert the configuration information we need to see, and ship the
report off to <bug-glibc@gnu.org>. Don't send a message there report off to <bugs@gnu.org>. Don't send a message there directly; it
directly; it is fed to a program that expects mail to be formatted in a is fed to a program that expects mail to be formatted in a particular
particular way. Use the script. way. Use the script.
If you are not sure how a function should behave, and this manual If you are not sure how a function should behave, and this manual
doesn't tell you, that's a bug in the manual. Report that too! If the doesn't tell you, that's a bug in the manual. Report that too! If the

4
README.template
View File

@ -57,10 +57,10 @@ for crypt; it is called `glibc-crypt-VERSION.tar.gz'. You can just
unpack the crypt distribution along with the rest of the C library and unpack the crypt distribution along with the rest of the C library and
build; you can also build the library without getting crypt. Users build; you can also build the library without getting crypt. Users
outside the USA can get the crypt distribution via anonymous FTP from outside the USA can get the crypt distribution via anonymous FTP from
ftp.funet.fi [128.214.248.6] in the directory pub/gnu/funet, or ftp.gwdg.de [134.76.11.100] in the directory pub/linux/glibc, or
another archive site outside the USA. Archive maintainers are another archive site outside the USA. Archive maintainers are
encouraged to copy this distribution to their archives outside the encouraged to copy this distribution to their archives outside the
USA. Please get it from ftp.funet.fi; transferring this distribution USA. Please get it from ftp.gwdg.de; transferring this distribution
from ftp.gnu.org (or any other site in the USA) to a site outside the from ftp.gnu.org (or any other site in the USA) to a site outside the
USA is in violation of US export laws. USA is in violation of US export laws.

3
manual/install.texi
View File

@ -26,7 +26,8 @@ bundle; the file is @file{glibc-linuxthreads-@var{VERSION}.tar.gz}.
Support for the @code{crypt} function is distributed separately because Support for the @code{crypt} function is distributed separately because
of United States export restrictions. If you are outside the US or of United States export restrictions. If you are outside the US or
Canada, you must get @code{crypt} support from a site outside the US, Canada, you must get @code{crypt} support from a site outside the US,
such as @samp{ftp.ifi.uio.no}. such as @samp{ftp.gwdg.de}. @samp{ftp.gwdg.de} has the crypt
distribution in @code{pub/linux/glibc}.
@c Check this please someone: @c Check this please someone:
(Most non-US mirrors of @samp{ftp.gnu.org} will have it too.) The file (Most non-US mirrors of @samp{ftp.gnu.org} will have it too.) The file
you need is @file{glibc-crypt-@var{VERSION}.tar.gz}. you need is @file{glibc-crypt-@var{VERSION}.tar.gz}.

2
sysdeps/sparc/sparc32/sparcv8/Makefile
View File

@ -1 +1 @@
sysdep-CFLAGS += -mv8 sysdep-CFLAGS += -mcpu=v8

2
sysdeps/sparc/sparc32/sparcv9/Makefile
View File

@ -1,4 +1,4 @@
sysdep-CFLAGS += -mv8 -mtune=ultrasparc -Wa,-Av9a sysdep-CFLAGS += -mcpu=v8 -mtune=ultrasparc -Wa,-Av9a
ifeq ($(subst gnulib,string,$(subdir)),string) ifeq ($(subst gnulib,string,$(subdir)),string)
ASFLAGS-.o += -Wa,-Av9a ASFLAGS-.o += -Wa,-Av9a

1
sysdeps/sparc/sparc64/Makefile
View File

@ -1,2 +1,3 @@
# The Sparc `long double' is a distinct type we support. # The Sparc `long double' is a distinct type we support.
long-double-fcts = yes long-double-fcts = yes
sysdep-CFLAGS += -fcall-used-g7

2
time/Makefile
View File

@ -29,7 +29,7 @@ routines := offtime asctime clock ctime ctime_r difftime \
tzfile getitimer setitimer \ tzfile getitimer setitimer \
stime dysize timegm ftime \ stime dysize timegm ftime \
strptime getdate wcsftime \ strptime getdate wcsftime \
clock_getres clock_gettime clock_setres \ clock_getres clock_gettime clock_settime \
timer_create timer_delete timer_getoverr \ timer_create timer_delete timer_getoverr \
timer_gettime timer_settime timer_gettime timer_settime