On Sat, Mar 4, 2017 at 5:41 PM, Abhishek Tiwari
<erabhishektiwar...@gmail.com> wrote:
> Good evening everyone,
> I am Abhishek Tiwari pursuing M.Tech IIT Kharagpur. I am looking
> forward to contribute to strace Project Idea -> Netlink socket
> parsers.
>
> Thank you.
Hi,
I have made a change in INSTALL file (there the bootstrap script was
not mentioned to be run in installation step). Please review the
patch.
I am inside a private network, so cannot send patch through git
send-email due to network settings.
Is sending patch preferred over sending pull request or I can directly
send pull requests from github?
From 45cccac74d4251713af450a62425496bad3a7195 Mon Sep 17 00:00:00 2001
From: Abhishek Tiwari <erabhishektiwar...@gmail.com>
Date: Sun, 5 Mar 2017 00:31:34 +0530
Subject: [PATCH v1] Updated INSTALL documentation
---
INSTALL | 18 ++++++++++--------
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/INSTALL b/INSTALL
index 0fad641..2c4c10a 100644
--- a/INSTALL
+++ b/INSTALL
@@ -51,30 +51,32 @@ of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system.
+ `./bootstrap' to copy required header files and generate configuration files.
+
+ 2. Type `./configure' to configure the package for your system.
Running `configure' might take a while. While running, it prints
some messages telling which features it is checking for.
- 2. Type `make' to compile the package.
+ 3. Type `make' to compile the package.
- 3. Optionally, type `make check' to run any self-tests that come with
+ 4. Optionally, type `make check' to run any self-tests that come with
the package, generally using the just-built uninstalled binaries.
- 4. Type `make install' to install the programs and any data files and
+ 5. Type `make install' to install the programs and any data files and
documentation. When installing into a prefix owned by root, it is
recommended that the package be configured and built as a regular
user, and only the `make install' phase executed with root
privileges.
- 5. Optionally, type `make installcheck' to repeat any self-tests, but
+ 6. Optionally, type `make installcheck' to repeat any self-tests, but
this time using the binaries in their final installed location.
This target does not install anything. Running this target as a
regular user, particularly if the prior `make install' required
root privileges, verifies that the installation completed
correctly.
- 6. You can remove the program binaries and object files from the
+ 7. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
@@ -83,12 +85,12 @@ The simplest way to compile this package is:
all sorts of other programs in order to regenerate files that came
with the distribution.
- 7. Often, you can also type `make uninstall' to remove the installed
+ 8. Often, you can also type `make uninstall' to remove the installed
files again. In practice, not all packages have tested that
uninstallation works correctly, even though it is required by the
GNU Coding Standards.
- 8. Some packages, particularly those that use Automake, provide `make
+ 9. Some packages, particularly those that use Automake, provide `make
distcheck', which can by used by developers to test that all other
targets like `make install' and `make uninstall' work correctly.
This target is generally not run by end users.
--
2.7.4
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Strace-devel mailing list
Strace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/strace-devel
