Mike Frysinger wrote:
> On Friday 12 September 2008, billium wrote:
>> get openocd from respository, svn checkout
>> svn://svn.berlios.de/openocd/trunk/openocd and extract
>
> why ? we have an openocd-9999.ebuild which fetches straight from the
> upstream
> site ...
> -mike
Just tried to emerge it. Here are two small patches to the ebuilds to
make it compile on amd64.
Let me know if it looks good and I'll hit bugzilla.
Jason.
--- /usr/portage/dev-embedded/libftd2xx/libftd2xx-0.4.13-r1.ebuild
2007-12-29 07:27:16.000000000 -0500
+++ /usr/local/portage/dev-embedded/libftd2xx/libftd2xx-0.4.13-r1.ebuild
2008-10-26 10:59:06.000000000 -0400
@@ -12,14 +12,18 @@
LICENSE="as-is"
SLOT="0"
-KEYWORDS="~x86"
+KEYWORDS="~x86 ~amd64"
IUSE="examples"
-DEPEND=""
+DEPEND="amd64? ( app-emulation/emul-linux-x86-baselibs)"
RDEPEND="${DEPEND}"
S="${WORKDIR}/${MY_P}"
+pkg_setup() {
+ has_multilib_profile && ABI="x86"
+}
+
src_install() {
ftdifile="${PN}.so.${PV}"
ftdisym="${PN}.so.0 ${PN}.so"
--- /usr/portage/dev-embedded/openocd/openocd-9999.ebuild 2008-06-04
13:05:41.000000000 -0400
+++ /usr/local/portage/dev-embedded/openocd/openocd-9999.ebuild 2008-10-26
11:12:02.000000000 -0400
@@ -24,6 +24,13 @@
ewarn "You enabled libftdi but not ft2232!"
ewarn "libftdi is only used for ft2232, so this is meaningless!"
fi
+
+ if use ft2232 && has_multilib_profile ; then
+ ABI="x86"
+ if use ftdi ; then
+ die "ft2232 is x86 and ftdi is amd64, choose one or the
other!"
+ fi
+ fi
}
src_unpack() {
