As I understand Jim Tcl is in external submodule and jimtcl/ is empty. emerge =dev-embedded/openocd-9999 >>> Unpacking source... * GIT update --> * repository: git://openocd.git.sourceforge.net/gitroot/openocd/openocd * at the commit: 8902789f0de78f52d74e467017a064dcc568b66b * branch: master * storage directory: "/var/portage/distfiles/git-src/openocd" Initialized empty Git repository in /var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999/.git/ >>> Unpacked to /var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999 * Running eautoreconf in '/var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999/jimtcl' ... * Running aclocal ... [ !! ] * Failed Running aclocal ! ***** aclocal ***** ***** PWD: /var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999/jimtcl ***** aclocal aclocal-1.10: `configure.ac' or `configure.in' is required Reproducible: Always Steps to Reproduce:
Created attachment 256507 [details] ebuild for jimtcl It seems that jimtcl needs to be built separately (the attachment is a slightly midified jimtcl ebuild from "stuge" repository). Here is a small patch for the openocd-9999.ebuild that currently available in portage: --- old/openocd-9999.ebuild 2010-12-06 19:07:09.088688962 +0300 +++ new/openocd-9999.ebuild 2010-12-06 19:07:52.985009499 +0300 @@ -20,11 +20,12 @@ LICENSE="GPL-2" SLOT="0" -IUSE="ftd2xx ftdi parport presto usb" +IUSE="ftd2xx ftdi parport presto usb blaster versaloon" RESTRICT="strip" # includes non-native binaries # libftd2xx is the default because it is reported to work better. -DEPEND="usb? ( dev-libs/libusb ) +DEPEND="dev-lang/jimtcl + usb? ( dev-libs/libusb ) presto? ( dev-embedded/libftd2xx ) ftd2xx? ( dev-embedded/libftd2xx ) ftdi? ( dev-embedded/libftdi )" @@ -59,10 +60,13 @@ --enable-at91rm9200 \ --enable-gw16012 \ --enable-oocd_trace \ + --disable-internal-jimtcl \ $(use_enable usb usbprog) \ $(use_enable parport) \ $(use_enable presto presto_ftd2xx) \ $(use_enable ftdi ft2232_libftdi) \ + $(use_enable blaster usb_blaster_libftdi) \ + $(use_enable versaloon vsllink) \ $(use ftdi || use_enable ftd2xx ft2232_ftd2xx) \ ${myconf} emake || die "Error in emake!" with jimtcl-9999.ebuild added and openocd-9999.ebuild patched "emerge openocd" goes fine.
Even with this patch openocd-9999 dont want to build - it still contain jimtcl directory in the sources and try call eautoreconf from it: /var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999/jimtcl (which is empty) so, also see this aclocal error
Here is log of emerge (with already installed jimtcl-9999 from ebuild attached to this bug, and with applied diff for openocd-9999, also described in this bug): # emerge openocd These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-embedded/openocd-9999 USE="ftdi parport usb -blaster -ftd2xx -presto -versaloon" 0 kB [1] Total: 1 package (1 new), Size of downloads: 0 kB Portage tree and overlays: [0] /usr/portage [1] /usr/local/portage Would you like to merge these packages? [Yes/No] Yes >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-embedded/openocd-9999 from unknown repo * Package: dev-embedded/openocd-9999 * USE: elibc_glibc ftdi kernel_linux parport usb userland_GNU x86 * FEATURES: ccache sandbox >>> Unpacking source... * GIT update --> * repository: git://openocd.git.sourceforge.net/gitroot/openocd/openocd * at the commit: 95de667e243fe48783da0fdc92270a0d3d28ff0c * branch: master * storage directory: "/usr/portage/distfiles/git-src/openocd" Cloning into /var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999... done. >>> Unpacked to /var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999 * Running eautoreconf in '/var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999/jimtcl' ... * Running aclocal ... [ !! ] * Failed Running aclocal ! * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-embedded/openocd-9999/temp/aclocal.out * ERROR: dev-embedded/openocd-9999 failed (unpack phase): * Failed Running aclocal ! * * Call stack: * ebuild.sh, line 56: Called src_unpack * environment, line 3139: Called eautoreconf * environment, line 922: Called eautoreconf * environment, line 930: Called eaclocal * environment, line 863: Called autotools_run_tool 'aclocal' * environment, line 406: Called die * The specific snippet of code: * die "Failed Running $1 !"; * * If you need support, post the output of 'emerge --info =dev-embedded/openocd-9999', * the complete build log and the output of 'emerge -pqv =dev-embedded/openocd-9999'. * This ebuild is from an overlay: '/usr/local/portage/' * The complete build log is located at '/var/tmp/portage/dev-embedded/openocd-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-embedded/openocd-9999/temp/environment'. * S: '/var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999' >>> Failed to emerge dev-embedded/openocd-9999, Log file: >>> '/var/tmp/portage/dev-embedded/openocd-9999/temp/build.log' * Messages for package dev-embedded/openocd-9999: * GIT update --> * repository: git://openocd.git.sourceforge.net/gitroot/openocd/openocd * at the commit: 95de667e243fe48783da0fdc92270a0d3d28ff0c * branch: master * storage directory: "/usr/portage/distfiles/git-src/openocd" * Failed Running aclocal ! * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-embedded/openocd-9999/temp/aclocal.out * ERROR: dev-embedded/openocd-9999 failed (unpack phase): * Failed Running aclocal ! * * Call stack: * ebuild.sh, line 56: Called src_unpack * environment, line 3139: Called eautoreconf * environment, line 922: Called eautoreconf * environment, line 930: Called eaclocal * environment, line 863: Called autotools_run_tool 'aclocal' * environment, line 406: Called die * The specific snippet of code: * die "Failed Running $1 !"; * * If you need support, post the output of 'emerge --info =dev-embedded/openocd-9999', * the complete build log and the output of 'emerge -pqv =dev-embedded/openocd-9999'. * This ebuild is from an overlay: '/usr/local/portage/' * The complete build log is located at '/var/tmp/portage/dev-embedded/openocd-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-embedded/openocd-9999/temp/environment'. * S: '/var/tmp/portage/dev-embedded/openocd-9999/work/openocd-9999' * * The following package has failed to build or install: * * (dev-embedded/openocd-9999, ebuild scheduled for merge), Log file: * '/var/tmp/portage/dev-embedded/openocd-9999/temp/build.log' *
I've had dev-lang/jimtcl-9999 and dev-embedded/openocd-9999 ebuilds in my overlay "stuge" for a while, and feedback from xvilka on IRC prompted me to make updates so that they will sucessfully build current jimtcl and openocd git. To install: emerge layman layman -a stuge grep -q source.*layman /etc/make.conf || echo 'source /var/lib/layman/make.conf' >> /etc/make.conf emerge =openocd-9999
I pushed a snapshot and a live ebuild for jimctl on the tree. Tomorrow I will fix openocd live ebuild and probably commit a snapshot for 0.5.0 release
(In reply to comment #5) > I pushed a snapshot and a live ebuild for jimctl on the tree. Thanks! I've removed the one in my overlay. > Tomorrow I will fix openocd live ebuild Yeah, I did a bit of a hack in mine because I didn't know exactly what to do with all the optional programmer cables. > and probably commit a snapshot for 0.5.0 release Note that there is no upstream 0.5.0 release available yet.
(In reply to comment #6) I know that 0.5.0 is not out but the master branch is moving towards this release.
Snapshot and new live ebuild is on tree. Please give them a shot. Thank you
