config/4371: Make fails because Ultrix "ar" truncates filenames (?)

[Nick Boyce <ni...@eds.com>]

>Number:         4371
>Category:       config
>Synopsis:       Make fails because Ultrix "ar" truncates filenames (?)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri May  7 14:10:01 PDT 1999
>Last-Modified:
>Originator:     nick.boyce@eds.com
>Organization:
apache
>Release:        1.3.6
>Environment:
Ultrix 4.4 on a DEC 5240 (MIPS) using DEC's "CC" compiler

uname -a = ULTRIX rccnx1 4.4 0 RISC
>Description:
The make trundles on for a while, displaying a large number of compiler warnings (which I've submitted just now as a separate PR), then at the end of the "src/modules/standard" section I see two filename-truncated errors (?) reported by "ar" after which the make is abandoned.

Here's an extract from the make :-

[snip]
...
===> src/modules
===> src/modules/standard
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_env.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_log_config.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_mime.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_negotiation.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_status.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_include.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_autoindex.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_dir.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_cgi.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_asis.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_imap.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_actions.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_userdir.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_alias.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_access.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_auth.c
cc -c  -I../../os/unix -I../../include   -DULTRIX -std -DUSE_HSREGEX `../../apaci` mod_setenvif.c
rm -f libstandard.a
ar cr libstandard.a mod_env.o mod_log_config.o mod_mime.o mod_negotiation.o mod_
status.o mod_include.o mod_autoindex.o mod_dir.o mod_cgi.o mod_asis.o mod_imap.o
 mod_actions.o mod_userdir.o mod_alias.o mod_access.o mod_auth.o mod_setenvif.o 
ar: Info: filename mod_log_config.o truncated to mod_log_config.
ar: Info: filename mod_negotiation.o truncated to mod_negotiation
ranlib libstandard.a
<=== src/modules/standard
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.
>How-To-Repeat:
Just make Apache 1.3.6 on Ultrix 4.4 with *no* SSL or other additional modules
>Fix:
No, but I checked the man page for this machine's "ar", and it seems that it is intended to truncate filenames to 15 characters - is this normal !?!  Here's an extract :

  RISC                                                                 ar(1)

    Restrictions
    If you specify the same file twice in an argument list, it can appear
    twice in the archive file.

    The -o option does not change the last-modified date of a file unless
    you own the extracted file or you are the superuser.

    This command truncates filenames to 15 characters.

  Files
    /tmp/v*    temporaries

  See Also
    lorder(1), ld(1), ranlib(1), ar(5)

Do I need to get a replacement "ar" ?
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]