[ruby-core:85617] Re: Why require autoconf 2.67+

Actually, the snippet helps with Ruby 2.4, Ruby 2.5 renamed configure.in
to configure.ac, but it might be similar hopefully.


V鱈t


Dne 18.2.2018 v 12:12 V鱈t Ondruch napsal(a):
> This could help you to build Ruby with older autoconf (2.63 is default
> on RHEL/CentOS 6):
>
> ~~~
> # Allow to use autoconf 2.63.
> sed -i '/AC_PREREQ/ s/(.*)/(2.62)/' configure.in
>
> # AS_FOR is not supported on RHEL6, inject our own version.
> cat >> acinclude.m4 <<\EOF
> m4_ifndef([AS_FOR], [
>   m4_define([AS_FOR], [
>     m4_pushdef([$1], [$$2])
>     for $2 in $3; do
>       $4
>     done
>     m4_popdef([$1])
>   ])
> ])%endif
>
> EOF
>
> sed -i '/AS_FUNCTION_DESCRIBE/ s/^/#/' configure.in
> sed -i '/AS_FUNCTION_DESCRIBE/ s/^/#/' acinclude.m4
> ~~~
>
>
> V鱈t
>
> 2018-02-17 13:46 GMT+01:00 leam hall <[e-mail]>:
>> Please pardon the intrusion; I am new to Ruby and like to pull the
>> development version of Ruby to compile and code with.
>>
>> On 8 Feb 18 (US/Eastern) I pulled the code from GitHub and Ruby
>> 2018-02-09 trunk 62326 compiled fine and all tests except for some
>> timezone ones passed.
>>
>> Today I pulled the source again. The configure step worked well but make failed:
>>
>>   configure.ac:7: error: Autoconf version 2.67 or higher is required
>>   configure.ac:7: the top level
>>   autom4te: /usr/bin/m4 failed with exit status: 63
>>   make: *** [configure] Error 63
>>
>> In configure.ac line 7:
>>
>>   AC_PREREQ(2.67)
>>
>> If I changed 2.67 to 2.63 which is what my server has, the make
>> configure step fails with:
>>
>>   ./configure: line 674: syntax error near unexpected token `colorize_result,'
>> .  /configure: line 674: `AS_FUNCTION_DESCRIBE(colorize_result, MSG,
>> Colorize result)'
>>
>> I tried commenting out the lines it complained about but that led to
>> an "unexpected token 'fi'" error on line 76907. Commented that out but
>> then hit:
>>
>>   ./configure: line 77563: syntax error near unexpected token `opt,'
>>
>> At this point I do not know if it is better to follow the path and try
>> to see what the difference is or just ask. If I change things then the
>> next pull breaks the changes. So I decided to ask.
>>
>> Thank you .
>>
>> Leam
>>
>> Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
>> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>


Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>