Re: I cant compile (53440f9bffba)

[Daniel J Sebald]

On 04/01/2018 01:55 PM, Doug Stewart wrote:
> On Sun, Apr 1, 2018 at 2:51 PM, Mike Miller <address@hidden 
> <mailto:address@hidden>> wrote:
>
>     On Sun, Apr 01, 2018 at 14:48:14 -0400, Doug Stewart wrote:
>     > I did
>     > ./configure  --with-qt=5
>     > and it worked, but I thought that qt5 was the default.
>
>     It is the default.
>
>     I guess that the ./configure forced the moc-* files to be regenerated,
>     you probably didn't need the --with-qt option. You might have also been
>     able to delete the moc-* files as Dan suggested.
>
>     --
>     mike
>
> I had done a complete
> ./bootstrap
> ./configure
> make
>    without success .
> then did
> ./configure  --with-qt=5
> and make and it worked.
> Thanks to all.
> Doug

It might be worth redoing your original configuration without the 
"--with-qt=5" option and investigate with the config.log looks like.

Did you do anything in between with updating packages or anything?  One 
thing that could happen is that the builder has all of the packages 
necessary for Qt 4 but not the now-required Qt5Help:

  ## Check for Qt libraries
  case "$qt_version" in
    4)
      QT_MODULES="QtCore QtGui QtNetwork QtOpenGL QtHelp"
    ;;
    5)
      QT_MODULES="Qt5Core Qt5Gui Qt5Network Qt5OpenGL Qt5PrintSupport 
Qt5Help"
    ;;
    *)
      as_fn_error $? "Unrecognized Qt version $qt_version" "$LINENO" 5
    ;;
  esac

in which case the config would fall back to Qt4.  (If the builder didn't 
have a complete Qt 4 package list, then the GUI would be excluded.)

The other aspect of this is that the version check goes through a loop, 
first looking whether Qt 4 is complete, then whether Qt 5 is complete. 
It could be that the MOC check

  for ac_prog in moc-qt$qt_version
  do
    # Extract the first word of "$ac_tool_prefix$ac_prog", so it can be 
a program name with args.
[snip]
      if test -n "$MOC" && test -n "$QTCHOOSER"; then
        MOCFLAGS="-qt$qt_version"
      fi

is independent.  That is, if there isn't already, there should be some 
logic that prevents MOCFLAGS="-qt5" if the Qt 5 package check fails. 
It's hard to tell the logic because AC-tools indents the output file 
"configure" so poorly.  In any case, that would be an auto-config issue, 
not Octave.

Dan