Quote from: w7cce on January 12, 2018, 11:01:50 PM

PITA is an understatement. Of the responses to this thread that I could decipher I tried them all. NONE WORKED. I suppose that is intentional. Job security? or is it simply fraud? I don't know but someone will. Lets hope it doesn't become an SEC issue someday. Been there, done that, not fun.

1. If the libdb_cxx file is required, and its an old version, it should be included with the distribution.
2. ditto for all other files not easily available.

It feels to me like the "community", in a response to the question, how do you get to Sacramento from LA is handing users a map to Peoria, IL, and saying, all you've got to do is read this map which you can find here, and pointing them to a hotel in Reno.

Never mind that you have to travel 2000 miles each way for no legitimate reason. (I know, I've actually had to do similar things, but this isn't about airline logistics).

If you want to solve all of the errors you can do it easily with some really stupid and simple commands, which take only a few minutes to execute:

yum install *bdb*
yum install boost*

Yes a couple hundred megabytes of crap gets installed, but when you .\configure it sails along and you can then type 'make' and it all works. In my opinion git needs a new layer that checks requirements against versions and forces old versions to be included whenever they are required, OR when such a situation occurs install the missing files automatically as dependencies from github on line. Not rocket science, but what do I know.

Believe it or not, it's a lot easier to compile than half of the other open source projects out there. Now if the package maintainers were better at keeping packages up to date or backward compatible, it would be even better. However, I'm not paying them to do that, so I can't really complain.