New: host-module-init-tools 3.11 fails to build

https://bugs.busybox.net/show_bug.cgi?id=2479

Summary: host-module-init-tools 3.11 fails to build
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: nnazarenko at radiofid.ru
CC: buildroot at uclibc.org
Estimated Hours: 0.0

PATH=/home/savant/devel/irz/buildroot/output/host/bin:/home/savant/devel/irz/buildroot/output/host/usr/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/lib/perl5/core_perl/bin:/opt/qt/bin LD_LIBRARY_PATH="/home/savant/devel/irz/buildroot/output/host/usr/lib:"
PKG_CONFIG=""
PKG_CONFIG_LIBDIR="/home/savant/devel/irz/buildroot/output/host/usr/lib/pkgconfig"
PERLLIB="/home/savant/devel/irz/buildroot/output/host/usr/lib/perl"
/usr/bin/make -j4 -C
/home/savant/devel/irz/buildroot/output/build/host-module-init-tools-3.11/
make[1]: Entering directory
`/home/savant/devel/irz/buildroot/output/build/host-module-init-tools-3.11'
Makefile:15: *** recipe commences before first target. Stop.
make[1]: Leaving directory
`/home/savant/devel/irz/buildroot/output/build/host-module-init-tools-3.11'
make: ***
[/home/savant/devel/irz/buildroot/output/build/host-module-init-tools-3.11/.stamp_built]
Error 2

[savant at savant_devel buildroot]$ LC_ALL=C make -v GNU Make 3.82

OS: Archlinux

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

<snip>

<snip>

These three lines in output/build/host-module-init-tools-3.11/Makefile.am are causing the issue:

SGML
mandir
TESTSUITE

... vim highlights them in red, and changing them to '= foo' causes the build to kick off and fail when it gets to the SGML building stage.

I haven't figured out exactly how to change them to make them do as desired yet, but hopefully this saves someone a lot of work.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJMfSrZAAoJECSpOhdQESq63VMIAJXOLnbIkKBK3LkQ0VLPhZUk zMeQ3IApE7F06IejQLR05tryWzy20r9UGR6SHvXL3c3OLK073aAr2VTlnZa3kQ+c HzBVnmLPm6svrDlIxun86kxl3ERgM9JvCGdzU6/ISYcVnru3pBfM7abcOZnKWbij lvhCRycxPZdhph0cg7UvJ0IMqkse+asQfFtAcoI1spZO821DhCMI84C3hcPZLW7Y 2JpoIbHUfk0lPJ1sK0FO0WWkzPWCgJAe8VNH4vtFhZr6JzqMy5Sfbk+5JKI77nWt tlRhuh/baWMIibGYx4PcG1/2jR8pYt/OC0YrLMMuWexgj6w85BEX8qFyBHhujzI= =JUn+
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

em to make them do as

I forgot to mention that, after editing the aforementioned three lines, you need to delete the Makefile and do the following to generate new files with the modified Makefile.am lines:

aclocal
autoconf
automake

... then edit out line 1930 of the configure script, since it gives:

./configure: line 1930: syntax error near unexpected token build' ./configure: line 1930: AX_ENABLE_BUILDDIR(build)'

and then do a ./configure before running make in the top level directory

All of this is just to prove that those three lines cause the problem of course. Obviously once they are fixed properly all these hoops will not need to be jumped through.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJMfTAAAAoJECSpOhdQESq6DbkH+gN/BS2qMshsN8DJE08X70s0 l8iNEhXfEavycOYNuxF4rvx7bbiB+zKFEfIWPCsicD24xFmxJNN+lfoEIsZ5zjKR dmXfGu4BwPzB87d/RdJrLDLK45MyNrh5QjodEGCpJip8r8kNvcekEA9v/njixnvQ 79pwIVTRO+X9lxqUsSooGW40ao6tMoCbJSQp7QyGPzmvWeJYo5FmAHBWRftlyqFG cBo7bWlcx2DtyO6tVEngzrUC3+T+n4JvKu98DoQqEjyNNxKGGeEjs5SDXkO9aHH8 pwTIqWPqTBbzhbkUb2b556182j1UVIHGW9xZsb+i2UkfrzwsXqszdEQX3ZYx/G8= =lMg5
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In order to get past this until a fix is available upstream or someone here creates a patch to Makefile.am, one can disable the option to generate documentation for the host in the menuconfig, then rather than doing an option-less ./configure simply copy and paste the ./configure line from the failed make and do a make from the top level directory.

The result is that docs on the target won't be available, but since the other option is to have no target available at all this seems like a fair trade-off :-)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJMfUqbAAoJECSpOhdQESq6cZYH/jKyl9ldos8eHg8RtiHcgLTY hVT7dwmhPirOI/2miE348TVRPjZx1h7uquJMJFNKM+nm6HVOWc/qspq9CS2Mcbu1 8FX49uSX5mVYlFzXRO49/qVxPNNhTo+wVk26Ywq8g3hdzdrvenzfRLVx55M9lN3r 7eqULjDw09GiPQxKZnNYglh/P0OfEuyshfxfVIupnS8dqrVqKujqO1vxuAgnqNNk cM29JuAJcMsMVfmbFRi1iyoQLccjqyfEDrpT6y2barwPS6IEHl6budfjiBJ76Uzx bgC2hWUEClREBwPDavyTBSXIA2OPup4h8XHmaTj/+two04mq3EhI5lPs2tPLOdo= =VPPQ
-----END PGP SIGNATURE-----

https://bugs.busybox.net/show_bug.cgi?id=2479

--- Comment #1 from Nazarenko Nikita <[email protected]> --- Created attachment 2419
--> https://bugs.busybox.net/attachment.cgi?id=2419
fix for m4 script which generate broken configure script

This patch work for me, but I'm not sure in correctness

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=2479

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #2 from Thomas Petazzoni <[email protected]> --- This has been fixed by bumping module-init-tools 3.12. See
http://git.buildroot.net/buildroot/commit/?id=7be90dae8adc8d98b57dc4bc21630d8671523350

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.