On Wed, 2003-02-05 at 16:49, Scott Klement wrote:
> Hi Martin,
> 
> Looking in CVS, I see that the 2nd argument to tn5250_stream_open() was
> added 26 Sep 2001.
> 
> Is it possible that it's linking against a version of tn5250 that's older
> than that?  Please try updating your version of lib5250 (part of the base
> tn5250 package) to a recent version, and then re-build gnome-5250.

Hi Scott

It is a month older than that, so I checked out tn5250 to build, but get
undefined macro errors for that.

mrowe@mrowe:~/tn5250$ ./autogen.sh 
autoconf: Undefined macros:
configure.in:234:AC_CONFIG_FILES([Makefile src/Makefile tn5250.spec
doc/Makefile linux/Makefile freebsd/Makefile win32/Makefile sun/Makefile
tn5250-config xt5250])
configure.in:3:AC_CONFIG_SRCDIR([src/tn5250.c])
autoconf: Undefined macros:
configure.in:234:AC_CONFIG_FILES([Makefile src/Makefile tn5250.spec
doc/Makefile linux/Makefile freebsd/Makefile win32/Makefile sun/Makefile
tn5250-config xt5250])
configure.in:3:AC_CONFIG_SRCDIR([src/tn5250.c])

then I get

mrowe@mrowe:~/tn5250$ ./configure
creating cache ./config.cache
./configure: line 720: syntax error near unexpected token `src/tn5250.c'
./configure: line 720: `AC_CONFIG_SRCDIR(src/tn5250.c)'

I'll try with a .deb of tn5250 to see if I can get the gnome-5250
compiled, but I normally tweak cursesterm.c to get blue instead of cyan
on my screen, so like to build from source.

Regards, Martin
-- 
martin@dbg400.net  AIM/Gaim: DBG400dotNet  http://www.dbg400.net       /"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open        \ /
Source free test environment tools and others (file/spool/misc)         X 
[this space for hire]  ASCII Ribbon Campaign against HTML mail & news  / \


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].