|
From: | Philip Nienhuis |
Subject: | [Octave-bug-tracker] [bug #58331] (pkg.m) "V=1" flag in configure_make leads to incorrect cmd |
Date: | Thu, 7 May 2020 17:03:16 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0 |
URL: <https://savannah.gnu.org/bugs/?58331> Summary: (pkg.m) "V=1" flag in configure_make leads to incorrect cmd Project: GNU Octave Submitted by: philipnienhuis Submitted on: Thu 07 May 2020 11:03:14 PM CEST Category: Octave Function Severity: 3 - Normal Priority: 5 - Normal Item Group: Regression Status: None Assigned to: None Originator Name: Philip Nienhuis Originator Email: Open/Closed: Open Release: 6.0.90 Discussion Lock: Any Operating System: GNU/Linux _______________________________________________________ Details: With Octave-6.0.1 (just built tonight) io pkg installation fails because the entire configure step is skipped. The culprit is the recent addition of the V=1 flag in cset c26838a3afa6, which leads to the following command in L.88: cmd = cd '/tmp/oct-Ny2IZN/io-2.6.1/src'; MKOCTFILE='/usr/local/bin/mkoctfile-6.0.1 --verbose' OCTAVE_CONFIG='/usr/local/bin/octave-config-6.0.1' OCTAVE='/usr/local/bin/octave-6.0.1' V=1./configure CC="gcc " CXX="g++ " AR="ar " RANLIB="ranlib " Adding just one space after "V=1" loosens it from the ensuing "./configure" command. I'ĺl upload a cset once I have a bug number. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?58331> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |