Closed simeonmiteff closed 2 years ago
FYI, ./target/debug/build/example-b9b2d66896358201/out/libVtop__ALL.a
is getting built and contains the Vtop
class.
The linking step that fails includes among the many arguments:
"-L" "/tmp/verilated-rs/target/debug/build/example-b9b2d66896358201/out"
"-Wl,--whole-archive" "-lVtop__ALL"
This seems OK to me :man_shrugging:...
Oh no, I misread the output of nm
, they are indeed U
(for undefined):
$ nm -g ./target/debug/build/example-b9b2d66896358201/out/libVtop__ALL.a | c++filt | grep 'Vtop::_eval_initial('
U Vtop::_eval_initial(Vtop__Syms*)
Damn, sorry for the noise.
I think I had some old object files from a previous failed build with an older version of verilator. The linking issue went away to be replaced by a different issue. I'll close this for now and open another issue if I don't manage to work it out by myself.
Hi @djg
I'm using rustc 1.55 and verilator 4.212 on Linux and I encountered a linking issue:
I'm still trying to wrap my head around how the build is supposed to work, but figure maybe you already know why those symbols would be missing?
Regards, Simeon.