-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stepan Kasal <[EMAIL PROTECTED]> writes:
> On Fri, Dec 31, 2004 at 03:09:21PM -0800, J.T. Conklin wrote:
>> While AC_CONFIG_PKGCONFIG_IN() is very appealing, writing a script
>> that takes similar arguments and generates a *.pc.in file that can
>
> if
Hi,
On Fri, Dec 31, 2004 at 03:09:21PM -0800, J.T. Conklin wrote:
> While AC_CONFIG_PKGCONFIG_IN() is very appealing, writing a script
> that takes similar arguments and generates a *.pc.in file that can
if understand your situation correctly, you can still use
AC_CONFIG_PKGCONFIG_IN to get the *
>>> "J" == J T Conklin <[EMAIL PROTECTED]> writes:
J> There appears to be no way to tell automake that a
J> AC_CONFIG_FILE file will be generated earlier in the configure script,
[...]
J> it seems like you're saying that there was a bug which has
J> long been fixed.
My bad. I though you were
Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> jtc> I've since learned that the problem isn't in autoconf, but in
> jtc> automake.
>
> It was. More than one year ago.
Perhaps I'm misunderstanding your response, but it seems like you're
saying that there was a bug which has long been fixed.
>>> "J" == J T Conklin <[EMAIL PROTECTED]> writes:
J> I've since learned that the problem isn't in autoconf, but in
J> automake.
It was. More than one year ago.
--
Alexandre Duret-Lutz
Hi Stepan,
The solution is to not list the file in the list of files to be configured.
Instead, in your Makefile.am:
mumble-sh.in : $(mumble_PREDECESSORS)
create-mumble-sh-in
mumble.sh : mumble-sh.in
$(SHELL) $(top_builddir)/config.status --file mumble.sh:mumble-sh.in
Someon
Bruce Korb <[EMAIL PROTECTED]> writes:
>> However, if I add foo.pc to AC_CONFIG_FILES, autoconf complains that
>> foo.pc.in does not exist (which it does not). However, if I omit it,
>> foo.pc.in is generated at configure-time, but foo.pc is not.
>>
>> Does anyone have any clue how to use this ma
Stepan Kasal <[EMAIL PROTECTED]> writes:
> On Thu, Dec 30, 2004 at 08:19:41PM -0800, J.T. Conklin wrote:
>> However, if I add foo.pc to AC_CONFIG_FILES, autoconf complains that
>> foo.pc.in does not exist (which it does not). However, if I omit it,
>> foo.pc.in is generated at configure-time, but
Sorry to follow-up to myself, but with a little help from autoreconf's
-verbose flag I just figured out that this may be failing in automake,
not autoconf. The underlying problem remains.
--jtc
[EMAIL PROTECTED] (J.T. Conklin) writes:
> Roger Leigh's AC_CONFIG_PKGCONFIG_IN macro from the aut
