Click here to Skip to main content
15,843,200 members
Home / Discussions / Linux Programming
   

Linux Programming

 
AnswerRe: Active PID Pin
Randor 4-Apr-19 16:57
professional Randor 4-Apr-19 16:57 
GeneralRe: Active PID Pin
Mohibur Rashid4-Apr-19 17:12
professionalMohibur Rashid4-Apr-19 17:12 
GeneralRe: Active PID Pin
Randor 4-Apr-19 17:23
professional Randor 4-Apr-19 17:23 
AnswerRe: Active PID Pin
k50544-Apr-19 17:29
mvek50544-Apr-19 17:29 
GeneralRe: Active PID Pin
Mohibur Rashid4-Apr-19 19:17
professionalMohibur Rashid4-Apr-19 19:17 
QuestionUsing "R CMD INSTALL ..." to install package Pin
Vaclav_1-Apr-19 15:41
Vaclav_1-Apr-19 15:41 
RantRe: Using "R CMD INSTALL ..." to install package Pin
k50542-Apr-19 5:50
mvek50542-Apr-19 5:50 
GeneralRe: Using "R CMD INSTALL ..." to install package Pin
Richard MacCutchan3-Apr-19 9:24
mveRichard MacCutchan3-Apr-19 9:24 
GeneralRe: Using "R CMD INSTALL ..." to install package Pin
k50543-Apr-19 11:51
mvek50543-Apr-19 11:51 
Questioncommand "/../" Pin
Vaclav_1-Apr-19 8:35
Vaclav_1-Apr-19 8:35 
AnswerRe: command "/../" Pin
k50541-Apr-19 10:17
mvek50541-Apr-19 10:17 
AnswerRe: command "/../" Pin
Eddy Vluggen1-Apr-19 10:35
professionalEddy Vluggen1-Apr-19 10:35 
GeneralRe: command "/../" Pin
Vaclav_1-Apr-19 15:32
Vaclav_1-Apr-19 15:32 
GeneralRe: command "/../" Pin
k50541-Apr-19 18:39
mvek50541-Apr-19 18:39 
GeneralRe: command "/../" Pin
Eddy Vluggen2-Apr-19 2:49
professionalEddy Vluggen2-Apr-19 2:49 
AnswerRe: command "/../" Pin
Richard MacCutchan1-Apr-19 22:24
mveRichard MacCutchan1-Apr-19 22:24 
GeneralRe: command "/../" Pin
Vaclav_2-Apr-19 4:26
Vaclav_2-Apr-19 4:26 
QuestionWhy lscpu returns BOTH 32 -bit , 64-bit ? Pin
Vaclav_1-Apr-19 6:47
Vaclav_1-Apr-19 6:47 
AnswerRe: Why lscpu returns BOTH 32 -bit , 64-bit ? Pin
Richard MacCutchan1-Apr-19 6:52
mveRichard MacCutchan1-Apr-19 6:52 
GeneralRe: Why lscpu returns BOTH 32 -bit , 64-bit ? Pin
Vaclav_1-Apr-19 7:42
Vaclav_1-Apr-19 7:42 
QuestionHow to "include / link " to libbluetooth-dev (package?) ? Pin
Vaclav_1-Apr-19 6:33
Vaclav_1-Apr-19 6:33 
AnswerRe: How to "include / link " to libbluetooth-dev (package?) ? Pin
Richard MacCutchan1-Apr-19 6:49
mveRichard MacCutchan1-Apr-19 6:49 
GeneralSOLVED Re: How to "include / link " to libbluetooth-dev (package?) ? Pin
Vaclav_1-Apr-19 7:42
Vaclav_1-Apr-19 7:42 
QuestionAnybody feels like dissecting / discussing "Linux" STANDARD "configure" script / file? Pin
Vaclav_27-Mar-19 11:31
Vaclav_27-Mar-19 11:31 
AnswerRe: Anybody feels like dissecting / discussing "Linux" STANDARD "configure" script / file? Pin
k505427-Mar-19 13:18
mvek505427-Mar-19 13:18 
1) the configure script is AUTOGENTERATED by the autoconf tool set. There's generally no good that can come from messing about in it.
2) I have told you several times use --host=arm-linux-gnueabihf.
From your post 3 days ago:
Quote:
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

Now, I would expect anyone paying any attention (and surely anyone who's as nit-picky as you seem to be) to think to themselves:
Hmm ... looks like the configure script is trying to use armv7l-unknown-linux-gnueabihf-gcc. That prefix is  what I supplied as the value of the --host argument.  I  don't have arm7l-unkown-linux-gneabihf-gcc on my system.  I do have, however arm-linux-gnueabihf-gcc - maybe I'll try --host=arm-linux-gneuabihf and see if that works.
And lo-and-behold configure completes, and you can start make. and wonder of wonders it uses arm-linux-gnueabihf-gcc, just like we want it too. Result!

BUT,BUT, and again BUT: until you've got the prerequisites (GLib, D-Bus) built for armhf make will fail anyway!

3) if you do some googling around for autoconf --target you should find information about the so called candian cross Cross-Compilation (automake). Take the time to read down to the bottom of the page. There it tells you that --target is used when compiling compiler tools i.e. ld, ar, as, etc (binutils) in a three-way cross-compilation. For example, when you are compiling binutils on an X86 to run on an armhf but will produce code for PowerPC. --target has NOTHING to do with cross compiling in the normal way. I have not tried it by suspect that since configure is AUTOGENERATED that the --target option always shows up in the script, whether its required or not.

Now, stop elephanting around.

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.