laboriousway 发表于 2006-3-27 14:03:52

求助:skyeye编译出错

我用了好几种版本的linux,编译时都出现以下错误,现在用的是fc4,
........
autoconf ./../unix/configure.in > ./../unix/configure
../unix/configure.in:187: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'
      If this token and others are legitimate, please use m4_p attern_allow.
      See the Autoconf documentation.
make: *** [../unix/configure] 错误? 1
make: Leaving directory `/opt/skyeye_insight/tcl/unix'
make: *** 错误? 2
make: Leaving directory `/opt/skyeye_insight/tcl'
make: *** 错误? 2
高手帮帮忙!

zhangyichi 发表于 2006-4-17 21:00:35

能把
../unix/configure.in:187: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'
If this token and others are legitimate, please use m4_p attern_allow.

能把那个 configure.in 文件贴出来吗?

你可以参考:autoconf 的文档自己搞定。
http://www.gnu.org/software/autoconf/manual/autoconf.pdf


15.6.4 AC_LIBOBJ vs. LIBOBJS

Up to Autoconf 2.13, the replacement of functions was triggered via the variable LIBOBJS.
Since Autoconf 2.50, the macro AC_LIBOBJ should be used instead (see Section 5.5.3 [Generic
Functions], page 46). Starting at Autoconf 2.53, the use of LIBOBJS is an error.
This change is mandated by the unification of the gnu Build System components. In
particular, the various fragile techniques used to parse a ‘configure.ac’ are all replaced
with the use of traces. As a consequence, any action must be traceable, which obsoletes
critical variable assignments. Fortunately, LIBOBJS was the only problem, and it can even
be handled gracefully (read, “without your having to change something”).
页: [1]
查看完整版本: 求助:skyeye编译出错