Closed silabs-robin closed 5 months ago
Never seen this one before, but is there any chance you are running configure
from within a directory that is not completely empty? Have you tried blowing away the directory, recreating it, and rerunning?
Hi.
[...] is there any chance you are running
configure
from within a directory that is not completely empty? Have you tried blowing away the directory, recreating it, and rerunning?
$ cd riscv-isa-sim/
$ git reset . ; git checkout . ; git clean -xdff .
Updated 0 paths from the index
Removing build/
$ mkdir build
$ cd build/
$ ../configure --prefix=`pwd`
$ make
^ results in the same problem.
(Right now I just used pwd
for the prefix
, but I don't think that could affect the generation of config.h
?)
Setting the prefix to be the build directory seems highly suspicious to me.
git clean -xdff .
../configure --prefix=/work/ropeders/tmp/spike/
make
This also results in the same problem.
Mysterious.
Since you're the only person to have reported this, and we can't reproduce it, I think it's up to you to figure it out. Let us know what you find.
[...] Let us know what you find.
According to this stackoverflow post, the most likely culprit is a missing libconfig
package.
As I'm not "in control" of the server I'm working on (no admin rights), I cannot confirm this. But I managed to bypass the problem by using a server node with an older version of the OS we're running, which presumably has this package installed.
One final question before closing this ticket:
The configure
script currently does not reflect that it failed to create config.h
, and the rest of the build system seems to be unaware of the failure and continues blindly.
Should that be fixed, or is it assumed to be such a rare problem that it is deemed don't-care?
According to this stackoverflow post, the most likely culprit is a missing
libconfig
package.
Ack. Thanks for getting your hands dirty on this one.
Should that be fixed, or is it assumed to be such a rare problem that it is deemed don't-care?
If there's a simple way to issue a helpful error message that fits within the autoconf framework, then we'd of course appreciate a PR. But I do think it's pretty rare, so if the fix is lengthy or otherwise awkward, then it might be best to leave it alone.
Ok :) Thank you very much for your time, then, @aswaterman. I consider this resolved and am closing the ticket now.
As I follow the build instructions,
configure
does not seem to createconfig.h
(even though it says it does).