On 15 Jan 2011, at 4:44, Matthew Mondor wrote: > At the end of the build:
> etags: not found > *** Error code 127 (ignored) > > For this first error, should ECL officially depend on etags, with > the configure script failing if it can't find it? Or should it be > optional, and not invoked if not previously detected as available? > In any case, this warning is not new and as so far been harmless. Maybe just add an explicit "this is harmless, no need to do anything" to the output? I build ECL seldom enough that I forget about this, and a few times looked for a fix only to find a note in the Makefile about it actually being harmless. Regards. -DS ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
