general/5855: Poor error reporting when libtoolize not in path during ./buildconf

[Jeff Godin <je...@tcnet.org>]

>Number:         5855
>Category:       general
>Synopsis:       Poor error reporting when libtoolize not in path during ./buildconf
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Mar 10 17:20:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     jeff@tcnet.org
>Release:        2.0a1
>Organization:
apache
>Environment:
Linux host.example.org 2.2.13 #2 Mon Nov 29 11:02:22 EST 1999 i686 unknown
redhat-release-6.1-1

>Description:

When running ./buildconf from within the src directory, and libtoolize is not in the current path, error reporting could use some help. Minor issue, but could be confusing for some. 

[jeff@host src]$ ./buildconf
dirname: too few arguments
Try `dirname --help' for more information.
make[1]: *** No rule to make target `/../share/aclocal/libtool.m4', needed by `aclocal.m4'.  Stop.
make: *** [all] Error 2
>How-To-Repeat:
Attempt to run ./buildconf without libtoolize in the current path.
>Fix:
Perhaps add some error checking in src/build/build.mk near:

generated_lists:
        @echo config_m4_files = `find . -name config.m4` > $@
        @n=`helpers/PrintPath libtoolize`; echo libtool_prefix = `dirname $$n`/.. >> $@
>Release-Note:
>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 make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database 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!     ]