Re: [Mingw-users] mingw64

From: Ralf Wildenhues <Ralf(dot)Wildenhues(at)gmx(dot)de>
To: MinGW Users List <mingw-users(at)lists(dot)sourceforge(dot)net>
Cc: "mingw-w64-public(at)lists(dot)sourceforge(dot)net" <mingw-w64-public(at)lists(dot)sourceforge(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [Mingw-users] mingw64
Date: 2011-02-12 10:10:31
Message-ID: 20110212101031.GE3799@gmx.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, and sorry for the delay,

* Peter Rosin wrote on Sat, Jan 29, 2011 at 02:26:24PM CET:
> Or is plain 'ar' used somewhere instead of 'x86_64-w64-mingw32-ar'?

Automake outputs 'AR = ar' in Makefile.in for rules creating old
libraries iff neither AC_PROG_LIBTOOL nor another method to define
AR correctly is used in configure.ac.

So this issue concerns packages using Automake but not using Libtool.

I figured with AM_PROG_AR eventually being needed anyway that would fix
this in one go ...

A good workaround, as already mentioned, is to use this in configure.ac:
AC_CHECK_TOOL([AR], [ar], [false])

Cheers,
Ralf

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Urbański 2011-02-12 10:58:39 Re: pl/python explicit subtransactions
Previous Message Alex Hunsaker 2011-02-12 09:18:36 Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding.