trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Re: [trinity-devel] libtool version - "Third Point in the Line"

From: "David C. Rankin" <drankinatty@...>
Date: Fri, 23 Mar 2012 10:54:07 -0500
On 03/22/2012 07:43 PM, David C. Rankin wrote:
> Confirmed,
>
>    Libtool version mismatch resulting in undeclared 'to_tool_file_cmd' is common
> to all tde modules requiring autoconf. With tdeaddons, after issuing:

   I have filed a bug report with gnu regarding the libtool issue and I'm 
currently working with the developer. So far, here is the initial response I 
have received:

 > It looks like this isn't getting set to the default in libtool.m4, but it's
 > strange that our test suite didn't notice (and that this is the first report
 > of it).
 >
 > Could you please send me a failing build log, and perhaps run a failing
 > libtool command with an added --debug flag (right after the 'libtool') and
 > send the output of that also.
 >
 > Then we can come up with a test that fails, right now it seems the fix is
 > something like:
 >
 > diff --git a/m4/libtool.m4 b/m4/libtool.m4
 > index 75bfdb4..45a988f 100644
 > --- a/m4/libtool.m4
 > +++ b/m4/libtool.m4
 > @@ -7862,6 +7862,9 @@ case $host in
 > ;;
 > esac
 > ;;
 > + * ) # unhandled hosts (and "normal" native builds)
 > + lt_cv_to_tool_file_cmd=func_convert_file_noop
 > + ;;
 > esac
 > ])
 > to_tool_file_cmd=$lt_cv_to_tool_file_cmd
 >
 >
 > Thanks,
 > Peter

   I'll keep you posted as I get more information.

-- 
David C. Rankin, J.D.,P.E.