Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=478749
--- Comment #26 from manuel wolfshant <wolfy(a)nobugconsulting.ro> 2009-04-09
03:15:12 EDT ---
(In reply to comment #25)
>[wolfy@wolfy tmp]$ dinotrace /tmp/*vcd
>%E, Strange bit value U on line 388 of /tmp/wave1.vcd
>wave1,vcd is in fact part of stock IUS82, that is
>/tools.lnx86/inca/examples/vhpi/waveform/test/golden/wave1.vcd
U's aren't legal in VCDs. This is probably a EVCD file, which verilator
doesn't support. EVCDs are used primarily by chip testers, it's a bit odd that
an example would use that.
Well, that's what Cadence distributes. And the company I work for has chip
testing as major part of it's business.
>2. Is the emacs subpackage really supposed to be used without
having dinotrace
>installed? I see no reason to not allow that, but I want your confirmation that
>this is intentional.
No, the emacs part won't be usable without the verilog-mode.el package, but
the rest of the tool will be.
My question was directed more towards Chitlesh. As
packaged now, the
emacs-dinotrace package does not require dinotrace. Which is OK if you only
edit files but will lead to unpleasant experience if one wants to launch
dinotrace from inside emacs, as "yum install emacs-dinotrace" would not have
pulled in dinotrace.
If you're distributing with emacs-21.4 then you really should be
providing a
verilog-mode.el RPM. It's far more in demand than Dinotrace/Verilator/Icarus
all which you're including. Emacs-22 includes it as part of the Emacs core
library, so if you release a more recent emacs that gets it too.
Well, RHEL5
ships emacs-21.4 and it's not for us to decide what will be
included in the future. What I am most interested in is having dinotrace
available for my colleagues who use Centos. For the moment the free tool they
could use is only gtkwave, if I am not mistaken.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.