×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I would *strongly* recommend NOT installing lib5250 into /usr/lib.
James isn't a FreeBSD person, and he doesn't understand the FreeBSD
philosophy. In FreeBSD, /usr/local is for stuff installed by 3rd party
packages, etc. /usr is for stuff that's part of FreeBSD.
Typing "setenv LIBS -L/usr/local/lib" before configuring/building x5250
isn't that hard. (setenv is for csh/tcsh... if you use sh, ksh or bash,
use "export LIBS=-L/usr/local/lib" instead).
If you install into /usr, then you may find your next upgrade of FreeBSD
deleting the file. Or some administrator might decide to move your
software over to a new box by saving/restoring /usr/local and installing
/usr fresh, causing you to lose parts of tn5250.
Since it's FreeBSD... use the FreeBSD philosophy and install in
/usr/local!!
James Rich wrote:
Scott Klement reports that on his FreeBSD system he can't get x5250's
configure to find lib5250 if it installed in /usr/local/lib. Scott is no
slouch, so if x5250 can't find it then it is probably a problem with
x5250. Use Scott's solution which posted a few minutes ago or install
tn5250 in /usr. I always use the second option. If you want to install
in /usr just build tn5250 like this:
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.
midrange.com
