[strongSwan] Cannot compile strong-swan from git
Ben Greear
greearb at candelatech.com
Mon Jul 15 15:01:35 CEST 2019
On 07/14/2019 10:54 PM, Martin Willi wrote:
> Hi Ben,
>
>> First, maybe autogen could detect this missing gperf right at the
>> beginning and tell the user?
>
> ./autogen.sh is just a wrapper for autogen -i these days, so it won't
> help users calling that directly.
>
> Doing such a check in ./configure is no option, as gperf is not
> required for an ordinary build from tarball. The gperf (and other)
> output is part of the distribution tarball, so that users don't need
> non-standard tools.
You could check for existence of gperf or detect that you are in a build
system that has already successfully run gperf and fail if neither of those
are true.
The make maintainer-clean is indeed a useful step. If the make file were
done better, though, it could add a dependency such that when the gperf
generated files or makefile were changed, then they are automatically re-built.
Please see the patch that I posted that fixes detection of gperf on
older build systems. With that, it builds back to fedora-17 at least.
Centos-6 still fails, but I am thinking I will just ignore that.
Thanks,
Ben
>
>> confread.o: In function `load_conn':
>> /home/greearb/git/strongswan/src/starter/confread.c:568: undefined
>> reference to `in_word_set'
>
> Try "make maintainer-clean", and start from scratch with autogen and
> ./configure.
>
> The problem here is that the gperf rule generates an empty file if
> gperf is missing, and then "make" thinks the file is up to date once
> gperf got installed. I've tried to address this issue with [1].
>
> Regards
> Martin
>
> [1] https://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=bca7571b0fa17b3b0c448187166833ad3664250c
>
--
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
More information about the Users
mailing list