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

[sfeam <sf...@us...>]

On Saturday, 06 December 2014 09:22:12 PM Jonathan Thornburg wrote:
> I've just built 5.0-rc3 from the sourceforge tarball on OpenBSD 5.6
> (amd64).  There were minor glitches (see below), but overall -r3c seems
> to be in good shape (lots of great new features!), and almost ready for
> release.
> 
> The terminals I normally use (x11 and ps) work fine in my limited tests
> so far, as do pbm and pdfcairo.
> 
> Glitches:
> 
> Glitch 1: INSTALL refers to the configure option  --enable-bitmap-terminals
> but the configure script actually wants  -with-bitmap-terminals  (and
> complains about  --enable-bitmap-terminals  being unrecognized).

Oops.  Will fix.  Thanks for the report.

> Glitch 2. The configure script reports some problems with the 'missing'
> script:
> 
> --- begin start of build transcript ---
> Script started on Sat Dec  6 19:39:01 2014
> % uname -a
> OpenBSD cobalt.astro.indiana.edu 5.6 GENERIC.MP#0 amd64
> % /usr/bin/gcc --version
> gcc (GCC) 4.2.1 20070719
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> % /usr/bin/g++ --version
> g++ (GCC) 4.2.1 20070719
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> % gmake --version
> GNU Make 4.0
> Built for x86_64-unknown-openbsd5.6
> Copyright (C) 1988-2013 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> % ./configure --prefix /usr/local/ --disable-history-file --with-readline=gnu --with-bitmap-terminals --without-pdf --without-lua --with-qt CC=/usr/bin/gcc CXX=/usr/bin/g++ LIBS=-lm
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /usr/local/src/gnuplot/gnuplot-5.0.rc3/missing: Unknown `--is-lightweight' option
> Try `/usr/local/src/gnuplot/gnuplot-5.0.rc3/missing --help' for more information
> configure: WARNING: 'missing' script is too old or missing
> checking for a thread-safe mkdir -p... ./install-sh -c -d
> checking for gawk... gawk
> [[...]]
> --- end start of build transcript ---

So far as I know this message is annoying but harmless.
It has something to do with version mismatch of the "automake" tool.  
What version of automake do you have?
This line in the Makefile
	AUTOMAKE_OPTIONS = foreign
used to suppress the warning but maybe this is no longer sufficient.

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.
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.

	Ethan