Click here to Skip to main content
14,332,463 members

Linux Programming

 
GeneralRe: linker error file not recognized: File format not recognized Pin
Vaclav_23-Mar-19 6:48
memberVaclav_23-Mar-19 6:48 
GeneralRe: linker error file not recognized: File format not recognized Pin
Richard MacCutchan23-Mar-19 7:15
protectorRichard MacCutchan23-Mar-19 7:15 
GeneralRe: linker error file not recognized: File format not recognized Pin
Vaclav_23-Mar-19 10:50
memberVaclav_23-Mar-19 10:50 
GeneralRe: linker error file not recognized: File format not recognized Pin
k505423-Mar-19 8:16
memberk505423-Mar-19 8:16 
GeneralRe: linker error file not recognized: File format not recognized Pin
Vaclav_23-Mar-19 10:38
memberVaclav_23-Mar-19 10:38 
GeneralRe: linker error file not recognized: File format not recognized Pin
k505423-Mar-19 11:35
memberk505423-Mar-19 11:35 
GeneralRe: linker error file not recognized: File format not recognized Pin
Vaclav_23-Mar-19 16:32
memberVaclav_23-Mar-19 16:32 
GeneralChange package architecture - no go Pin
Vaclav_24-Mar-19 5:45
memberVaclav_24-Mar-19 5:45 
I am getting frustrated as far as where to post - so here it is
Progress report

I managed to convince "configure" that "host" is

pi@pi:~ $ sudo bash ./config.guess
armv7l-unknown-linux-gnueabihf


as reported by "config.guess" running on RPi. No errors.

However,
"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:
 /media/jim/DEV/BLUEZ/bluez-5.50/bluez_5.50-1_armv7l-unknown-linux-gnueabihf.deb







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.





Addendum
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.

GeneralRe: Change package architecture - no go Pin
k505424-Mar-19 8:34
memberk505424-Mar-19 8:34 
GeneralRe: Change package architecture - no go Pin
Vaclav_24-Mar-19 13:24
memberVaclav_24-Mar-19 13:24 
GeneralRe: Change package architecture - no go Pin
k505424-Mar-19 14:38
memberk505424-Mar-19 14:38 
GeneralRe: Change package architecture - no go Pin
k505424-Mar-19 9:49
memberk505424-Mar-19 9:49 
GeneralRe: Change package architecture - no go Pin
Vaclav_25-Mar-19 6:12
memberVaclav_25-Mar-19 6:12 
GeneralRe: Change package architecture - no go Pin
k505425-Mar-19 7:30
memberk505425-Mar-19 7:30 
GeneralRe: linker error file not recognized: File format not recognized Pin
Member 1419936827-Mar-19 1:12
memberMember 1419936827-Mar-19 1:12 
GeneralRe: linker error file not recognized: File format not recognized Pin
Vaclav_27-Mar-19 3:15
memberVaclav_27-Mar-19 3:15 
GeneralRe: linker error file not recognized: File format not recognized Pin
Richard Deeming27-Mar-19 5:37
mveRichard Deeming27-Mar-19 5:37 
AnswerRe: SOLVED ??? linker error file not recognized: File format not recognized Pin
k505426-Mar-19 8:15
memberk505426-Mar-19 8:15 
GeneralRe: SOLVED ??? linker error file not recognized: File format not recognized Pin
Vaclav_26-Mar-19 9:44
memberVaclav_26-Mar-19 9:44 
GeneralRe: SOLVED ??? linker error file not recognized: File format not recognized Pin
k505426-Mar-19 11:41
memberk505426-Mar-19 11:41 
GeneralRe: SOLVED ??? linker error file not recognized: File format not recognized Pin
Vaclav_26-Mar-19 16:24
memberVaclav_26-Mar-19 16:24 
GeneralUsing virtualbox to load Debian OS Pin
Vaclav_27-Mar-19 3:23
memberVaclav_27-Mar-19 3:23 
GeneralRe: Using virtualbox to load Debian OS Pin
k505427-Mar-19 5:05
memberk505427-Mar-19 5:05 
GeneralRe: Using virtualbox to load Debian OS Pin
Vaclav_27-Mar-19 5:32
memberVaclav_27-Mar-19 5:32 
GeneralRe: Using virtualbox to load Debian OS Pin
k505427-Mar-19 6:25
memberk505427-Mar-19 6:25 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.