Before I start getting into technical things, what are you trying to achieve?
If you just want to vent, I don’t have to judge that, but I’d rather not engage with it. I’m just a random guy on the internet trying to be help out other people every once in a while, and to be honest I’m asking myself why sometimes.



 divinho:

Using pytorch from your github link leads to the problem that it tries to get eigen from 'https://github.com/RLovelett/eigen.git which doesn’t exist. I fix it by getting eigen from the current remote repo. Then when compiling an error: call to 'stod' is ambiguous , of course there is a github issue on this with no response. When finished, not all requested libraries have been built, and I realize that for some reason pytorch/c10 doesn’t exist. git submodule update does nothing, so I give up and try and just use the latest pytorch.


Now, the eigen repository changed URL quite a while ago (seams not unreasonable to me) and for some reason you picked up the old one (maybe because I don’t use the master branch in my github repo and it is old enough to still have that - but I don’t know and git submodule apparently does not handle changes in the upstream repository - probably because no-one who hit the problem showed up to fix it, I certainly am guilty of that). Similarly, I could point out that we’re all doing git submodule update --init --recursive or so these days.
Probably it’s fair to say that some of the things that are happening in the following are from mixing different versions and builds. Including the headers seems like a not so stable recipe when people might use different versions of the lib, and I must admit I am hoping that someone else finds out about how to get all the headers in one place nicely and tells me.
I am not quite able to discern what you did from your description. It’s no wonder that typical bug report templates ask people to provide as exact instructions to reproduce. The issues you are seeing likely stem from the complexity of the interactions of various bits so that apparently the instructions such as the ones I put out don’t allow you to replicate what I did. But anyone trying to look into your issue will have the exact same problem, so it would seem a natural reaction to say yeah well, I’ll answer someone who provided more detail instead. It might be nicer to drop a note of that sort into the bug report, but I’ll tell you from experience, that it’s as frustrating for the people trying to find out what went wrong as for the reporter, so it’s easy for incomplete bug reports to fall through the grid.
To me, your report sounds like I started with what you said and then I did all sorts of crazy things and then it turned out wrong and now I’m angry and by the time I could have looked at more details I have zoomed out and walked away.
Good luck with your project!
Best regards
Thomas