Bug 675276

Summary:	dev-lang/jimtcl-0.76 : * econf failed
Product:	Gentoo Linux	Reporter:	Toralf Förster <toralf>
Component:	Current packages	Assignee:	No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed>
Status:	RESOLVED FIXED
Severity:	normal	Keywords:	PullRequest
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://github.com/gentoo/gentoo/pull/12396
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge-info.txt dev-lang:jimtcl-0.76:20190112-141731.log emerge-history.txt environment etc.portage.tbz2 logs.tbz2 temp.tbz2 emerge-info.txt dev-lang:jimtcl-0.76:20190116-194910.log emerge-history.txt environment etc.portage.tbz2 logs.tbz2 temp.tbz2

Description Toralf Förster gentoo-dev

2019-01-12 14:42:55 UTC

 * 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"

Comment 1 Toralf Förster gentoo-dev

2019-01-12 14:42:58 UTC

Created attachment 560770 [details]
emerge-info.txt

Comment 2 Toralf Förster gentoo-dev

2019-01-12 14:43:01 UTC

Created attachment 560772 [details]
dev-lang:jimtcl-0.76:20190112-141731.log

Comment 3 Toralf Förster gentoo-dev

2019-01-12 14:43:04 UTC

Created attachment 560774 [details]
emerge-history.txt

Comment 4 Toralf Förster gentoo-dev

2019-01-12 14:43:07 UTC

Created attachment 560776 [details]
environment

Comment 5 Toralf Förster gentoo-dev

2019-01-12 14:43:10 UTC

Created attachment 560778 [details]
etc.portage.tbz2

Comment 6 Toralf Förster gentoo-dev

2019-01-12 14:43:13 UTC

Created attachment 560780 [details]
logs.tbz2

Comment 7 Toralf Förster gentoo-dev

2019-01-12 14:43:15 UTC

Created attachment 560782 [details]
temp.tbz2

Comment 8 Pacho Ramos gentoo-dev

2019-01-13 19:23:33 UTC

are you able to reproduce this error? I am a bit puzzled about the 
free(): invalid pointer

error

Comment 9 Toralf Förster gentoo-dev

2019-01-16 19:52:01 UTC

got at the unstable amd64 chroot image 17.0-no-multilib-hardened_libressl-test_20190113-153406 this too

Comment 10 Toralf Förster gentoo-dev

2019-01-16 19:52:04 UTC

Created attachment 561586 [details]
emerge-info.txt

Comment 11 Toralf Förster gentoo-dev

2019-01-16 19:52:07 UTC

Created attachment 561588 [details]
dev-lang:jimtcl-0.76:20190116-194910.log

Comment 12 Toralf Förster gentoo-dev

2019-01-16 19:52:09 UTC

Created attachment 561590 [details]
emerge-history.txt

Comment 13 Toralf Förster gentoo-dev

2019-01-16 19:52:12 UTC

Created attachment 561592 [details]
environment

Comment 14 Toralf Förster gentoo-dev

2019-01-16 19:52:15 UTC

Created attachment 561594 [details]
etc.portage.tbz2

Comment 15 Toralf Förster gentoo-dev

2019-01-16 19:52:17 UTC

Created attachment 561596 [details]
logs.tbz2

Comment 16 Toralf Förster gentoo-dev

2019-01-16 19:52:20 UTC

Created attachment 561598 [details]
temp.tbz2

Comment 17 Eugene Bright 2019-07-06 21:57:49 UTC

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.

Comment 18 Eugene Bright 2019-07-07 16:59:08 UTC

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 ]

Comment 19 Eugene Bright 2019-07-20 18:26:14 UTC

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.

Comment 20 Larry the Git Cow gentoo-dev

2019-07-20 18:46:30 UTC

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(+)