Implementing PKG_CONFIG_DEBUG_SPEW in "configure" script.
 

This post is a result of several incomplete / unsolved posts on this forum.
I would prefer not to be accused of reposting etc., but if possible like to get into serious discussion regarding the issues instead.

I have previously successfully used environment variable PKG_CONFIG_DEBUG_SPEW=set as an option for "configure".

The result were numerous debugging outputs helping me to analyse the "configure" script.

After downloading new and clean copy of "configure" I am unable to implement this variable again as a "configure" option or even setting it in script itself.

The enclosed test code verifies that PKG_CONFIG_DEBUG_SPEW is set in script but it does no show in printenv


I like to mention the recent discussion about using "autotools", perhaps adding
PKG_CONFIG_DEBUG_SPEW into "configure" is wrong thing to do and the variable should be implemented elsewhere.

Appreciate any help in solving this issue.

Configure script is a shell script.

There is a common way to debug shell scripts which I've mentioned before in your repeated threads about package configuration questions. Please think about the advice you've been given in the past, or instead review the blog of mine from my signature titled My Bash Blog which contains numerous methods to perform shell debugging effectively, including what I'm talking about here.

Once again, make sure you retain incremental backups of files so you can recover or retain things which work and be able to re-use them.

Now that mention it, it is time to pay more attention to this as the multiple similar posts have been noted by myself and others.

When these things are brought to your attention please do not think of them as "accusations", and it isn't even really about "the rules". It is all about providing the best, most accessible help for yourself now, and future visitors who may have similar questions and end up on your thread from search results. And it is all about being respectful of the time others volunteer to consider and reply to your questions. The rules mention this because it is a good thing!

Keeping all your related questions in a single thread makes it very much easier for others to follow the development of your issue in a continuous manner. Not only are they more aware simply because they recognize individual threads of interest to themselves, but as participants in a thread they receive notifications when anyone posts new information, or you post a followup or related question. Better for you, better for everyone else!

When you post related questions in multiple threads, others cannot easily follow and many simply avoid participation in those after a while.

So, from here forward, let's work on keeping related things in the same thread. If your threads are merged from time to time, think of it as a service, not a reprimand. Mostly just good housekeeping!

Thanks!

Be happy to do so, unfortunately even simple , single sided unrelated to anything else question turns into innuendos "you do not know what you are doing" and nagging "if you make a backup if will work ".

It is obvious I am obligated to heed any of the subject PERSONAL remarks and have no say so about it.

No need to go far - look at this post.
So far no real contribution to the problem , only "sermons".

And I am supposedly appreciate all this from "volunteers"?

Why is so difficult to accept the fact I am looking for a technical answer and not this kind of replies?

The purpose of the forum SHOULD be to promote product by providing place to exchange ideas.

I am not that naive to expect everybody overflowing with knowledge , however , it seems that this forum seem to be more interested in maintaining format that providing for ideas exchange.

I can guess what the repose to this vent will be.

IBTL just reminder that this is not the only game in town.


PS
Found a workaround solution.

Did you not read my previous post, or simply ignore it?

One reason you do not receive many replies is very likely that based on your posting history, others can guess what your own response will be - a vent...

No one has threatened to lock your thread, and everyone, including myself has been very patient to give you opportunity to settle in and find your place in the LQ environment. Some take longer than others, and some put more effort into it than others.

Indeed, this is not "the only game in town", and while you are welcome here, no one here is competing for your business.

If you cannot find a comfortable fit for yourself here, then by all means try another venue more suitable for your style of participation. Better for you and better for everyone else.

But if you wish to continue here, please read again the Site FAQ to which you have been referred several times before now. It is a simple and very permissive code of conduct among friends, but ultimately it must govern everyone who participates here.

Best of luck in whatever you do.

As a contributing participant, you would share the solution you found, yes? That’s what makes LQ work.

(Why?)
It was a silly workaround and not really a solution.
I just made it work on different hardware.
The real solution is as I suspected - reinstalling pkg-config package.
Works peachy.
One down ... more to come.