On Sun, Aug 10, 2014 at 2:06 PM, Paul Fertser <fercer...@gmail.com> wrote: > Hi, > > On Sun, Aug 10, 2014 at 01:47:08PM +0200, Tormod Volden wrote: >> Thanks a lot for investigating this! I am Cc'ing the dfu-util list and >> preferably we move the conversation there. > > Releasing a dfu-util version with known-to-be-broken openmoko support > would be a real SHAME :/ > >> Can I ask you the favour to send me a lsusb -v dump both from runtime >> and dfu mode? it would be good to keep for reference and we have a >> device-logs folder for this. > > Attached. > >> > PS: regarding configure.ac, it's my strong enough impression that >> > MAINTAINER_MODE macro should be removed from there, it only adds >> > confusion and never does anything useful IMHO. >> >> I just searched a little for AM_MAINTAINER_MODE and I that see it has >> been debated a lot. Looks like some recommend >> AM_MAINTAINER_MODE([disabled]). Would that help? I don't know if it is >> needed by some distributors, this could be cargo-cult for what I know. > > Basically, non-maintainer mode means that autoconf doesn't create > rules to regenerate configure when configure.ac is changed. It's > supposed to benefit users who do not have autoconf installed but I can > hardly see how it can be so. If a user modifies configure.ac, he or > she clearly wants to have configure regenerated, so it's better to > have an error because of missing autoconf than to have the changes > silently ignored. So my conclusion was that the maintainer mode macro > should be removed altogether; this was done for OpenOCD about a year > ago, and the results were positive (consistent rules, less confusion). >
Thanks! I have pushed all this to git master. Best regards, Tormod _______________________________________________ devel mailing list devel@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/devel
