On Sat, 17 Aug 2019 at 11:18, Björn Persson <Bjorn@rombobjörn.se> wrote: > > Stephen John Smoogen wrote: > > gcc-objc will need someone to make a module or SCL for it. The GCC > > src.rpm seems to be patched out to not make any of the alternative > > compilers that gcc normally makes. > > In that case I guess there is no gcc-gnat either? :-( > As far as I know, the only artifacts which come out of the gcc src.rpm are the ones which are shipped.. everything else is removed to make the build process simpler and less prone to 'oh gcc-gnat enabled something which made gcc-g++ do X when it should have done Y. [Not that happens a lot.. but this is meant to be a process where even 1 in a million problems aren't wanted by enterprise customers] > > So someone will need to take this on as a major project to form. > > I have little experience with building GCC, and none at all with > modules or SCLs. I think this would be too big a project for me to > handle in my scarce free time, but if a team would form to build a GCC > with more languages enabled, then maybe I could help to some small > degree. > Me either. This is going to be a learning process ! > Björn Persson > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
