[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after auto
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure |
Date: |
Tue, 24 Jan 2017 01:10:20 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #4, bug #50129 (project octave):
Yes, I want to save the value for MOC and MOCFLAGS together. I tried changing
the line
AC_SUBST(MOCFLAGS)
to
AC_ARG_VAR(MOCFLAGS, [flags to pass to moc])
However, the problem still remains. According to the documentation for
AC_ARG_VAR
The value of variable when configure was launched is saved in the cache,
including if it was not specified on the command line but via the environment.
Indeed, while configure can notice the definition of CC in ‘./configure
CC=bizarre-cc’, it is impossible to notice it in ‘CC=bizarre-cc
./configure’, which, unfortunately, is what most users do.
We emphasize that it is the initial value of variable which is saved, not that
found during the execution of configure. Indeed, specifying ‘./configure
FOO=foo’ and letting ‘./configure’ guess that FOO is foo can be two
different things.
This is indeed what seems to be happening. The initial value is "", and then
it is calculated by this stanza in m4/acinclude.m4.
if test -z "$MOC"; then
AC_CHECK_TOOLS(MOC, [moc])
if test -n "$QTCHOOSER"; then
MOCFLAGS="-qt$qt_version"
fi
fi
The cached value is always "", rather than the calculated value, which doesn't
wark. I'm trying something with AC_CACHE_CHECK right now to see if that
works.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50129>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Rik, 2017/01/23
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Rik, 2017/01/23
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Mike Miller, 2017/01/23
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Mike Miller, 2017/01/23
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure,
Rik <=
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Rik, 2017/01/23
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, John W. Eaton, 2017/01/24
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Mike Miller, 2017/01/24
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, John W. Eaton, 2017/01/24
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Mike Miller, 2017/01/24
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Mike Miller, 2017/01/24
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Rik, 2017/01/24
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, John W. Eaton, 2017/01/24
- [Octave-bug-tracker] [bug #50129] Incorrect Qt version chosen after automatic updates to configure, Rik, 2017/01/24