<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>134091</bug_id>
          
          <creation_ts>2006-05-23 02:49 0000</creation_ts>
          <short_desc>sci-electronics/freehdl-0.0.1 needs to be marked ~ppc</short_desc>
          <delta_ts>2006-05-27 05:00:17 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>calchan@gentoo.org</reporter>
          <assigned_to>ppc@gentoo.org</assigned_to>
          <cc>calchan@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>calchan@gentoo.org</who>
            <bug_when>2006-05-23 02:49:53 0000</bug_when>
            <thetext>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&apos;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&apos;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.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>nixnut@gentoo.org</who>
            <bug_when>2006-05-26 02:35:19 0000</bug_when>
            <thetext>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&apos;t work
Is there a testcase that can be used to check functionality more thoroughly?

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>calchan@gentoo.org</who>
            <bug_when>2006-05-26 09:10:12 0000</bug_when>
            <thetext>(In reply to comment #1)
&gt; It compiles here and seems to run. 
&gt; freehdl-v2cc A4020B.vhd -o foo.cpp seem to generate a cpp source file from a
&gt; vhdl file, but I have no idea what does and doesn&apos;t work
&gt; Is there a testcase that can be used to check functionality more thoroughly?

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

Denis.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>nixnut@gentoo.org</who>
            <bug_when>2006-05-27 05:00:17 0000</bug_when>
            <thetext>Denis&apos; cooking recipe worked nicely, so ~ppc keyword added.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>