Bugzilla Bug 134091

freehdl-0.0.1 was released a few months ago. Previously, the releases were
named freehdl-yyyymmdd (year-month-day). With the new versioning scheme, new
releases appear as a downgrade during an emerge. After discussing this with
plasmaroo, the solution seemed to be adding an ebuild for 0.0.1 and removing
the old ones.

Unfortunately, the old ebuilds were marked ~x86 and ~ppc, and quick tests by a
nice volunteer in #gentoo-ppc showed that the new version may not compile
cleanly on ppc (I'm not able to test on ppc). So, what I have done is add a
0.0.1 ebuild in Portage, mark it ~x86 (and ~amd64 since it worked too), and
remove ~x86 from all the the old ebuilds. This way, x86 users will
automatically be updated to 0.0.1 (although this will look like a downgrade),
and ppc users will not be bothered.

What's left to do is more thoroughly verify whether 0.0.1 compiles on ppc, fix
it if necessary, and mark that new ebuild ~ppc. Then, and only then, we will be
able to remove the old ebuilds and fix that upgrade-that-looks-like-a-downgrade
behavior.

Thanks for your help.
Denis.

It compiles here and seems to run. 
freehdl-v2cc A4020B.vhd -o foo.cpp seem to generate a cpp source file from a
vhdl file, but I have no idea what does and doesn't work
Is there a testcase that can be used to check functionality more thoroughly?

(In reply to comment #1)
> It compiles here and seems to run. 
> freehdl-v2cc A4020B.vhd -o foo.cpp seem to generate a cpp source file from a
> vhdl file, but I have no idea what does and doesn't work
> Is there a testcase that can be used to check functionality more thoroughly?

I'll try and send you a test case along with a cooking recipe ASAP. Don't
forget to beat me with a huge stick in case I don't do so before the end of the
week-end.

Denis.

Denis' cooking recipe worked nicely, so ~ppc keyword added.