Hey Mark, The reason I disabled autoheader was because autoheader was failing during autoreconf due to missing templates for certain macros. Since autoheader isn't necessary here anyway, I disabled it per the instruction in DH_AUTORECONF(1), which says to set the environment variable of any part of autoreconf to "true" if you don't want it to be run (as it will just execute "true" and move on).
Per your point about the architecture, it has been proposed<https://lists.debian.org/debian-powerpc/2013/09/msg00045.html>, and libtool has been updated to support it in Debian<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726404> . Hope this helps! Please let me know if you have any further questions/requests for clarification. Logan On Tue, Feb 4, 2014 at 8:04 AM, Mark Brown <broo...@debian.org> wrote: > severity 737337 wishlist > kthxbye > > On Sat, Feb 01, 2014 at 03:24:01PM -0500, Logan Rosen wrote: > > > In Ubuntu, the attached patch was applied to achieve the following: > > > > * Use dh-autoreconf to also fix FTBFS on ppc64el. > > * Disable autoheader to fix FTBFS during autoreconf. > > * Use system libtool, and build-depend on it accordingly. > > * Use autotools-dev dh helper instead of copying files manually. > > I need more explanation for this, especially for the second item - > you've not provided any information on what the problems are (such as > the error messages) so it's hard to evaluate if this is a good set of > fixes. > > > +export AUTOHEADER = true > > This looks odd for example and doesn't seem to tie in with what you say > above. > > I've also lowered the severity to wishlist since this architecture > hasn't even been proposed for Debian as far as I can tell. >
