I tried to have a brief go at catching a few stale things here and there.
@marnovandermaas @elliotb-lowrisc I happen to also have touched something you guys seem to have been interacting with apparently. Do have a look at what I have done in 18c002348e437ce065719eb58c5fe06aaa3ca044.
Unless we pass a specific qcvengine to the runscript, we should just draw a line in the sand and expect some agreed upon fixed location to the binary. Rather than silently have that location be "the one that some old version of cabal wanted" and have the think about how things should be each time a new toolchain changes that path, we just get cabal to tell us where it put the binary and copy it to where we want it when we build. (and for what it's worth, 02a337ee786df0e86c08740bd9ee3eb08e78f7e1 cleans up the run script a bit further).
I tried to have a brief go at catching a few stale things here and there.
@marnovandermaas @elliotb-lowrisc I happen to also have touched something you guys seem to have been interacting with apparently. Do have a look at what I have done in 18c002348e437ce065719eb58c5fe06aaa3ca044. Unless we pass a specific qcvengine to the runscript, we should just draw a line in the sand and expect some agreed upon fixed location to the binary. Rather than silently have that location be "the one that some old version of cabal wanted" and have the think about how things should be each time a new toolchain changes that path, we just get cabal to tell us where it put the binary and copy it to where we want it when we build. (and for what it's worth, 02a337ee786df0e86c08740bd9ee3eb08e78f7e1 cleans up the run script a bit further).