I just did a git pull and make update
article.c gcc: warning: @BLOCKLIST_CPPFLAGS@: linker input file unused because linking not done gcc: error: @BLOCKLIST_CPPFLAGS@: linker input
file not found: No such file or directory make[1]: *** [Makefile:44: article.o] Error 1 make[1]: Leaving directory '/usr/compile/inn/nnrpd'
make: *** [Makefile:58: all] Error 1
Any suggestions? I also did a make distclean and then make and the same results.
Hi Nigel,
I just did a git pull and make update
article.c gcc: warning: @BLOCKLIST_CPPFLAGS@: linker input file
unused because linking not done gcc: error: @BLOCKLIST_CPPFLAGS@:
linker input file not found: No such file or directory make[1]: *** [Makefile:44: article.o] Error 1 make[1]: Leaving directory '/usr/compile/inn/nnrpd' make: *** [Makefile:58: all] Error 1
Any suggestions? I also did a make distclean and then make and the
same results.
This is not enough when building from Git.
You'll normally see a file named BOOTSTRAP at the root of the
repository, saying:
"""
If you're seeing this file, you have cloned or checked INN out of
Git, or otherwise obtained a copy of the development tree rather than
a snapshot or standard release. This means that you need to start by bootstrapping the tree before you can build INN or read much of the documentation.
To do this, run:
./autogen
./configure
make bootstrap
"""
./autogen
./configure
make bootstrap
Oh ok. I thought autogen was only required when first building from a
new git clone. I'll add this to my notes since it's the first time I've
come across this issue.
Hi Nigel,
./autogen
./configure
make bootstrap
Oh ok. I thought autogen was only required when first building from
a new git clone. I'll add this to my notes since it's the first
time I've come across this issue.
If you do not run autogen, the modification of some files
(configure.ac and related m4 files used at configure time,
innshellvars scripts, Makefile.global, include/config.h,
include/inn/paths.h and a few others) won't be picked up. It could
lead to an unexpected behaviour, though the code builds fine. Of
course, you'll notice it directly when the code no longer builds
because a new macro is used, defined at configure time, but not
present in the files generated by a previous run of configure.
(That's the case you encountered.)
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 70 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:56:14 |
| Calls: | 949 |
| Calls today: | 1 |
| Files: | 1,325 |
| Messages: | 281,114 |