On Sat, 2008-09-20 at 18:23 -0700, Brian Dessent wrote:
> I don't see why you keep mentioning cross-compiling. The problem is not
> specific to cross compilation at all, it affects native use as well.
Thank you, Brian, I have sent your message to the macro author, so now
it is really easy for him
Mat?j Tý? wrote:
> Anyway, don't you think that the usability of AC_CHECK_LIB in the
> current form (not allowing inclusion of headers nor the precise
> specification of the function call) is quite low because of this calling
> convention issue?
I agree that something with the functionality of AC
On Sunday 21 September 2008 21:12:22 Matěj Týč wrote:
> Thank you, Brian, I have sent your message to the macro author, so
> now it is really easy for him to fix it for others as well.
Why don't you just adapt it yourself, to suit your own requirements?
That after all, is the underpinning of the
On Sun, 21 Sep 2008, Keith Marshall wrote:
This "calling convention issue" is specific to MS-Windows, which is a
*very* minor target platform for autoconf; indeed native MS-Windows
doesn't even provide a shell which is capable of running an autoconf
configure script.
not really (I've been bit
