On Fri, Jul 13, 2018 at 12:39:55PM +0200, Igor Gnatenko wrote: > On Fri, Jul 13, 2018, 11:19 Miro Hrončok <mhron...@redhat.com> wrote: > > On 8.7.2018 20:46, Igor Gnatenko wrote: > > > As per Changes/Remove GCC from BuildRoot > > > <https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot>, I'm > > > going to automatically add BuildRequires: gcc and/or BuildRequires: > > > gcc-c++ to packages which fail to build with common messages (like gcc: > > > command not found, also autotools/cmake/meson are supported). > > > > > > I'm going to do this tomorrow. > > > > > > After which, I'm going to ask rel-eng to finally remove it from > > > buildroot. This will happen before mass rebuild. Stay tuned. > > > -- > > > > I've clicked randomly trough failures during the mass rebuild at [1]. > > > > I see quite a lot of commands not founds for gcc, cc, c++... > > > > I think the maintainers should add them and that's fine, but it seemed > > that during this change you said you will add those. Did it happen? > > > > Yes, I've pushed over 2k commits adding those, however regexp might have > not catched all possible cases. Would appreciate if you would link such > packages so that I can fix them. Or maintainers can do it themselves. > > [1] https://kojipkgs.fedoraproject.org/mass-rebuild/f29-failures.html
bionetgen was one. It was failing with "/bin/sh: g++: command not found". It is my package, I took care of that already. (Now it's failing on something unrelated.) Zbyszek _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/3R4KLJJR5ZADHEGTFBZONKDPP6DMKXW5/
