[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cleanup initialization of configure process (issue 549350043 by addr

From: jonas . hahnfeld
Subject: Re: Cleanup initialization of configure process (issue 549350043 by address@hidden)
Date: Tue, 14 Jan 2020 10:21:32 -0800

On 2020/01/14 15:54:28, dak wrote:
Well, how about
diff --git a/ b/
index 1ca0fc0c0f..c638993f34 100755
--- a/
+++ b/
@@ -18,7 +18,7 @@ else
    conf_flags="--srcdir $srcdir $conf_flags"
    echo "Running autoconf for read-only source directory ..."
-  autoconf -I "$srcdir" -o "$configure" "$srcdir/" ||
exit 1
+  SRCDIR="$srcdir" autoconf -I "$srcdir" -o "$configure"
|| exit 1
  # Autoconf automatically checks its own minimum required
  # version, and it aborts when the check fails.
diff --git a/ b/
index bdbc827187..c75e01de9b 100644
--- a/
+++ b/
@@ -4,7 +4,9 @@ dnl Process this file with autoconf to produce a

  # Bootstrap the init process.
+    [m4_esyscmd_s([. ${SRCDIR:-.}/VERSION; echo
+    mailto:[address@hidden], [lilypond],

  # Bootstrap StepMake configure

That would seem to cater for Dan's use case reasonably well.  Sure,
autoconf from outside of for a read-only source
directory...  But at
some point of time, people have to deal with the strange things they

IF we really want to continue supporting autoconf in a read-only
directory, then this sounds like one of the few possibilities we have.
I've added this for now (thanks for your testing efforts!), but it will
probably hit us sooner or later...

Dan, if you don't want to run with a writable ~/lilypond-src,
maybe you can instead copy all files from that directory to a fresh one
in the container?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]