syntax error

[gorskiy69]

At compilation I receive the following error:

../configure: line 1892: syntax error near unexpected token `foreign'
../configure: line 1892: `AM_INIT_AUTOMAKE(foreign subdir-objects -Wall -Werror)'
** Error: Configure failed
** Error: image build exited
** Error: reboot to resume the build



Reboot does not help. How to fix this problem?

[Tim Curtis]

You will have to post more of the log to determine whats being compiled and why the .configure might be failing.
Also what model Pi are you running the Build on?

[gorskiy69]

Raspberry Pi3 B

/bin/mkdir -p '/usr/bin'
/bin/bash ./libtool --mode=install /usr/bin/install -c client/bluetoothctl monitor/btmon tools/rctest tools/l2test tools/l2ping tools/bccmd tools/bluemoon tools/hex2hcd tools/mpris-proxy tools/btattach '/usr/bin'
libtool: install: /usr/bin/install -c client/bluetoothctl /usr/bin/bluetoothctl
libtool: install: /usr/bin/install -c monitor/btmon /usr/bin/btmon
libtool: install: /usr/bin/install -c tools/rctest /usr/bin/rctest
libtool: install: /usr/bin/install -c tools/l2test /usr/bin/l2test
libtool: install: /usr/bin/install -c tools/l2ping /usr/bin/l2ping
libtool: install: /usr/bin/install -c tools/bccmd /usr/bin/bccmd
libtool: install: /usr/bin/install -c tools/bluemoon /usr/bin/bluemoon
libtool: install: /usr/bin/install -c tools/hex2hcd /usr/bin/hex2hcd
libtool: install: /usr/bin/install -c tools/mpris-proxy /usr/bin/mpris-proxy
libtool: install: /usr/bin/install -c tools/btattach /usr/bin/btattach
/bin/mkdir -p '/usr/libexec/bluetooth'
/bin/bash ./libtool --mode=install /usr/bin/install -c src/bluetoothd obexd/src/obexd '/usr/libexec/bluetooth'
libtool: install: /usr/bin/install -c src/bluetoothd /usr/libexec/bluetooth/bluetoothd
libtool: install: /usr/bin/install -c obexd/src/obexd /usr/libexec/bluetooth/obexd
/bin/mkdir -p '/usr/lib/cups/backend'
/bin/bash ./libtool --mode=install /usr/bin/install -c profiles/cups/bluetooth '/usr/lib/cups/backend'
libtool: install: /usr/bin/install -c profiles/cups/bluetooth /usr/lib/cups/backend/bluetooth
/bin/mkdir -p '/etc/dbus-1/system.d'
/usr/bin/install -c -m 644 src/bluetooth.conf '/etc/dbus-1/system.d'
/bin/mkdir -p '/usr/share/dbus-1/services'
/usr/bin/install -c -m 644 obexd/src/org.bluez.obex.service '/usr/share/dbus-1/services'
/bin/mkdir -p '/usr/share/dbus-1/system-services'
/usr/bin/install -c -m 644 src/org.bluez.service '/usr/share/dbus-1/system-services'
/bin/mkdir -p '/usr/include/bluetooth'
/usr/bin/install -c -m 644 lib/bluetooth.h lib/hci.h lib/hci_lib.h lib/sco.h lib/l2cap.h lib/sdp.h lib/sdp_lib.h lib/rfcomm.h lib/bnep.h lib/cmtp.h lib/hidp.h '/usr/include/bluetooth'
/bin/mkdir -p '/usr/share/man/man1'
/usr/bin/install -c -m 644 tools/rctest.1 tools/l2ping.1 tools/bccmd.1 tools/btattach.1 tools/hid2hci.1 '/usr/share/man/man1'
/bin/mkdir -p '/usr/share/man/man8'
/usr/bin/install -c -m 644 src/bluetoothd.8 '/usr/share/man/man8'
/bin/mkdir -p '/usr/lib/pkgconfig'
/usr/bin/install -c -m 644 lib/bluez.pc '/usr/lib/pkgconfig'
/bin/mkdir -p '/lib/udev/rules.d'
/usr/bin/install -c -m 644 tools/97-hid2hci.rules '/lib/udev/rules.d'
/bin/mkdir -p '/lib/systemd/system'
/usr/bin/install -c -m 644 src/bluetooth.service '/lib/systemd/system'
/bin/mkdir -p '/usr/lib/systemd/user'
/usr/bin/install -c -m 644 obexd/src/obex.service '/usr/lib/systemd/user'
/bin/mkdir -p '/lib/udev'
/bin/bash ./libtool --mode=install /usr/bin/install -c tools/hid2hci '/lib/udev'
libtool: install: /usr/bin/install -c tools/hid2hci /lib/udev/hid2hci
** Delete symlink and bin for old bluetoothd
** Create symlink for new bluetoothd
** Compile bluez-alsa
Archive: bluez-alsa-master-88aefee.zip
88aefeea56b7ea20668796c2c7a8312bf595eef4
replace bluez-alsa-master/.gitignore? [y]es, [n]o, [A]ll, [N]one, [r]ename: NULL
(EOF or read error, treating as "[N]one" ...)
Ignore warnings from autoreconf and configure
mkdir: cannot create directory ‘build’: File exists
../configure: line 1892: syntax error near unexpected token `foreign'
../configure: line 1892: `AM_INIT_AUTOMAKE(foreign subdir-objects -Wall -Werror)'
** Error: Configure failed
** Error: image build exited
** Error: reboot to resume the build

[Tim Curtis]

Very odd.

You could try the two deletes below, then reboot but if same failure occurs then I would just start from scratch.

Code:

sudo rm -rf /home/pi/mosbuild/bluez-alsa-master
sudo rm /home/pi/mosbuild/bluez-alsa-master-88aefee.zip

[TheOldPresbyope]

Raspberry Pi3 B

...
Archive:  bluez-alsa-master-88aefee.zip
88aefeea56b7ea20668796c2c7a8312bf595eef4
replace bluez-alsa-master/.gitignore? [y]es, [n]o, [A]ll, [N]one, [r]ename:  NULL
(EOF or read error, treating as "[N]one" ...)
Ignore warnings from autoreconf and configure
mkdir: cannot create directory ‘build’: File exists
../configure: line 1892: syntax error near unexpected token `foreign'
../configure: line 1892: `AM_INIT_AUTOMAKE(foreign subdir-objects -Wall -Werror)'
** Error: Configure failed
** Error: image build exited
** Error: reboot to resume the build

@gorskiy69

I believe this error occurs because configuration files for bluez-alsa are left over from a previous, failed build. The conventional (e.g., Google) wisdom is to use "autoreconf -i" followed by "configure" to fix this but I don't know how this wisdom fits in with the automated moOde OS builder.

What happened the first time through the build? I've never had a failure in the bluez/bluez-alsa step.

Regards,
Kent

[gorskiy69]

Very odd.

You could try the two deletes below, then reboot but if same failure occurs then I would just start from scratch.

Code:

sudo rm -rf /home/pi/mosbuild/bluez-alsa-master
sudo rm /home/pi/mosbuild/bluez-alsa-master-88aefee.zip

Yes, it helped