Click here to Skip to main content
14,666,918 members
Home » Discussions » Linux Programming
   

Linux Programming

 
QuestionHow to retrieve "terminal" output? Pin
Vaclav_17-May-19 7:26
MemberVaclav_17-May-19 7:26 
AnswerRe: How to retrieve "terminal" output? Pin
Richard MacCutchan17-May-19 9:27
mveRichard MacCutchan17-May-19 9:27 
QuestionTheoretical server/site setup Pin
pyango58-May-19 12:00
Memberpyango58-May-19 12:00 
QuestionSOLVED "configure" script option PKG_CONFIG_DEBUG_SPEW fails to run on X86 Pin
Vaclav_4-May-19 3:51
MemberVaclav_4-May-19 3:51 
I am trying to learn how to build a package (bluez) from source.
My main objective is to build a bluez library for ARM architecture so I can cross-compile my application on X86 architecture and run it (--host) on ARM.
For such purpose I option autotool generated “configure” script.
There is nothing special about “configure” options for cross-compiling– all “normal” options.
I have been making reasonable progress, but periodically running into “problems”.
Since “configure” is a product of autotools it has a nasty feature failing when debug code is inserted into wrong place.
BUT – one of the standard debugging “configure” options is to ADD environment variable(s) PKG_CONFIG_DEBUG_SPEW=set.
When it works it aids in debugging.
My “current problem” is – for unknown reason PKG_CONFIG_DEBUG_SPEW quit working on my X86 system.

So I installed fresh bluez on my ARM – Raspberry Pi 3B machine , and run plain “configure” with PKG_CONFIG_DEBUG_SPEW=set.
The “configure” script completed, so did “make” and “make install”.
All normal, no errors or issues.

I repeated the same – fresh install etc. on my X86 and got NO PKG_CONFIG_DEBUG_SPEW output.
I did check the config.log and it has the PKG_CONFIG_DEBUG_SPEW option “invoked”.


I suspect the “pkg-config” MAY be the problem, I do hope it is NOT my Ubuntu OS running on X86.
I did try to purge and reinstall “pkg-config” but run into too many dependencies.

I am attaching the actual output from "configure" where pkg-config is actually run
and PKG_CONFIG_DEBUG_SPEW is active


checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... PKG_CONFIG_DEBUG_SPEW variable enabling debug spew
Adding directory '/usr/local/lib/arm-linux-gnueabihf/pkgconfig' from PKG_CONFIG_PATH
Adding directory '/usr/local/lib/pkgconfig' from PKG_CONFIG_PATH
Adding directory '/usr/local/share/pkgconfig' from PKG_CONFIG_PATH
Adding directory '/usr/lib/arm-linux-gnueabihf/pkgconfig' from PKG_CONFIG_PATH
Adding directory '/usr/lib/pkgconfig' from PKG_CONFIG_PATH
Adding directory '/usr/share/pkgconfig' from PKG_CONFIG_PATH
Global variable definition 'pc_sysrootdir' = '/'
Global variable definition 'pc_top_builddir' = '$(top_builddir)'
no output option set, defaulting to --exists
Error printing disabled by default due to use of output options --exists, --atleast/exact/max-version, --list-all or no output option at all. Value of --print-errors: 1
Error printing enabled
yes
checking for C/C++ restrict keyword... __restrict


Any (reasonable) suggestion how to recover and get PKG_CONFIG_DEBUG_SPEW functioning on X86 would be greatly appreciated.

Cheers

SOLUTION

Reinstall "pkg-config" package.

modified 5-May-19 14:00pm.

GeneralRe: "configure" script option PKG_CONFIG_DEBUG_SPEW fails to run on X86 Pin
Richard MacCutchan4-May-19 4:56
mveRichard MacCutchan4-May-19 4:56 
Questionmissing mount.pc Pin
Vaclav_12-Apr-19 3:49
MemberVaclav_12-Apr-19 3:49 
AnswerRe: missing mount.pc Pin
Gerry Schmitz12-Apr-19 4:53
mveGerry Schmitz12-Apr-19 4:53 
GeneralRe: missing mount.pc Pin
Vaclav_12-Apr-19 7:53
MemberVaclav_12-Apr-19 7:53 
QuestionBad UDP length 736 > IP payload length Len = 728 packet drop Pin
sarali8-Apr-19 18:35
Membersarali8-Apr-19 18:35 
AnswerRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
Gerry Schmitz9-Apr-19 6:22
mveGerry Schmitz9-Apr-19 6:22 
AnswerRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
Randor 10-Apr-19 21:26
professional Randor 10-Apr-19 21:26 
GeneralRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
sarali12-Apr-19 20:43
Membersarali12-Apr-19 20:43 
GeneralRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
Randor 28-Apr-19 12:50
professional Randor 28-Apr-19 12:50 
GeneralRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
sarali10-May-19 2:55
Membersarali10-May-19 2:55 
PraiseRe: Bad UDP length 736 > IP payload length Len = 728 packet drop Pin
Randor 10-May-19 11:18
professional Randor 10-May-19 11:18 
QuestionActive PID Pin
Mohibur Rashid4-Apr-19 15:05
professionalMohibur Rashid4-Apr-19 15:05 
AnswerRe: Active PID Pin
Randor 4-Apr-19 15:57
professional Randor 4-Apr-19 15:57 
GeneralRe: Active PID Pin
Mohibur Rashid4-Apr-19 16:12
professionalMohibur Rashid4-Apr-19 16:12 
GeneralRe: Active PID Pin
Randor 4-Apr-19 16:23
professional Randor 4-Apr-19 16:23 
AnswerRe: Active PID Pin
k50544-Apr-19 16:29
mvek50544-Apr-19 16:29 
GeneralRe: Active PID Pin
Mohibur Rashid4-Apr-19 18:17
professionalMohibur Rashid4-Apr-19 18:17 
QuestionUsing "R CMD INSTALL ..." to install package Pin
Vaclav_1-Apr-19 14:41
MemberVaclav_1-Apr-19 14:41 
RantRe: Using "R CMD INSTALL ..." to install package Pin
k50542-Apr-19 4:50
mvek50542-Apr-19 4:50 
GeneralRe: Using "R CMD INSTALL ..." to install package Pin
Richard MacCutchan3-Apr-19 8:24
mveRichard MacCutchan3-Apr-19 8:24 
GeneralRe: Using "R CMD INSTALL ..." to install package Pin
k50543-Apr-19 10:51
mvek50543-Apr-19 10:51 

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.