On Wed, Nov 14, 2018 at 11:01 AM Michael Biebl <bi...@debian.org> wrote:
> Hi Felipe
>
> On Wed, 14 Nov 2018 10:42:55 -0300 Felipe Sateler <fsate...@debian.org>
> wrote:
> > + SED=/bin/sed dh_auto_configure --builddirectory $${target}-build
> $(PARALLEL) -- $$(eval echo \$${$${target}_config}); \
>
> Reading
>
> https://stackoverflow.com/questions/13848154/passing-environment-variables-to-autoconfs-configure
> it appears to me that setting SED=/bin/sed as an argument to
> configure/dh_auto_auto_configure is preferred over passing as env var.
>
Thanks. Please find an attached patch. However, I don't think this makes a
practical difference for debian packages, since they run configure only
once per builddir.
--
Saludos,
Felipe Sateler
From ed1b5bb488c9b9b026e27bf273f668fe825ca9fe Mon Sep 17 00:00:00 2001
From: Felipe Sateler <fsate...@debian.org>
Date: Wed, 14 Nov 2018 10:36:47 -0300
Subject: [PATCH] Always use /bin/sed as sed command
Autodetection by configure script might find /usr/bin/sed in systems where
/ has been merged with /usr, which then doesn't work on non-merged systems.
Closes: #913228
---
debian/rules | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/debian/rules b/debian/rules
index c32856580..f953c2cb8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -206,7 +206,8 @@ COMMON_CONFIG := \
--with-zlib-dir=/usr \
$(CONFIGURE_ZTS) \
$(CONFIGURE_DTRACE_ARGS) \
- $(CONFIGURE_PCRE_JIT)
+ $(CONFIGURE_PCRE_JIT) \
+ SED=/bin/sed
# disable all SAPIs in extension build
export ext_config = \
--
2.19.1
