|
On Tue, 17 Apr 2001, Jason Bechtel wrote: > Scott Klement wrote: > > > > Does it still do this with the current development sources? > > You'll have to help me to get setup with the development sources. I'm > still new to CVS. To build from CVS, I have to have some extra development tools. I have: autoconf-2.13, automake-1.4, libtool-1.3.4 To build version 0.17.x (the current development version) of tn5250, you also need glib-1.2.7 or later To get the sources, type: cvs -d ':pserver:anonymous@cvs.cleveland.lug.net:/tn5250' login (it'll ask you for a password. the password is "anonymous") cvs -d ':pserver:anonymous@cvs.cleveland.lug.net:/tn5250' checkout tn5250 The result should be a directory called "tn5250" which has the current sources in it. To build them, type: cd tn5250/ ./autogen.sh ./configure make To install them type (as root): make install > > In the meantime I'm checking out 0.16.1. Do you think this will fix it? It may help. 0.16.1 does have some changes to that section of code. There are some bug fixes to the 0.16.x branch in CVS as well. To get the 0.16 branch from CVS, follow the same procedure as 0.17.x, except add a switch to the checkout, like so: cvs -d ':pserver:anonymous@cvs.cleveland.lug.net:/tn5250' checkout -r b0-16 tn5250 (that should all be one line -- in case it gets wordwrapped) you can also add a -d option to the "checkout" if you want to download into a different directory name. so you might have something like: . . . checkout -r b0-16 -d tn5250-0.16 tn5250 or . . . checkout -r HEAD -d tn5250-0.17 tn5250 Once you have the branch that you want, you can update your directory to match the CVS server simply by: cd tn5250-0.16 cvs update > > Can you tell me how to reproduce the problem? > > It's rather involved and I think the steps would be specific to the > application that my client is using. I've counted and it takes about 68 > keystrokes to ge the point in the application where the emulator > crashes. Hmmm... this makes it more difficult for me to try to come up with a fix. A tracefile might help, but I'm not familiar with them. :( If the problem persists after upgrading tn5250, maybe I'll take a look at that... or give Mike access to my AS/400 to see if he can figure it out :) +--- | This is the LINUX5250 Mailing List! | To submit a new message, send your mail to LINUX5250@midrange.com. | To subscribe to this list send email to LINUX5250-SUB@midrange.com. | To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.