From fb2cd4775f20876c2976085560f6df9de40b4508 Mon Sep 17 00:00:00 2001 From: Daniel Andrade Date: Sun, 4 Sep 2016 00:51:57 -0300 Subject: [PATCH 1/2] Added missing compilation instruction on README --- README.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.txt b/README.txt index f47d03f5f..8d5f1bbb9 100644 --- a/README.txt +++ b/README.txt @@ -77,7 +77,8 @@ the configure scripts. Unpack the tar-ball and cd into the verilog-######### directory (presumably that is how you got to this README) and compile the source with the commands: - + + sh autoconf.sh ./configure make From 7362c7cbf8c8d822fb24deead5e0b83893291ee2 Mon Sep 17 00:00:00 2001 From: Daniel Andrade Date: Fri, 30 Jun 2017 20:41:55 -0300 Subject: [PATCH 2/2] Clarifying compilation instructions --- README.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.txt b/README.txt index 8d5f1bbb9..a2e535955 100644 --- a/README.txt +++ b/README.txt @@ -78,10 +78,15 @@ Unpack the tar-ball and cd into the verilog-######### directory (presumably that is how you got to this README) and compile the source with the commands: - sh autoconf.sh ./configure make +If you are building from git, you have to run the command below before +compile the source. This will generate the "configure" file, which is +automatically done when building from tarball. + + sh configure.sh + Normally, this command automatically figures out everything it needs to know. It generally works pretty well. There are a few flags to the configure script that modify its behavior: