Quote:
Originally Posted by carrud
Yes, I have successfully worked around this issue by putting a chmod in our build.xml.
However, this is just not right. This is a dangerous way to fix this and leaves us vulnerable if we were to need to reinstall, etc. But we are up and that is good.
It is just a same to spend so many hours chasing this and I'm interested to know what is the underlying cause of this.
|
I agree completely - I'd like the NI/WPILib people to at least investigate what might be causing this to occur and publish an endorsed method of dealing with the problem should it occur. If this happens to someone while at an event....