[PATCH] Pass Autom4te path down to programs that autoreconf invokes.

2009-10-26 Thread Paolo Bonzini
* bin/autoreconf.in (autom4te): New variable. Export its value as $ENV{'AUTOM4TE'}. Suggested by Peter Johansson. * THANKS: Update. --- Like this? ChangeLog |7 +++ THANKS|1 + bin/autoreconf.in |2 ++ 3 files changed, 10 insertions(+), 0

Re: [PATCH] Pass Autom4te path down to programs that autoreconf invokes.

2009-10-26 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Paolo Bonzini on 10/26/2009 10:20 AM: * bin/autoreconf.in (autom4te): New variable. Export its value as $ENV{'AUTOM4TE'}. Suggested by Peter Johansson. * THANKS: Update. --- Like this? Yep, that looks like it will do the

AC_SEARCH_LIBS and non-cdecl calling conventions (was: pkg-config wisdom)

2009-10-26 Thread Ralf Wildenhues
* Matěj Týč wrote on Sun, Oct 25, 2009 at 03:05:26PM CET: There is one big issue with AC_SEARCH_LIBS: If you use a different calling convention than cdecl (like stdcall, but I don't know, they've just told me), you will get unresolved symbols if you try to link without a proper include file

Re: [autoconf] Re: pkg-config wisdom

2009-10-26 Thread Tim Post
On Fri, 2009-10-23 at 12:36 +0900, mpsuz...@hiroshima-u.ac.jp wrote: * Their custom built library is not used, the system's is. Indeed. It might be popular when default pkg-config prefix is differnt from the prefix that users install their own libraries. Have you experienced the troubles

Re: pkg-config wisdom

2009-10-26 Thread Tim Post
On Sun, 2009-10-25 at 11:07 -1000, William Pursell wrote: Alfred M. Szmidt wrote: pkg-config is broken because it checks for the existance of libraries, and not for the features that are required for the program to run. It does not even check for the existence of

Re: pkg-config wisdom

2009-10-26 Thread Tim Post
On Mon, 2009-10-26 at 12:28 +1100, Russell Shaw wrote: William Pursell wrote: Alfred M. Szmidt wrote: pkg-config is broken because it checks for the existance of libraries, and not for the features that are required for the program to run. It does not even check for the existence of

Re: pkg-config wisdom

2009-10-26 Thread John Calcote
Matěj, On 10/25/2009 8:05 AM, Matěj Týč wrote: There is one big issue with AC_SEARCH_LIBS: If you use a different calling convention than cdecl (like stdcall, but I don't know, they've just told me), you will get unresolved symbols if you try to link without a proper include file (or something

AC_SEARCH_LIBS and non-cdecl calling conventions (was: pkg-config wisdom)

2009-10-26 Thread Ralf Wildenhues
Hello, * John Calcote wrote on Mon, Oct 26, 2009 at 05:46:07PM CET: On 10/25/2009 8:05 AM, Matěj Týč wrote: There is one big issue with AC_SEARCH_LIBS: If you use a different calling convention than cdecl (like stdcall, but I don't know, they've just told me), you will get unresolved symbols