From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libmodsecurity: fix build with libmaxminddb
Date: Sun, 18 Jul 2021 14:25:55 +0200 [thread overview]
Message-ID: <20210718122555.GF12203@scaer> (raw)
In-Reply-To: <20210718140606.1ba06d6b@windsurf>
Thomas, All,
On 2021-07-18 14:06 +0200, Thomas Petazzoni spake thusly:
> 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...
[--SNIP--]
> Shouldn't we "simply" teach to libmodsecurity configure.ac that it may
> be autoreconf'ed outside of a Git repository ?
Easier said than done... That was my initial thought, but given how
configure.ac is written, this will have to be quite some intrusive
changes. The most problematic being test/test-cases/secrules-language-tests
and others/libinjection, which are both managed via git submodules.
And no, switching over to downloading via git, will not help: we still
do not have a .git/ directory in the archives we generate, and from
which we do the build.
But really, sice these version strings are only ever used as informative
text at the end of configure, I don't think we should care much what
they get set to:
configure.ac:
414 # Print a fancy summary
415 echo " "
416 echo " "
417 echo "ModSecurity - ${MSC_GIT_VERSION} for $PLATFORM"
418 echo " "
419 echo " Mandatory dependencies"
420 echo -n " + libInjection ...."
421 echo LIBINJECTION_VERSION
422 echo -n " + SecLang tests ...."
423 echo SECLANG_TEST_VERSION
424
425 echo " "
426 echo " Optional dependencies"
configure:
24978 # Print a fancy summary
24979 echo " "
24980 echo " "
24981 echo "ModSecurity - ${MSC_GIT_VERSION} for $PLATFORM"
24982 echo " "
24983 echo " Mandatory dependencies"
24984 echo -n " + libInjection ...."
24985 echo v3.9.2-46-gbfba51f
24986 echo -n " + SecLang tests ...."
24987 echo a3d4405
24988
24989 echo " "
24990 echo " Optional dependencies"
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2021-07-18 12:25 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
2021-07-18 12:25 ` Yann E. MORIN [this message]
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=20210718122555.GF12203@scaer \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.