From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2, 1/1] package/ngircd: fix static build with openssl and atomic
Date: Mon, 15 Apr 2019 22:10:11 +0200 [thread overview]
Message-ID: <20190415221011.55b0ea91@windsurf> (raw)
In-Reply-To: <20190414155153.4317-1-fontaine.fabrice@gmail.com>
On Sun, 14 Apr 2019 17:51:53 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fixes:
> - http://autobuild.buildroot.org/results/72345ebd144bed824329618e66721a98eba3be22
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
This was still causing the AC_CHECK_LIB error here, which was in fact
due to the use of PKG_CHECK_MODULES without having host-pkgconf in the
dependencies. With this, ngircd built fine, but unfortunately, there is
still an issue.
> +# We're patching configure.ng, but package cannot autoreconf with
> +# automake >= 1.12 because de-ANSI-fication has been removed so apply the same
> +# tweaks that are done by upstream in autogen.sh
> +define NGIRCD_REMOVE_DE_ANSI_FICATION
> + sed -e "s|^__ng_PROTOTYPES__|AC_C_PROTOTYPES|g" \
> + $(@D)/configure.ng > $(@D)/configure.ac
> +
> + sed -e "s|^__ng_Makefile_am_template__|AUTOMAKE_OPTIONS = ${SERIAL_TESTS} #ansi2knr|g" \
This ${SERIAL_TESTS}
> + $(@D)/src/portab/Makefile.ng > $(@D)/src/portab/Makefile.am
> + for i in ipaddr/Makefile ngircd/Makefile testsuite/Makefile tool/Makefile; do \
> + sed -e "s|^__ng_Makefile_am_template__|AUTOMAKE_OPTIONS = ${SERIAL_TESTS} #../portab/ansi2knr|g" \
and here, cause check-package to complain:
package/ngircd/ngircd.mk:23: use $() to delimit variables, not ${}
package/ngircd/ngircd.mk:26: use $() to delimit variables, not ${}
so we need to find a way to either silence those warnings, or work
around them. Perhaps we could simply include a patch ?
The tarball already has the configure.ac and Makefile.am generated,
they only need to be tweaked for de-ansi-fication, and a patch may be a
good alternative.
What do you think ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-15 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 15:51 [Buildroot] [PATCH v2, 1/1] package/ngircd: fix static build with openssl and atomic Fabrice Fontaine
2019-04-15 20:10 ` Thomas Petazzoni [this message]
2019-04-15 21:08 ` Arnout Vandecappelle
2019-04-15 21:14 ` Thomas Petazzoni
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=20190415221011.55b0ea91@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 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.