Quoting Patrice Dumas <[EMAIL PROTECTED]>: > > > What is the issue with space in the build path ?? > > path are not between quotes so that commands that copy from directory to > > another do not work correctly. > > cp /home/baud123/directory with spaces/file $DESTINATION > > does not work, when cp "/home/baud123/directory with spaces/file" > > $DESTINATION would work... > > Indeed, but where are such cp needed? There shouldn't be a need for > an absolute path to source dir, all the paths should be relative.
The makefile of the Linux kernel copy the eagle-usb.ko module in /lib/... And before that it makes something like this make -C $MODULEDIR build And if there is space... OUCH !!! > This patch adds support for use of xmlto instead of xsltproc (if found). > The echoing of warning message instead of error in case the documentation > isn't built is also in. I removed GEN_DOC, and instead use directly the > xslt program name (or no when not found) in XSLTPROGRAM. For me, xmlto is a front for xsltproc. It's a more high level program. "xmlto xml ..." is more simpler, but it's useless if we continue to use "xlstproc" when we don't find "xmlto". I propose to use always xmlto. > > > - the additional path in AC_CHECK_PROG when it is > > > "/bin:/usr/bin:/usr/local/bin" > > I don't understand this. > > There are pieces of code like > AC_CHECK_PROG(XSLTPROGRAM, xsltproc, xsltproc, "no", > "/bin:/usr/bin:/usr/local/bin") > > I don't think the additional path is usefull, it is even harmfull in case > the user a special PATH or avoid some directories in the PATH. I find this http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_node/autoconf_41.html By default, these macros use the environment variable PATH. If you need to check for a program that might not be in the user's PATH, you can pass a modified path to use instead, like this: AC_PATH_PROG([INETD], [inetd], [/usr/libexec/inetd], [$PATH:/usr/libexec:/usr/sbin:/usr/etc:etc]) And I think we must use impose autoconf >= 2.50 now. mcoolive.
