Re: Packaging a library that requires cross-compiled code
On Wed, Oct 03, 2007 at 01:13:34AM -0500, Manoj Srivastava wrote:
> I don't think canard means what you think it mean: all my
> packages treat .ac files exactly like they treat .c files; and this
> factual statement blows “canard” out of the water.
Really, so your package runs ./configure and $(MAKE) and then runs .ac
files through gcc to produce .o files?
> I have not had any issues with regenerating all autoconf files
> during ./debian/rules configure phase. Do people have examples of
> packages where this currently fails?
It should fail for fakeroot, as that uses libtool features not present
in unstable.
Reply to: