Dne 13. 10. 20 v 14:29 Mamoru TASAKA napsal(a):
Pavel Valena wrote on 2020/10/13 21:00:
> ----- Original Message -----
>> From: "Vít Ondruch" <vondruch(a)redhat.com>
>> To: ruby-sig(a)lists.fedoraproject.org
>> Sent: Friday, October 9, 2020 1:52:07 PM
>> Subject: Re: Ruby 3.0
>>
>> Hi all,
>>
>> Another update to the most recent version of Ruby 3.0 is here:
>>
>>
https://src.fedoraproject.org/rpms/ruby/pull-request/70
>>
>>
https://koji.fedoraproject.org/koji/taskinfo?taskID=53075655
>>
>> The main difference is RubyGems patch fixing issues with build of
>> rubygem- packages pvalena encountered in Copr. Apart of that, there is
>> ongoing StdLib gemification.
>>
>> As always, I'm looking for any feedback.
>
> Hello,
>
> I've rebuilt your ruby in my ruby-testing copr repo, and I'm building
> (almost) all rubygem-* packages on top of it in my rubygems-testing
> corp repo.
Appreciate that!
>
> This time, it was more successful. I only had to remove `racc`
> requirement from Nokogiri so far (colliding with ruby-default-gems).
>
>
https://download.copr.fedorainfracloud.org/results/pvalena/rubygems-testi...
Interesting. I have already dropped the %{_bindir}/racc, I should
probably drop also the bin/racc directrly from the package. Good catch.
>
> All build results can be found here:
>
>
https://copr.fedorainfracloud.org/coprs/pvalena/rubygems-testing/builds/
>
> I'm looking into the failed ones, and rebuilding those which can be,
> as their dependencies got fullfiled.
>
> One 'interesting' failure is a gem with native extension:
>
>
https://download.copr.fedorainfracloud.org/results/pvalena/rubygems-testi...
> (It builds fine in rawhide.)
>
> Pavel
Looks like with Vít's ruby 3.0 scratch build (taskID=53075655),
CONFIG["CXX"] is not set ( in /usr/lib64/ruby/rbconfig.rb on x86_64),
while
with ruby-libs-2.7.1-134.fc33.x86_64, CONFIG["CXX"] is correctly set
as g++.
rubygem-eventmachine uses CONFIG["CXX"] to find c++ compiler, so it seems
currently eventmachine cannot find c++ compiler.
Mamoru, thx for analysis. Very interesting. We don't have installed g++
during build of Ruby, that might be the reason for the issue. But the
question is what have changed. I will need to take a closer look.
Vít