Click here to Skip to main content
14,304,561 members

Linux Programming

 
GeneralRe: linker error file not recognized: File format not recognized Pin
Richard MacCutchan22-Mar-19 22:53
protectorRichard MacCutchan22-Mar-19 22:53 
GeneralRe: linker error file not recognized: File format not recognized Pin
Vaclav_23-Mar-19 5:10
memberVaclav_23-Mar-19 5:10 
GeneralRe: linker error file not recognized: File format not recognized Pin
Richard MacCutchan23-Mar-19 5:36
protectorRichard MacCutchan23-Mar-19 5:36 
GeneralRe: linker error file not recognized: File format not recognized Pin
k505423-Mar-19 5:51
memberk505423-Mar-19 5:51 
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 
where did this come from? Your X86 or your PI?
sudo dpkg  -l "bluez"
[sudo] password for jim: 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
ii  bluez:armhf    5.50-1       armhf        bluez-5.50
Are you building a .deb package on the X86 and installing it there? If so then presumably you might also have libbluetooth and libbluetooth-dev packages that you could install also which reduce the pain you're going through.
Vaclav_ wrote:
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu

From configure --help
System types:
  --build=BUILD     configure for building on BUILD [guessed]
  --host=HOST       cross-compile to build programs to run on HOST [BUILD]
If you don't specify --host, the default is the same as for --build (which configure will guess at using config.guess. For a PI, the host should be
arm-linux-gnueabihf
I think I figured that out because I tried something like host=arm7 and you get a configure error saying something like arm7-gcc not found.

You do realize that you're going down a rabbit hole, trying to do this via cross-compilation. In order to build bluez, you'll need to have all the prerequisites:
In order to compile Bluetooth utilities you need following software packages:
        - GCC compiler
        - GLib library
        - D-Bus library
        - udev library (optional)
        - readline (command line clients)
So you'll need to build all those for arm before you can build bluez --- and those probably have dependencies, etc, etc, etc. After each package is build and installed you'll need to figure out how to tell successive packages where to find their dependencies. That might be as simple as something like adding --with-glib=<path-to-armhf-glib> to the configure command line, or you may have to use make's CFLAGS (C compiler flags), CPPFLAGS (c-pre-prossor flags e.g -I<path>), CXXFLAGS (C++ flags), LDFLAGS (linker flags e.g -L<path>), LDLIBS (linker libraries e.g -l<lib>) environment varialbes. Also see configure --help. At the end there's a long list of environment variables you can set to tell configure where to find things. To set those you can either
$ export CPPFLAGS=-I/usr/local/arm/inlcude
$ export LDFLAGS=-L/usr/local/arm/lib
$ export LDLIBS=-lglib -ldbus -ludev
$ ./configure <args>
or
$ CPPFLAGS=-I/usr/local/arm \
      LDFLAGS=-L/usr/local/arm/lib \
      LDLIBS="-lglib -ldbus -ludev" \ 
      ./configure <args>

Vaclav_ wrote:
I guess learn how to edit "configure " is my real option.


Almost nobody ever edits configure files. They are generated by the autom4te, autoconf, and automake tools. I've not used them myself, so I can't tell you much about how they work. But there's plenty of reading if you google for it.
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 
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 

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.