<div>
SCO is now 18 years past its release date* and there have been major changes in u-fix since 2003. &nbsp;lftp might have compiled on SCO previous to lftp 4.0.0 (released 2004), but it is unlikely that later versions which use modern encryption methods can compile and link correctly. &nbsp;The necessary libraries won't be there and those which <i>are</i> present are well out of date, which will break build dependencies.<br />
<br />
I/M/O it would be more profitable to come forward to a newer release of u-fix that is supportable.<br />
<br />
However, if you are determined to chase the problem, look at line 1906 in the .configure file, stick in a line to echo it during the build process, and see if there is an obvious syntax problem.<br />
<br />
(*)<a href="https://en.wikipedia.org/wiki/OpenServer" rel="ugc">https://en.wikipedia.org/wiki/OpenServer</a>
</div>


Fractional CTO

David Favor

tomwe

<div>
The paraphrase Dr. Klahn, &quot;SCO... A blast from the past...&quot;<br />
<br />
You mentioned, <b>&quot;I am not a C developer&quot;</b>...<br />
<br />
It's very likely you'll have to become a C developer, if you expect to get much recent software compiled on an old SCO system.<br />
<br />
You asked, <b>&quot;anyone have any suggestions?&quot;</b><br />
<br />
Likely you'll have to start by rewriting the configure script, as the error you mention is likely a shell-ish...<br />
<br />
That's just the beginning, as it's likely whatever source code you compile, you'll have to hand edit the source in some way to get a clean compile... then... if the code fails the test suite... or worse, just flat out fails to work... you'll be going through all the source code... line by line... potentially rewriting significant amounts of code...<br />
<br />
The lftp program is fairly simple, compared to many other tools, so this will be a somewhat painful adventure, rather than a horribly painful adventure.<br />
<br />
First step will be to turn on shell debugging (likely <b>set -x</b>) in the configure script + rewrite configure to work, then proceed on to whatever else must be fixed.
</div>


Principal Software Engineer

Dr. Klahn

<div>
I second what David has said above.<br />
<br />
Side note:<br />
<br />
Unless you keep meticulous and specific notes ... even if you do get this to work, the system will probably be married to this specific version until the system is decommissioned. &nbsp;There will be a lot of probe-and-try that is unlikely to all end up in a project notebook, resulting in &quot;Yes it works, but how is voodoo.&quot;<br />
<br />
Even if all changes are logged, the changes necessary to make it work again on a new release of lftp are not probably going to be quite exactly the same, and you will not want to do them over again every six months when a new release pops up.
</div>


<div>
Suggestion: Likely there's some reason why you're still running SCO, like a binary executable file with no source, so it can't be recompiled.<br />
<br />
Might be useful to open a 2nd question describing why you're still using SCO, specifically what's keeping you from moving up to a recent version of Linux.<br />
<br />
If you can solve the problem keeping your trapped in SCO, might be faster to escape SCO, than live with SCO.
</div>


<div>
thanks for all your comments. and yes I am trapped in SCO, it runs a custom written program in SCO FoxBase that the company runs on. I only need to get lftp to run for a year or so until the replacement software is done <br><br>Thanks for the comments
</div>


<div>
Perfect.<br />
<br />
I had a similar case like this a few years ago.<br />
<br />
As best I recall... this was before I started keeping copious notes about every action I take on every project...<br />
<br />
Seems like I found an emulator which allowed the database system (seems like it was something different than FoxBase) to run under current Linux Distro.<br />
<br />
Here's how I'd approach this.<br />
<br />
1) Setup an Ubuntu Focal (LTS) machine.<br />
<br />
2) Remove all traces of APT LXD, install SNAP LXD.<br />
<br />
3) Create an LXD container for your testing.<br />
<br />
4) Install an emulator, clone your SCO data over to your LXD container.<br />
<br />
5) Run experiments, till you get this working.<br />
<br />
6) At this point you have a self contained, bootable entity, inside a container, you can then move to any machine running LXD.<br />
<br />
Said differently, once you get this working, the container will keep working, independent of machine where container is running.<br />
<br />
7) At this point, work to replace the entire FoxBase system.
</div>


<div>
<u><a href="https://github.com/search?q=foxbase" rel="ugc">https://github.com/search?q=foxbase</a></u> provides an alternative approach.<br />
<br />
Find a version of Foxbase that works on recent Linux Distros, then migrate your Foxbase data into a working version of Foxbase.
</div>


<div>
<div class="content wysiwyg-content fr-view">
I am trying to compile a GNU program on my SCO server, specifically it is lftp. I need it to do FTP-TLS uploads from the server.<br>I have installed gcc from SCO skunkworks 98 and what I believe are all of the required supplements.<br>but every time I try to run ./configure I get the error: &nbsp;./configure[1906]: : is not an identifier<br>In the README file there is this note: The package is known to compile on Solaris(gcc), Linux, FreeBSD, NetBSD, SCO v5.0(gcc), IRIX(gcc), Tru64(gcc) and other systems.<br>so it should compile.<br>I am not a C developer, I am just doing my best to follow what instructions I can find on google.<br>I have tried newer and older versions but get the same error, just a different error number.<br>I even get the error when I try to run ./configure --help<br><br>I must be missing something but I can't figure out what, anyone have any suggestions?<br>TIA<br>Tom<br><br><br><br>
</div>
</div>



I am trying to compile a GNU program on my SCO server, specifically it is lftp. I need it to do FTP-TLS uploads from the server.
I have installed gcc from SCO skunkworks 98 and what I believe are all of the required supplements.
but every time I try to run ./configure I get the error:  ./configure[1906]: : is not an identifier
In the README file there is this note: The package is known to compile on Solaris(gcc), Linux, FreeBSD, NetBSD, SCO v5.0(gcc), IRIX(gcc), Tru64(gcc) and other systems.
so it should compile.
I am not a C developer, I am just doing my best to follow what instructions I can find on google.
I have tried newer and older versions but get the same error, just a different error number.
I even get the error when I try to run ./configure --help
I must be missing something but I can't figure out what, anyone have any suggestions?
TIA
Tom

compile GNU software on SCO UNIX 5.0.7 using gcc

C is a general-purpose, imperative computer programming language, supporting structured programming, lexical variable scope and recursion, while a static type system prevents many unintended operations. By design, C provides constructs that map efficiently to typical machine instructions, so it has found lasting use in applications that had formerly been coded in assembly language, including operating systems as well as various application software for computers ranging from supercomputers to embedded systems. It is distinct from C++ (which has its roots in C) and C#, and many later languages have borrowed directly or indirectly from C.

Unix is a multitasking, multi-user computer operating system originally developed in 1969 at Bell Labs. Today, it is a modern OS with many commercial flavors and licensees, including FreeBSD, Hewlett-Packard’s UX, IBM AIX and Apple Mac OS-X. Apart from its command-line interface, most UNIX variations support the standardized X Window System for GUIs, with the exception of the Mac OS, which uses a proprietary system.