Re: 5.0-rc3 on OpenBSD 5.6: mostly ok, but a few glitches

[Hans-Bernhard B. <HBB...@t-...>]

Am 07.12.2014 um 05:54 schrieb sfeam:
> On Saturday, 06 December 2014 09:22:12 PM Jonathan Thornburg wrote:

>> configure: WARNING: 'missing' script is too old or missing

> So far as I know this message is annoying but harmless.
> It has something to do with version mismatch of the "automake" tool.

Indeed.  If aclocal.m4 was built by automake-1.13 or newer, but the 
'missing' script is older, you get this warning from the generated 
'configure' script.

FWIW, I have updates of the auto toolage to automake-1.14 / 
autoconf-2.69 sitting here, as mentioned previously in another thread. 
They seem to work fine.

> I can look into replacing the "missing" script with a newer version,
> but I hate making such a change this late in the release process.

I agree that auto tools changes should not go into the 5.0 branch just 
now. But they might be worth putting into HEAD.

> On the other hand, I think the script is only relevant to the packaging
> process itself, not to simply building or installing the program.
> So even if a last-minute replacement fails on some systems, it may
> affect only developers, not end users.
>
>> The other glitches I found were (I suspect) OpenBSD-specific.  Notably,
>> the wxt terminal compiled and linked ok, but core-dumps at the first
>> 'plot' command -- here's a stack traceback:
>>
>> (gdb) bt
>> #0  0x00001e14021cf83a in kill () at <stdin>:2
>> #1  0x00001e1402231889 in abort () at /usr/src/lib/libc/stdlib/abort.c:53
>> #2  0x00001e1454e68205 in _rthread_mutex_lock (mutexp=0x1e13fcb446d0,
>>      trywait=0, abstime=0x0) at /usr/src/lib/librthread/rthread_sync.c:127
>> #3  0x00001e13d696eba9 in wxMutexInternal::Lock ()
>>     from /usr/local/lib/libwx_base.so.3.0
>                              ^^^^^^^^^^^^^^^
>
> Unfortunately wxt 3.0 does not work with gnuplot.
> (I'm sure they would claim that is better said "gnuplot does not
> work with wxt 3.0" ;-)
>
> No fix is known and I am not aware of anyone working on it.
> It may not be fixable in general, although a couple of people have reported
> that
> 	./configure   --with-wx-single-threaded
> allows it to run correctly even though it prints alarming error messages.
> For me that configuration option doesn't make any apparent difference.
>
> This problem has already hit gnuplot packaging on both OSX and Debian,
> both of which have switched to the newer wxt and not made adequate provision
> for programs that require the older version 2.8.  Sad, really.
> The only work-around I can recommend at this point is to use the qt terminal
> instead.