From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libmodsecurity: fix build with libmaxminddb
Date: Sun, 18 Jul 2021 14:06:06 +0200 [thread overview]
Message-ID: <20210718140606.1ba06d6b@windsurf> (raw)
In-Reply-To: <20210717203343.GX12203@scaer>
Hello,
On Sat, 17 Jul 2021 22:33:43 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> +
> +# configure.ac will call git to get various version strings, from
> +# libmodsecurity itself, but also from bundled dependencies, just
> +# for the sake of siplaying them at the end of configure.
> +# Fake a git that returns the version for libmodescurity, to quiesce
> +# warnings...
> +define LIBMODSECURITY_FAKE_GIT
> + $(Q)mkdir -p $(@D)/.buildroot
> + $(Q)printf '#!/usr/bin/env sh\necho "$(LIBMODSECURITY_VERSION)"\n' \
> + >$(@D)/.buildroot/git
> + @(Q)chmod 755 $(@D)/.buildroot/git
> +endef
> +LIBMODSECURITY_POST_EXTRACT_HOOKS += LIBMODSECURITY_FAKE_GIT
> +
> +# 0001-Revert-Fix-maxminddb-link-on-FreeBSD.patch
> +LIBMODSECURITY_AUTORECONF = YES
> +LIBMODSECURITY_AUTORECONF_ENV = PATH="$(@D)/.buildroot:$(BR_PATH)"
> +
> LIBMODSECURITY_CONF_OPTS = \
> --with-pcre="$(STAGING_DIR)/usr/bin/pcre-config" \
> --disable-examples \
Shouldn't we "simply" teach to libmodsecurity configure.ac that it may
be autoreconf'ed outside of a Git repository ?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-18 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 17:20 [Buildroot] [PATCH 1/1] package/libmodsecurity: fix build with libmaxminddb Fabrice Fontaine
2021-07-17 9:11 ` Yann E. MORIN
2021-07-17 19:33 ` Fabrice Fontaine
2021-07-17 20:33 ` Yann E. MORIN
2021-07-18 7:55 ` Fabrice Fontaine
2021-07-18 8:08 ` Yann E. MORIN
2021-07-18 8:33 ` Fabrice Fontaine
2021-07-18 9:25 ` Yann E. MORIN
2021-07-18 12:06 ` Thomas Petazzoni [this message]
2021-07-18 12:25 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210718140606.1ba06d6b@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox