19 Mar
2012
19 Mar
'12
11:12 p.m.
On 03/19/2012 10:50 AM, Serghei Amelian wrote:
Hmm,
I wonder if the libtool.m4.in file may not be the problem? There is no
reference in libtool.m4.in at all concerning to_tool_file_cmd. Could this be the
problem?
10:51 nirvana:/mnt/nv1/home/chroot/david/build/src/tdeutils/admin> grep
to_tool_file_cmd *
libtool.m4:AC_CACHE_VAL(lt_cv_to_tool_file_cmd,
libtool.m4:lt_cv_to_tool_file_cmd=func_convert_file_noop
libtool.m4: lt_cv_to_tool_file_cmd=func_convert_file_msys_to_w32
libtool.m4:to_tool_file_cmd=$lt_cv_to_tool_file_cmd
libtool.m4:AC_MSG_RESULT([$lt_cv_to_tool_file_cmd])
libtool.m4:_LT_DECL([to_tool_file_cmd], [lt_cv_to_tool_file_cmd],
ltmain.sh: *,"$to_tool_file_cmd",*)
ltmain.sh: $to_tool_file_cmd "$1"
ltmain.sh: case $nm_file_list_spec~$to_tool_file_cmd in
Nothing in libtool.m4.in. I don't know if libtool.m4.in is even used since the
libtool.m4 is present, but this caught my eye looking around.
I'll report back on the kpowersave linker issue in the other thread :)
--
David C. Rankin, J.D.,P.E.
> Anybody
familiar with libtool know if this is a libtool problem or if
> this is a problem with the tdeutil code? If it is libtool, any
> work-arounds?
It seems like libtool can't execute g++