[Octave-bug-tracker] [bug #50214] qt not detected after changeset 23088

[John W. Eaton]

Update of bug #50214 (project octave):

                  Status:                    None => Works For Me           

    _______________________________________________________

Follow-up Comment #2:

Do you have qt4 but not qtchooser?

Looking at the configure script, it should be checking for the tools with the
"-qt4" suffix, then, if any of those are missing, checking again for the tools
without the suffix and using the "-qt4" option if qtchooser is available.

So it seems to me that the configure script should be able to find a mixture
of tools with or without the -qt4 suffix and with or without setting the -qt4
option in a FLAGS variable.

I just deleted the qt4 dev tools on my system and I now have uic and uic-qt4
installed (for example), but only rcc.  Running configure gives me UIC and RCC
set to uic and rcc and UICFLAGS and RCCFLAGS set to -qt4.  If I didn't have
qtchooser, I would expect empty values for the FLAGS variables, but UIC and
RCC still set to uic and rcc.

Is this a caching problem on your system?  Do you run configure with the
option to generate a cache file?  If so, try deleting any old cache file you
have.

Did you run bootstrap again after updating?  I'm not sure whether that's the
issue, but when strange things happen with configure and the development
sources, my first step is to start fresh.

If it still fails for you, then I need more info to understand how this can
fail, or you need to debug it and find where the logic is going wrong because
I can't duplicate it on my system.

If you want to send more info, then you can run the configure script with
"/bin/bash -xv" and extract the relevant parts of the output (there will be a
lot of it).


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50214>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/