GLIB, GCC, dpkg, pkg-config, bluez cross-compile env questions thread

I need to specify PKG_CONFIG_PATH to Glib package.


EDITED

yes - whereis works just fine

still like to know why I am getting conflicting info

END OF EDIT




I do not know how to find such path , however , I am also getting conflicting info about the Glib-2.0 package.

Could somebody help me in specifying / finding the package path and also explain to me why I am getting conflicting info about the package?

Will appreciate help very much.

jim@jim-desktop:~$ pkg-config --list-all | grep glib
glib-sharp-2.0                 GLib - GLib
spice-client-glib-2.0          spice-client-glib-2.0 - SPICE Client GLib 2.0 library
glib-2.0                       GLib - C Utility Library exists here 
dbus-sharp-glib-2.0            Managed DBus GLib integration - GLib integration for dbus-sharp, the D-Bus IPC library
gio-unix-2.0                   GIO unix specific APIs - unix specific headers for glib I/O library
glibmm-2.4                     glibmm - C++ wrapper for GLib
gio-2.0                        GIO - glib I/O library


jim@jim-desktop:~$ dpkg -l "glib*"
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  glib-networkin 2.48.2-1~ubu amd64        network-related giomodules for GL
ii  glib-networkin 2.48.2-1~ubu all          network-related giomodules for GL
ii  glib-networkin 2.48.2-1~ubu amd64        network-related giomodules for GL
un  glibc-doc      <none>       <none>       (no description available)

no glib-2.0 detected here 
jim@jim-desktop:~$

Use strace to find out:

$ strace pkg-config --cflags glib-2.0 2>&1 | grep 'open.*glib-2.0.pc' 
open("/usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc", O_RDONLY) = 3

then dpkg -S to determine the package

$ dpkg -S /usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc
libglib2.0-dev: /usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc

Note dpkg -l trends to truncate the package-names, unless you trick it:

COLUMNS=2000 dpkg -l '*glib*' | cut -b1-40

Originally Posted by NevemTeve Use strace to find out: $ strace pkg-config --cflags glib-2.0 2>&1 | grep 'open.*glib-2.0.pc' open("/usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc", O_RDONLY) = 3 then dpkg -S to determine the package $ dpkg -S /usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc libglib2.0-dev: /usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc Note dpkg -l trends to truncate the package-names, unless you trick it: COLUMNS=2000 dpkg -l '*glib*' | cut -b1-40

Thanks very much for reply.
I followed your suggestions and "found" glib-2.0.pc in same path.

I must be missing something since I am still getting stuff like this

jim@jim-desktop:~$ sudo dpkg -p 'glib-2.0'
dpkg-query: package 'glib-2.0' is not available

At this point I feel it would be the best to "reinstall" - I had success doing so for "pkg-config".
( I am still not sure why I am having these issues - most likely "user error.)

I am still having trouble understanding the relations between "package name" and "installing " all these "x-dev" libraries.

I did add the /usr/lib/x86_64-linux-gnu/pkgconfig path to the "configure" options, but due to the above it still fails.


Many thanks for your help, appreciate it.

Good and bad news
Found #1 nemesis of programming - typo!
SPACE before the closing " !

export PKG_CONFIG_PATH="/usr/lib/x86_64-linux-gnu/pkgconfig "

Typo makes sense, but still do not get how "configure" verifies "GLIB" without dpkg finding it.
I could post PART of the successful log if anybody likes to see it. Perhaps the answer in there somewhere.

Update
I have clean "configure" script run.
Now mowing to "make" and as expected having my first "make" error.
Should I post it here as continuum or make a new thread?
It is related to "glib"

(Luckily the topic-title is broad enough.)

Originally Posted by AnneRanch Should I post it here as continuum or make a new thread? It is related to "glib"

Yes, here please.

Thanks for the permission.

Here is the full error output from "make".
It does no show up until the --host option is specified in "configure".

That according to SOME comments should be enough to specify "crosscompiling" - which is my objective.

I just run into unexpected errors when I added "echo" to the wrapper, so it is getting harder to "trace" part of suspected error code.

But these are header files so it may not be that hard.

It looks it may have something to do with 64 bits system, but that is just my first guess.

jim@jim-desktop:/media/jim/DEV/BLUEZ/BLUEZ_RPI/bluez-5.50$ sudo make
make --no-print-directory all-am
  CC       lib/bluetooth.lo
  CC       lib/hci.lo
  CC       lib/sdp.lo
  CCLD     lib/libbluetooth.la
  CC       lib/uuid.lo
  CCLD     lib/libbluetooth-internal.la
arm-linux-gnueabihf-ar: `u' modifier ignored since `D' is the default (see `U')
  CC       gdbus/mainloop.lo
In file included from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9:0,
                 from /usr/include/glib-2.0/glib/gtypes.h:32,
                 from /usr/include/glib-2.0/glib/galloca.h:32,
                 from /usr/include/glib-2.0/glib.h:30,
                 from gdbus/mainloop.c:28:
/usr/include/glib-2.0/glib/gtypes.h: In function '_GLIB_CHECKED_ADD_U64':
/usr/include/glib-2.0/glib/gmacros.h:232:53: error: size of array '_GStaticAssertCompileTimeAssertion_0' is negative
 #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER__)[(expr) ? 1 : -1] G_GNUC_UNUSED
                                                     ^
