* ERROR: dev-lang/jimtcl-0.76::gentoo failed (configure phase): * econf failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl_20190105-131125 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) [4] pypy3 (fallback) [5] pypy (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) * Available Rust versions: [1] rust-1.31.1 * java-config: The following VMs are available for generation-2: emerge -qpvO dev-lang/jimtcl [ebuild N ] dev-lang/jimtcl-0.76 USE="-doc -static-libs"
Created attachment 560770 [details] emerge-info.txt
Created attachment 560772 [details] dev-lang:jimtcl-0.76:20190112-141731.log
Created attachment 560774 [details] emerge-history.txt
Created attachment 560776 [details] environment
Created attachment 560778 [details] etc.portage.tbz2
Created attachment 560780 [details] logs.tbz2
Created attachment 560782 [details] temp.tbz2
are you able to reproduce this error? I am a bit puzzled about the free(): invalid pointer error
got at the unstable amd64 chroot image 17.0-no-multilib-hardened_libressl-test_20190113-153406 this too
Created attachment 561586 [details] emerge-info.txt
Created attachment 561588 [details] dev-lang:jimtcl-0.76:20190116-194910.log
Created attachment 561590 [details] emerge-history.txt
Created attachment 561592 [details] environment
Created attachment 561594 [details] etc.portage.tbz2
Created attachment 561596 [details] logs.tbz2
Created attachment 561598 [details] temp.tbz2
Configuration scripts are partially written in tcl. Autosetup looks for installed tcl interpreters and prefer jimtcl if available. Removing jimtcl before emerging can work as workaround while updating.
Bootstrapping was forced by the patch. My previous assumption was incorrect. > >>> Preparing source in /var/tmp/portage/dev-lang/jimtcl-0.76/work/msteveb-jimtcl-606f011 ... > * Applying jimtcl-0.75-bootstrap.patch ... > [ ok ]
The issue is hard to reproduce. The bug may be related to the compiler. Finally I disabled bootstrapping (`jimsh0` is never build) to work around this.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b11baed16e9180017bec5cabbc54e7fac8461367 commit b11baed16e9180017bec5cabbc54e7fac8461367 Author: Eugene Bright <eugene@bright.gdn> AuthorDate: 2019-07-07 00:00:31 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-07-20 18:42:09 +0000 dev-lang/jimtcl-0.78-r2: Disable bootstrapping Make `autosetup/autosetup-find-tclsh` scripts use system `tclsh`. Forbid building `jimsh0`. Closes: https://bugs.gentoo.org/675276 Signed-off-by: Eugene Bright <eugene@bright.gdn> Signed-off-by: Michał Górny <mgorny@gentoo.org> .../jimtcl/files/jimtcl-0.78-no-bootstrap.patch | 35 ++++++++++++++ dev-lang/jimtcl/jimtcl-0.78-r2.ebuild | 56 ++++++++++++++++++++++ 2 files changed, 91 insertions(+)