Commit f766139c authored by Ralf S. Engelschall's avatar Ralf S. Engelschall
Browse files

Add some more LIBS for the SCO5 platform which are needed for the already

used -lprot. It's actually a bug in SCO5, of course.

The background is this feedback from R.Record after I replied to him:
``Third, i still find the addition of "-lx -ltinfo -lm" to be necessary on
OpenServer. It's no doubt a bug or at least incorrectly documented, but any
time -lprot is used you also need -lx and -ltinfo to get nap(), cur_term(),
setup_term() and others. I've informed our development system guys and this
may be fixed in a later release but for now these libs are necessary. FYI,
libx is the SCO Xenix enhancements which have been carried forward since time
immemorial while libtinfo is the terminfo library. It looks like libprot is
supposed to setup its own curses stuff but isn't built correctly''

BTW, the following he also mentioned:
``First, a kernel bug in OpenServer 5.0.0 and 5.0.2 made it necessary to build
Apache with USE_FCNTL_SERIALIZED_ACCEPT.  That bug was fixed in 5.0.4 and a
patch made available for 5.0.0/5.0.2 systems. Further, i have created an
installation script which detects what release you are installing on and
whether you need to apply the "Network Maintenance Supplement".  Therefore, i
can now build Apache without the USE_FCNTL_SERIALIZED_ACCEPT which gets me
much better performance.  So, as long as you get Apache for OpenServer from
_me_ (that is, the SCO Skunkware CD-ROM or web site), you're ok. If you build
it yourself, you'd better know whether you need to apply the appropriate
support supplement.''

But I still think it's not really good to remove the
USE_FCNTL_SERIALIZED_ACCEPT. The only correct solution would be to dispatch
for 5.0.0 and 5.0.2 and avoid it only for >= 5.0.4.

Submitted by: Ronald Record <rr@sco.com>
PR: 2533


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@82027 13f79535-47bb-0310-9956-ffa450edef68
parent c235c045
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment