Received: (qmail 19340 invoked by uid 2012); 1 Feb 1999 21:53:39 -0000 Message-Id: <19990201215339.19339.qmail@hyperreal.org> Date: 1 Feb 1999 21:53:39 -0000 From: Joe Hohertz Reply-To: jhohertz@golden.net To: apbugs@hyperreal.org Subject: make install pukes on make install-data in tar X-Send-Pr-Version: 3.2 >Number: 3809 >Category: os-bsdi >Synopsis: make install pukes on make install-data in tar >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Feb 1 15:10:00 PST 1999 >Last-Modified: Tue Apr 20 21:44:40 PDT 1999 >Originator: jhohertz@golden.net >Organization: >Release: 1.3.4 (maybe others?) >Environment: This is BSDI 4.0, using all the default tools supplied. (Except perhaps perl, updated to 5.004_04) >Description: This is a really silly, stupid problem, which is thankfully easy to fix (I think) The problem is that BSDI's tar does NOT support the -h flag, which the Makefile.tmpl has hard-coded within. The causes apache to build just fine, but give an error on install. This is just one of those annoying little quirks that makes a package look poorly assembled, which really bugs me because I know in my heart that apache is by far the most superior web server available. I've flagged this as critical because it makes apache look poor, when I think it should look to be the best there is. >How-To-Repeat: Download apache 1.3.4 tarfile to BSDI 4.0 box. Untar. cd apache-1.3.4 ./configure --prefix=/usr/local/apache make make install On the last command, you will see tar complain and halt the install >Fix: Uhm.... stick the tar flags in a variable, say... TAR_FLAGS and have the autoconf fill in an appropriate value based on target platform. >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: dgaudet State-Changed-When: Tue Apr 20 21:44:40 PDT 1999 State-Changed-Why: looks like this was fixed in 1.3.6. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include 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! ]