Analyze "configure" script after adding PKG_CONFIG_DEBUG_SPEW option
Could somebody help me to figure out where is the problem?
I am including partial output from "configure" script where it "adds" directories -after executing "export" - first part of the snippet , but it physically does not create them. It cannot "find " them later - second part of the snippet. Perhaps I am missing some option in"configure" ? Here is the CLI Code:
sudo ./configure_421 --prefix=/usr/local/BLUEZ --enable-library --host=arm-linux-gnueabihf --mandir=/usr/share/man --enable-debug PKG_CONFIG_PATH=/media/jim/DEV/GLIB/GLIB_2.54.3/glib-2.54.3 PKG_CONFIG_DEBUG_SPEW=set Quote:
|
Quote:
Code:
Cannot open directory #2 '/usr/local/lib/arm-linux-gnueabihf/pkgconfig' in package search path: No such file or directory |
no, it does not try to create them (but use). It assumes they exist and could not be found.
|
Quote:
What confuses me is the "add" , it apparently does not "add" but only "includes" according what PKG_CONFIG_LIBDIR created. So logically the physical directories must be crated BEFORE or same time. But I do not see any code doing so. I need to take a closer look at code before /usr/bin/arm-linux-gnueabihf-pkg-config is run. |
OK, the consensus is that I am missing the code to build the needed directories.
To do so I need to find out HOW the published source code actually builds / implements the subscript "arm-linux-gnueabihf-pkg-config" which builds the PKG_CONFIG_LIBDIR variables needed for host crosscompliling. Back to "download source for bluez". |
Update
Apparently the "magical" arm-linux-gnueabihf-pkg-config "wrapper" is a product of OS (?). Here is yet another well documented (!) version from "github". It is still unclear from where did the original version I have been struggling with came from. I'll give this one a try to see if it actually builds the required directories and NOT JUST the PKG_CONFIG_LIBDIR which adds reference only. Quote:
|
Quote:
|
Quote:
As far as your comments goes. I will repeat - the "wrapper " builds the references from scratch. I could post the code to try to convince you, but why since you have indicated that I do not know what I am doing -in so may words. So why bother. The main configure script works just fine when run for native architecture. There is NOTHING missing in as far as pkg-config PACKAGE goes. The "host" references are added by the wrapper script and the wrapper itself attempts to make use of them physically hence the physical directories should be build by the wrapper , before the flow is passed to standard pkg-config and then to the main script. Thanks for all your constructive comments , I do appreciate your time and input. I really need to find out the original source of the "host" sub-script. |
Quote:
Quote:
Please review the Site FAQ for guidance in posting your questions and general forum usage. From that page... Quote:
|
As suspected ( from get go) , the arm-linux-gnueabihf-pkg-config wrapper script causes "addition" of several path to directory "pkgconfig". Reasonable - it makes "configure" pretty versatile.
One of them , the original default, does contain the required pkg-config package *.pc file. The PKG_CONFIG_DEBUG_SPEW option reports both success and failures in locating the required *.pc file scanning ALL of these directories. . In my case verifying the actuall pkg_config package version , verification being part of the "configure" process, was reporting success, and the failure to find another *.pc file. Thanks for helping me to stay on course. |
All times are GMT -5. The time now is 03:54 AM. |