Project

General

Profile

Actions

Bug #17723

closed

autoconf 2.70+ is not working with master branch

Bug #17723: autoconf 2.70+ is not working with master branch

Added by hsbt (Hiroshi SHIBATA) over 4 years ago. Updated over 4 years ago.


Description

MacPorts upgraded the version of autoconf to 2.71 recently. On macOS environment with MacPorts is broken now.

http://rubyci.s3.amazonaws.com/osx1100arm/ruby-master/log/20210314T214503Z.fail.html.gz

Updated by znz (Kazuhiro NISHIYAMA) over 4 years ago Actions #1 [ruby-core:102853]

How about adding wrapper script autogen.sh that download required files (config.guess, ...) and run autoconf.

This solution does not depend automake now, and it can use automake for future when needed.

Updated by shyouhei (Shyouhei Urabe) over 4 years ago Actions #2 [ruby-core:102854]

@znz (Kazuhiro NISHIYAMA) I don't understand why you suddenly start talking about automake. Can't you focus on fixing the bug?

Updated by shyouhei (Shyouhei Urabe) over 4 years ago Actions #3 [ruby-core:102856]

I guess running autoreconf instead of autoconf fixes the situation. Test code: https://github.com/shyouhei/docker-library/blob/master/%2317723/Dockerfile

Updated by nobu (Nobuyoshi Nakada) over 4 years ago Actions #4 [ruby-core:102857]

autoreconf seems to need automake.

Updated by shyouhei (Shyouhei Urabe) over 4 years ago Actions #5 [ruby-core:102858]

nobu (Nobuyoshi Nakada) wrote in #note-4:

autoreconf seems to need automake.

Not really. It runs aclocal, and that's because our aclocal.m4 was generated using it.

https://github.com/autotools-mirror/autoconf/blob/300349c84bce66b84b8d9cc8bb6b37d46aa19585/bin/autoreconf.in#L515-L524

We can fix this.

Updated by hsbt (Hiroshi SHIBATA) over 4 years ago Actions #6 [ruby-core:102860]

I'm okay to change the official instructions to autoreconf -i instead of autoconf. But I'm not sure that autoreconf -i needs automake.

I will update the usage of autoconf of ruby-build to it after investigating the minimum requirements.

And Should we update its instructions to stable versions like 3.0 and 2.7?

Updated by mame (Yusuke Endoh) over 4 years ago Actions #7 [ruby-core:102879]

Regardless whether it depends on automake or not, it would be great to have autogen.sh. I'm used to autoconf, and I have never heard autoreconf -i until this issue. Also, I had to change RubyCI code to support the new build process. It would be good to absorb such a change in autogen.sh instead of each CI configuration.

Updated by mame (Yusuke Endoh) over 4 years ago Actions #8 [ruby-core:102903]

I see no objection about autogen.sh, so I've added it. 4250d7c910fd67c0da07c6213901009330e3cd51

Updated by nobu (Nobuyoshi Nakada) over 4 years ago Actions #9

  • Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN to 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED, 3.0: REQUIRED

Updated by nobu (Nobuyoshi Nakada) over 4 years ago Actions #10

  • Status changed from Assigned to Closed

Updated by nagachika (Tomoyuki Chikanaga) over 4 years ago Actions #11 [ruby-core:103504]

  • Backport changed from 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED, 3.0: REQUIRED to 2.5: REQUIRED, 2.6: REQUIRED, 2.7: REQUIRED, 3.0: DONE

ruby_3_0 a55ba76617f240337854668c8b5dd9961873f5af merged revision(s) 4250d7c910fd67c0da07c6213901009330e3cd51,83f96642d2d74569cc38319d02d5922fac8f66b8,447feb0aa08e20cc5eeb8b3a6f881de261a2c9a2,1d80d703141f01383604022f9e8e53e10865197c,e271a3d4afc47e812b50fc9c50f6bf34d2d723a6,366e88e508de7c59d69906ad948cccd7979e932b,d825e34962540d345eb3c5a70eb264b415e915a5,4250d7c910fd67c0da07c6213901009330e3cd51,f9e43782995b1f77e7b10c79941bbbda15620e2a.

Updated by nagachika (Tomoyuki Chikanaga) over 4 years ago Actions #12 [ruby-core:103505]

And 5a9b5b8e953dc36f4f7f7639e8aeaa8132241c79 too.

Actions

Also available in: PDF Atom