On Sun, Nov 09, 2008 at 10:33:39PM +0100, Elimar Riesebieter wrote:
> * Lionel Elie Mamane [081109 22:10 +0100]
>> On Sun, Nov 09, 2008 at 10:07:22PM +0100, Elimar Riesebieter wrote:
>>> * Lionel Elie Mamane [081109 21:50 +0100]
>>>> On Sun, Nov 09, 2008 at 08:53:52PM +0100, Elimar Riesebieter wrote:
>>>>> * Lionel Elie Mamane [081109 15:10 +0100]
>>>>>> On Sun, Nov 09, 2008 at 02:29:58PM +0100, Elimar Riesebieter wrote:
>>>>>>> This runs fine here. So I don't know how to reproduce?
>>>>>> Does it run fine when run *twice*?
>>>>> Yes.
>>>> Do you have autoconf/automake/libtool installed in the environment
>>>> where you run it?
>>> Yes
>> Is it actually run during the build?
> Why?
Well, because on my system it is being run, which is the root of the
problem, as explained in a previous email. autoconf being run
regenerates a fresh configure, which overwrites the effect
debian/patches/configure_cross_compile.patch, which thus does not
unapply cleanly anymore.
> It isn't required by debian/rules.
But the file bibuild/Makefile runs it; I suppose these lines in it are
what runs it:
$(top_srcdir)/configure: $(am__configure_deps)
cd $(srcdir) && $(AUTOCONF)
triggered by
$(top_builddir)/config.status: $(top_srcdir)/configure
$(CONFIG_STATUS_DEPENDENCIES)
which might be triggerd by
Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
--
Lionel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