/usr/include/glib-2.0/glib/gmacros.h:229:47: note: in definition of macro 'G_PASTE_ARGS'
 #define G_PASTE_ARGS(identifier1,identifier2) identifier1 ## identifier2
                                               ^
/usr/include/glib-2.0/glib/gmacros.h:232:44: note: in expansion of macro 'G_PASTE'
 #define G_STATIC_ASSERT(expr) typedef char G_PASTE (_GStaticAssertCompileTimeAssertion_, __COUNTER__)[(expr) ? 1 : -1] G_GNUC_UNUSED
                                            ^
/usr/include/glib-2.0/glib/gtypes.h:422:3: note: in expansion of macro 'G_STATIC_ASSERT'
   G_STATIC_ASSERT(sizeof (unsigned long long) == sizeof (guint64));
   ^
Makefile:5858: recipe for target 'gdbus/mainloop.lo' failed
make[1]: *** [gdbus/mainloop.lo] Error 1
Makefile:3278: recipe for target 'all' failed
make: *** [all] Error 2
jim@jim-desktop:/media/jim/DEV/BLUEZ/BLUEZ_RPI/bluez-5.50$

You might want to quote the configure command you used before make.

Note: if I were to cross-compile programs on Debian(ish) platform, I would start here: https://wiki.debian.org/Multiarch/HOWTO

One or two remarks that might help you:

Most distros (certainly all the Debian-based ones) install a library in two parts. There is the library itself (which is needed by any running program that has been built against it) and the so-called "development package" consisting of compilation headers and documentation. This is only needed if you want to build an application which uses that library. The division goes back to the days of dial-up connections, when it saved mightily on download times. There was no need for people to download the headers if they weren't going to build anything locally.

Configure scripts are looking for headers, not library code. So when configure tells you that it can't find libfoo, it means it can't find the libfoo headers in /usr/include. The solution is to install the development package libfoo-dev.

Originally Posted by AnneRanch Typo makes sense, but still do not get how "configure" verifies "GLIB" without dpkg finding it.

Try checking the package called libglib2.0-dev in dpkg.

https://packages.debian.org/search?s...ds=glib-2.0.pc

Originally Posted by hazel One or two remarks that might help you: Most distros (certainly all the Debian-based ones) install a library in two parts. There is the library itself (which is needed by any running program that has been built against it) and the so-called "development package" consisting of compilation headers and documentation. This is only needed if you want to build an application which uses that library. The division goes back to the days of dial-up connections, when it saved mightily on download times. There was no need for people to download the headers if they weren't going to build anything locally. Configure scripts are looking for headers, not library code. So when configure tells you that it can't find libfoo, it means it can't find the libfoo headers in /usr/include. The solution is to install the development package libfoo-dev.

This is needed very useful info, thanks.

When I started analysing the ":configure" script I looked at this correct output

@line 1898 DEBUG Checking for linux/if_alg.h... yes
@line 13221 DEBUG Checking for GLIB... yes
@line 13374 DEBUG Checking for DBUS... yes
@line 13453 DEBUG Checking D-Bus configuration directory... PKG_CONFIG_DEBUG_SPEW variable enabling debug spew

Only AFTER there is ANY problems with "Checking for GLIB" I get more info, but in general the error would be in style "...cannot find GLIB > 2.43" .
The bottom line - I have no idea "configure" is actually looking for "lib*" or "C" header or else.

I generally get more info after adding PKG_CONFIG_DEBUG_SPEW and after I get into habit of checking "config.log".

My approach may look silly, but I find it useful to try something and ONLY after it does not work as expected I "hit the books" or forums.

If I do it the other way around - I would never complete any project , and it is doubtful I would retain the "books knowledge" on something which works just fine.

I may not present myself as such , but "doing" computers since 197x I believe I do have reasonable base to build on.


Enough venting.

Originally Posted by ntubski Try checking the package called libglib2.0-dev in dpkg. https://packages.debian.org/search?s...ds=glib-2.0.pc

I did similar - try to install "*-dev" only to get "you have the latest on your system ".

Originally Posted by NevemTeve You might want to quote the configure command you used before make. Note: if I were to cross-compile programs on Debian(ish) platform, I would start here: https://wiki.debian.org/Multiarch/HOWTO

These are VERY basic options , just adding --host option causes the "make" output the error.

$ sudo ./configure_56 PKG_CONFIG_DEBUG_SPEW=set --host=arm-linux-gnueabihf

Originally Posted by NevemTeve You might want to quote the configure command you used before make. Note: if I were to cross-compile programs on Debian(ish) platform, I would start here: https://wiki.debian.org/Multiarch/HOWTO

Good reference article, however, not totally applicable to what I am doing.

I do not want to restart another pointless discussion about reposting stuff, not explaining (in details) what I am doing and not appreciating group suggestions.

I do not need to build / install bluez package for ARM architecture package on my X86.
Bluetooth is part of the kernel, no need to do that.

What I have been after ,since I started discussing the project here, is to build bluetooth "C" library for ARM architecture on my X86 system.

That is what "configure" does , or should.

Optioning "configure" to build such "C" library for native, X86, architecture is NON ISSUE.
The issue is to do same for ARM , host, architecture and until I have such "C" library build by "configure" process - it is going to be an UNSOLVED issue.

Despite some misgivings about this forum. I DO APPRECIATE ALL SUGGESTIONS.

IT IS VERY HELPFUL TO BE ABLE TO BOUNCE OFF IDEAS IN FORUM. and not necessarily just having "SOLUTIONS".

Cheers

End of vent