On Mon, Aug 2, 2010 at 8:53 AM, Cyril Hrubis <[email protected]> wrote: > Hi! > I was trying to find a cause for very cryptic make errors and found that > I have colon somewhere in a path to the directory I was trying to > compile ltp in. Further examination showed that make is trying to > interpret all rules like: > > $(top_builddir)/include/mk/config.mk: > ... > > But found one more colon in $(top_builddir) and gets badly confused. > > Also space, semicolon and may be others does the same job, so we should > either escape all top_builddir, abs_builddir, SUBDIRS, ... variables or > get rid of rules that contains them.
I'm not going to spend the `time' to fix these `issues'. As Mike said, almost all autotools based projects (and I would argue almost all make based projects -- in particular the ones based on GNU make functions, use variables, etc) have this issue. There are more pressing issues with this project that need to be solved, because all of this can be explained down to the following simple rule: "Don't expect a project that uses Makefiles to function properly with paths that have colons, spaces, etc to function properly". Keep things as simple as possible and you won't have issues with building LTP :). Thanks, -Garrett ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
