I feel an urge to change hobby.,

I have been working with arm-linux-gnueabihf-pkg-config file.
Yesterday I changed the "sh" to "bash".

I have been working with my own copy of "configure_xxx" script, it WAS peppered with debugging "echoes" etc.

TODAY my current "configure_429" HAS NO echoes, printf etc.
TODAY the arm-linux-gnueabihf-pkg-config file is "sh" and barely one page long instead of over 5 pages.

What is happening ?
And no I am not making it up!
The arm-linux-gnueabihf-pkg-config lost ALL system environment variables I have added to it! The "configure_xxx" no longer works due to the lack of these variables!




I have never figured out where the arm-linux-gnueabihf-pkg-config file came from, but seriously - what could or who would make such drastic changes without users knowledge?

That is my qustion to the forum to ponder on.

this one ---> here

or
Package "pkg-config-arm-linux-gnueabihf"

You lost your work, either by accident, inadvertent action, or if there was some sort of git fetch action which occurred and thus overwrote your working copy.

If your editor keeps backup files, then perhaps you can recover your last version.

You are mixing "package" and the "configure" script architecture "wrapper".
Yes, I was using both wrappers - the unknown origin one and the one from RPI.
The one on my PC now resembles NEITHER one.

I use nano with -B option so I can recover my work,still like to know how can a file "accidentally" change contents.
I can buy intentionally or accidentally deleting the file, but this one is totally new.

that is a strange sounding phenomena indeed. Where did you keep it? it can be retrieved, or you stuck having to redo everything?

That's what I thought of ...an update had occurred and overwrote the manual changes the OP had made.

That's why I was wondering where OP kept the file. With anything that is update able, if one makes manual changes to "software" then they need to pull it away and put it somewhere safe, and, or no longer update it via normal means. For that reason alone.

The "wrapper " -setting additional environment variables and then executing pkg_config

is in /usr/bin/arm-linux-gnueabihf-pkg-config.

And as I have been saying - I have no idea where it came from.

Yes, if it is from OS it could have been updated since I installed another "package" and did standard update.


Now the "configure" script ignores PKG_CONFIG_DEBUG_SPEW=set.


PS
I'll be "off the air" , on "vacation", chipping rust off the WWII ships in Galveston TX.
Do not expect replies.
Thanks

do they even have a bed of water in Galveston, TX? I thought Texas only had steers and ..., well I'd take off a few days and go there in that image, anyways have fun...

Attached Thumbnails

 

1 members found this post helpful.

The post analysis is overkill. The file got reset or lost. If you have backup, then use it and move on.

Retain backups of your incremental work. This is a fundamental thing that all developers learn over time.

It it unlikely that a Linux system or package upgrade would overwrite this particular file since you are trying to install from source.

It is more likely that some other action caused a git fetch or a new extraction of the source code drop which resulted in this loss, or simple human error.

1 members found this post helpful.