Re: Getting ready to put out a 4.6 release candidate

[Ethan A M. <sf...@us...>]

Mojca Miklavec <moj...@gm...> wrote >
 
> Qt terminal doesn't work on Mac OS X, but I don't know if you plan to
> fix this before 4.6 on not.

Not me :-)  I think we have established very well that people here are not
up to the task of configuring support for new options under OSX.

> There are at least the following issues:
> - configure script is unable to find Qt 

It uses pkg-config.  If your Qt installation does not come with a set of
*.pc files then the configuration script will not work.

> - MOC and UIC are set to an empty string; here "moc" and "uic"
> commands work fine, but I don't know why configure script doesn't find
> them

Because it queries pkg-config to find out where they are.
   MOC=`pkg-config --variable=moc_location QtCore`

By the way, what version of Qt are you trying to use?
I've just been debugging configuration problems with Qt 4.7.4, where it turns
out that I need to do the same thing in order to pick up locations for
the rcc and lrelease utilities.

> - if I fix the two above, qt terminal compiles fine, but I cannot plot anything:
>
> gnuplot> plot sin(x)
> The process has forked and you cannot use this CoreFoundation
> functionality safely. You MUST exec().
> Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__()
> to debug.

No idea what that's about. It is clearly some OSX weirdness.
Googling that error message turns up this totally bizarre advice:

  In Server Admin stop SMB, remove it from services (save), re-add it (save), then start SMB.

In other words, people seem to have gotten this error message as a side effect of
the network/SMB configuration.

	Ethan