[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: func_convert_file_cygwin_to_w32 woes

From: Peter Rosin
Subject: Re: func_convert_file_cygwin_to_w32 woes
Date: Sat, 01 Jan 2011 19:07:43 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20101207 Thunderbird/3.1.7

Den 2011-01-01 04:53 skrev Dan McMahill:
> I am trying to build a program under cygwin but using the mingw tool
> chain in a fake cross build way.  In my configure environment, I have:
>  export lt_cv_to_tool_file_cmd=func_convert_file_cygwin_to_w32
> as suggested by the libtool manual.  I'm using libtool 2.4.
> Everything goes smoothly until install time when libtool calls ranlib
> (the mingw one) on an absolute path and of course the cygwin absolute
> path doesn't make sense to the mingw ranlib.  I thought that's what the
> func_convert... bit was for.

It is. My guess is that you have hit a bug, unfortunately I'm drowning
in work at the moment, so it will be a while before I can have a deeper
look. Ranlib invocations are also pretty spread out so the fix might
be intrusive...

> A full understanding of libtool internals escapes me.  Is there
> something else I should be doing or can anyone suggest good ways to
> troubleshoot this?

I'm not sure, but maybe you can skip ranlib altogether? (i.e. try
RANLIB=: when you configure)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]