>Number: 1646 >Category: os-solaris >Synopsis: Compile fails if /usr/ucb is on PATH during compile and >/usr/ucbinclude exists. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Sat Jan 10 04:10:00 PST 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.2.5 >Environment: SunOS prokyon 5.5.1 Generic_103640-14 sun4u sparc SUNW,Ultra-2 WorkShop Compilers 4.2 30 Oct 1996 C 4.2 >Description: First, this is NOT a bug in Apache, but a peculiarity in Sun's compiler driver that makes it appear as if the sources cannot compile cleanly. If during "make" the user's PATH includes /usr/ucb, then the compiler puts /usr/ucbinclude ahead of /usr/include on the -I path and links with dynamic libraries from /usr/ucblib. The result are a few compile problems that can be fixed, or so it seems (I can give details, if you wish). The resulting binary will not run correctly, however; most notable are mangled fancy directory listings, probably caused by /usr/ucbinclude/sys/dir.h vs. /usr/include/sys/dirent.h (the first two characters of every file name are missing, and other formatting problems).
The resulting binary will have /usr/ucblib/libucb.so.? linked in. If compiled correctly, no /usr/ucb/lib stuff should be there. >How-To-Repeat: prepend /usr/ucb to your PATH, then "make" >Fix: Mention this problem in the INSTALL docs. Admins using C 4.2 should make sure that /usr/ucb is not on their path, but /opt/SUNWspro/bin is, so "cc" can be found. After compile, do a "ldd httpd" and make sure that no /usr/ucblib stuff is there. %0 >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
