|I am getting frustrated as far as where to post - so here it is
I managed to convince "configure" that "host" is
pi@pi:~ $ sudo bash ./config.guess
as reported by "config.guess" running on RPi. No errors.
"checkinstall" now complains when I try to change the architecture to -A armv7l-unknown-linux-gnueabihf - which is whole point of this exercise!
dpkg: error processing archive /media/jim/DEV/BLUEZ/bluez-5.50/bluez_5.50-1_armv7l-unknown-linux-gnueabihf.deb (--install):
package architecture (armv7l-unknown-linux-gnueabihf) does not match system (amd64)
Errors were encountered while processing:
Of course the library file format is still wrong - as expected - nothing changed it
jim@jim-desktop:/usr/local/BLUEZ/bluez-5.50/lib$ file libbluetooth.so.3.18.16
libbluetooth.so.3.18.16: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=55d60353934d3672e2c88fbc64ceaba37c4d0442, not stripped
At this stage I have to ask -
assuming the documentation of "configure" IS CORRECT (?) - I should be able to change the "host" architecture BUT
how . where , by whom it is actually changed / processed ?
It sure looks as it is NOT being changed.
As soon as I resolve this , I can tackle the "checkinstall" complaint.
there is something strange in "configure" output
sudo ./configure --prefix=/usr/local/BLUEZ/bluez-5.50 --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var --enable-library --disable-systemd --host=armv7l-unknown-linux-gnueabihf
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for armv7l-unknown-linux-gnueabihf-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking how to create a pax tar archive... gnutar
checking for style of include used by make... GNU
checking for armv7l-unknown-linux-gnueabihf-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
The other note specifically said "use host to crosscomplie..."
modified 24-Mar-19 12:13pm.