summaryrefslogtreecommitdiffstats
path: root/src/kmk/README.template
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-11 08:21:29 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-11 08:21:29 +0000
commit29cd838eab01ed7110f3ccb2e8c6a35c8a31dbcc (patch)
tree63ef546b10a81d461e5cf5ed9e98a68cd7dee1aa /src/kmk/README.template
parentInitial commit. (diff)
downloadkbuild-29cd838eab01ed7110f3ccb2e8c6a35c8a31dbcc.tar.xz
kbuild-29cd838eab01ed7110f3ccb2e8c6a35c8a31dbcc.zip
Adding upstream version 1:0.1.9998svn3589+dfsg.upstream/1%0.1.9998svn3589+dfsg
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'src/kmk/README.template')
-rw-r--r--src/kmk/README.template178
1 files changed, 178 insertions, 0 deletions
diff --git a/src/kmk/README.template b/src/kmk/README.template
new file mode 100644
index 0000000..7739faa
--- /dev/null
+++ b/src/kmk/README.template
@@ -0,0 +1,178 @@
+This directory contains the %VERSION% release of GNU Make.
+
+See the file NEWS for the user-visible changes from previous releases.
+In addition, there have been bugs fixed.
+
+Please check the system-specific notes below for any caveats related to
+your operating system.
+
+For general building and installation instructions, see the file INSTALL.
+
+If you need to build GNU Make and have no other 'make' program to use,
+you can use the shell script 'build.sh' instead. To do this, first run
+'configure' as described in INSTALL. Then, instead of typing 'make' to
+build the program, type 'sh build.sh'. This should compile the program
+in the current directory. Then you will have a Make program that you can
+use for './make install', or whatever else.
+
+Some systems' Make programs are broken and cannot process the Makefile for
+GNU Make. If you get errors from your system's Make when building GNU
+Make, try using 'build.sh' instead.
+
+
+GNU Make is free software. See the file COPYING for copying conditions.
+GNU Make is copyright by the Free Software Foundation. Copyright notices
+condense sequential years into a range; e.g. "1987-1994" means all years
+from 1987 to 1994 inclusive.
+
+Downloading
+-----------
+
+GNU Make can be obtained in many different ways. See a description here:
+
+ http://www.gnu.org/software/software.html
+
+
+Documentation
+-------------
+
+GNU make is fully documented in the GNU Make manual, which is contained
+in this distribution as the file make.texinfo. You can also find
+on-line and preformatted (PostScript and DVI) versions at the FSF's web
+site. There is information there about ordering hardcopy documentation.
+
+ http://www.gnu.org/
+ http://www.gnu.org/doc/doc.html
+ http://www.gnu.org/manual/manual.html
+
+
+Development
+-----------
+
+GNU Make development is hosted by Savannah, the FSF's online development
+management tool. Savannah is here:
+
+ http://savannah.gnu.org
+
+And the GNU Make development page is here:
+
+ http://savannah.gnu.org/projects/make/
+
+You can find most information concerning the development of GNU Make at
+this site.
+
+
+Bug Reporting
+-------------
+
+You can send GNU make bug reports to <bug-make@gnu.org>. Please see the
+section of the GNU make manual entitled 'Problems and Bugs' for
+information on submitting useful and complete bug reports.
+
+You can also use the online bug tracking system in the Savannah GNU Make
+project to submit new problem reports or search for existing ones:
+
+ http://savannah.gnu.org/bugs/?group=make
+
+If you need help using GNU make, try these forums:
+
+ help-make@gnu.org
+ help-utils@gnu.org
+ news:gnu.utils.help
+ news:gnu.utils.bug
+
+
+Git Access
+----------
+
+The GNU make source repository is available via Git from the
+GNU Savannah Git server; look here for details:
+
+ http://savannah.gnu.org/git/?group=make
+
+Please note: you won't be able to build GNU make from Git without
+installing appropriate maintainer's tools, such as GNU m4, automake,
+autoconf, Perl, GNU make, and GCC. See the README.git file for hints on
+how to build GNU make once these tools are available. We make no
+guarantees about the contents or quality of the latest code in the Git
+repository: it is not unheard of for code that is known to be broken to
+be checked in. Use at your own risk.
+
+
+System-specific Notes
+---------------------
+
+It has been reported that the XLC 1.2 compiler on AIX 3.2 is buggy such
+that if you compile make with 'cc -O' on AIX 3.2, it will not work
+correctly. It is said that using 'cc' without '-O' does work.
+
+The standard /bin/sh on SunOS 4.1.3_U1 and 4.1.4 is broken and cannot be
+used to configure GNU make. Please install a different shell such as
+bash or pdksh in order to run "configure". See this message for more
+information:
+ http://mail.gnu.org/archive/html/bug-autoconf/2003-10/msg00190.html
+
+One area that is often a problem in configuration and porting is the code
+to check the system's current load average. To make it easier to test and
+debug this code, you can do 'make check-loadavg' to see if it works
+properly on your system. (You must run 'configure' beforehand, but you
+need not build Make itself to run this test.)
+
+Another potential source of porting problems is the support for large
+files (LFS) in configure for those operating systems that provide it.
+Please report any bugs that you find in this area. If you run into
+difficulties, then as a workaround you should be able to disable LFS by
+adding the '--disable-largefile' option to the 'configure' script.
+
+On systems that support micro- and nano-second timestamp values and
+where stat(2) provides this information, GNU make will use it when
+comparing timestamps to get the most accurate possible result. However,
+note that many current implementations of tools that *set* timestamps do
+not preserve micro- or nano-second granularity. This means that "cp -p"
+and other similar tools (tar, etc.) may not exactly duplicate timestamps
+with micro- and nano-second granularity on some systems. If your build
+system contains rules that depend on proper behavior of tools like "cp
+-p", you should consider using the .LOW_RESOLUTION_TIME pseudo-target to
+force make to treat them properly. See the manual for details.
+
+
+Ports
+-----
+
+ - See README.customs for details on integrating GNU make with the
+ Customs distributed build environment from the Pmake distribution.
+
+ - See README.VMS for details about GNU Make on OpenVMS.
+
+ - See README.Amiga for details about GNU Make on AmigaDOS.
+
+ - See README.W32 for details about GNU Make on Windows NT, 95, or 98.
+
+ - See README.DOS for compilation instructions on MS-DOS and MS-Windows
+ using DJGPP tools.
+
+ A precompiled binary of the MSDOS port of GNU Make is available as part
+ of DJGPP; see the WWW page http://www.delorie.com/djgpp/ for more
+ information.
+
+Please note there are two _separate_ ports of GNU make for Microsoft
+systems: a native Windows tool built with (for example) MSVC or Cygwin,
+and a DOS-based tool built with DJGPP. Please be sure you are looking
+at the right README!
+
+
+-------------------------------------------------------------------------------
+Copyright (C) 1988-2016 Free Software Foundation, Inc.
+This file is part of GNU Make.
+
+GNU Make is free software; you can redistribute it and/or modify it under the
+terms of the GNU General Public License as published by the Free Software
+Foundation; either version 3 of the License, or (at your option) any later
+version.
+
+GNU Make is distributed in the hope that it will be useful, but WITHOUT ANY
+WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
+A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License along with
+this program. If not, see <http://www.gnu.org/licenses/>.