Re: [HEADS UP] Removal of GCC from the buildroot

On Mon, Jul 23, 2018 at 4:59 PM wrote: > Another one, this time without any Vala: > Thanks a lot for your input! I'm going to block the Change tracking bug and fix them automatically within a few days. https://bugzilla.redhat.com/show_bug.cgi?id=1606043 >

Re: [HEADS UP] Removal of GCC from the buildroot

Another one, this time without any Vala: https://bugzilla.redhat.com/show_bug.cgi?id=1606043 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: [HEADS UP] Removal of GCC from the buildroot

On Sun, Jul 22, 2018 at 7:04 PM, Kevin Fenzi wrote: > On 07/21/2018 02:54 PM, Andrew Lutomirski wrote: > On Jul 15, 2018, at 5:47 AM, Richard W.M. Jones wrote: > > On Fri, Jul 13, 2018 at 04:05:42PM +0200, Mikolaj Izdebski wrote: > On 07/12/2018 10:17 PM, Richard W.M. Jones

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/21/2018 02:54 PM, Andrew Lutomirski wrote: On Jul 15, 2018, at 5:47 AM, Richard W.M. Jones wrote: On Fri, Jul 13, 2018 at 04:05:42PM +0200, Mikolaj Izdebski wrote: On 07/12/2018 10:17 PM, Richard W.M. Jones wrote: Does each build start with its own fresh VM? Do you

Re: [HEADS UP] Removal of GCC from the buildroot

>>> On Jul 15, 2018, at 5:47 AM, Richard W.M. Jones wrote: >>> >>> On Fri, Jul 13, 2018 at 04:05:42PM +0200, Mikolaj Izdebski wrote: >>> On 07/12/2018 10:17 PM, Richard W.M. Jones wrote: >>> Does each build start with its own fresh VM? Do you care about the >>> data in that build VM if either

Re: [HEADS UP] Removal of GCC from the buildroot

On Sun, Jul 8, 2018 at 1:46 PM, Igor Gnatenko wrote: As per 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

Re: [HEADS UP] Removal of GCC from the buildroot

Dne 12.7.2018 v 18:00 Mikolaj Izdebski napsal(a): > On 07/11/2018 10:27 PM, Zbigniew Jędrzejewski-Szmek wrote: >> The effects of fsync are impossible to see unless you hard-reboot the >> machine. (OK, strictly speaking, you can time the fsync call, but let's >> ignore that). I'd be more worried

Re: [HEADS UP] Removal of GCC from the buildroot

On Fri, 2018-07-13 at 12:39 +0200, Igor Gnatenko wrote: > On Fri, Jul 13, 2018, 11:19 Miro Hrončok wrote: > > On 8.7.2018 20:46, Igor Gnatenko wrote: > > > As per Changes/Remove GCC from BuildRoot > > > > >, I'm > > > going to

Re: [HEADS UP] Removal of GCC from the buildroot

On Thu, Jul 12, 2018 at 09:17:41PM +0100, Richard W.M. Jones wrote: > On Thu, Jul 12, 2018 at 02:10:37PM -0400, Cole Robinson wrote: > > On 07/11/2018 04:37 PM, Kevin Fenzi wrote: > > > On 07/11/2018 12:57 PM, Mikolaj Izdebski wrote: > > >> On 07/11/2018 09:26 PM, Kevin Fenzi wrote: > > >>> I

Re: [HEADS UP] Removal of GCC from the buildroot

On Mon, 2018-07-16 at 09:27 -0400, Cole Robinson wrote: > On 07/15/2018 11:47 AM, Richard W.M. Jones wrote: > > On Fri, Jul 13, 2018 at 04:05:42PM +0200, Mikolaj Izdebski wrote: > > > On 07/12/2018 10:17 PM, Richard W.M. Jones wrote: > > > > Does each build start with its own fresh VM? Do you

Re: [HEADS UP] Removal of GCC from the buildroot

On 10/07/18 08:42 +0100, Tomasz Kłoczko wrote: Do you see whole context now? No, because I stopped reading. Too longwinded, too much rambling. Try to express yourself more concisely. ___ devel mailing list -- devel@lists.fedoraproject.org To

Re: [HEADS UP] Removal of GCC from the buildroot

On Fri, Jul 13, 2018 at 12:39:55PM +0200, Igor Gnatenko wrote: > 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]

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/15/2018 11:47 AM, Richard W.M. Jones wrote: > On Fri, Jul 13, 2018 at 04:05:42PM +0200, Mikolaj Izdebski wrote: >> On 07/12/2018 10:17 PM, Richard W.M. Jones wrote: >>> Does each build start with its own fresh VM? Do you care about the >>> data in that build VM if either qemu or the host

Re: [HEADS UP] Removal of GCC from the buildroot

On Mon, Jul 16, 2018 at 7:29 AM Federico Bruni wrote: > > > Il giorno ven 13 lug 2018 alle 12:39, Igor Gnatenko > ha scritto: > > On Fri, Jul 13, 2018, 11:19 Miro Hrončok wrote: > >> On 8.7.2018 20:46, Igor Gnatenko wrote: > >> > As per Changes/Remove GCC from BuildRoot > >> > > >>

Re: [HEADS UP] Removal of GCC from the buildroot

Il giorno ven 13 lug 2018 alle 12:39, Igor Gnatenko ha scritto: On Fri, Jul 13, 2018, 11:19 Miro Hrončok wrote: On 8.7.2018 20:46, Igor Gnatenko wrote: > As per Changes/Remove GCC from BuildRoot > , I'm > going to

Re: [HEADS UP] Removal of GCC from the buildroot

On Fri, Jul 13, 2018 at 04:05:42PM +0200, Mikolaj Izdebski wrote: > On 07/12/2018 10:17 PM, Richard W.M. Jones wrote: > > Does each build start with its own fresh VM? Do you care about the > > data in that build VM if either qemu or the host crashes? If the > > answers are 'Yes' and 'No'

Re: [HEADS UP] Removal of GCC from the buildroot

This bit the bcache-tools package too, which I fixed. On 07/13/2018 12:39 PM, Igor Gnatenko wrote: On Fri, Jul 13, 2018, 11:19 Miro Hrončok > wrote: On 8.7.2018 20:46, Igor Gnatenko wrote: > As per Changes/Remove GCC from BuildRoot >

Re: [HEADS UP] Removal of GCC from the buildroot

> On Jul 12, 2018, at 4:26 AM, Simo Sorce wrote: > >> On Thu, 2018-07-12 at 07:32 +, Petr Pisar wrote: >>> On 2018-07-11, Zbigniew Jędrzejewski-Szmek wrote: >>> The effects of fsync are impossible to see unless you hard-reboot >>> the >>> machine. >> >> Are you sure non-fsynced changes are

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/12/2018 10:17 PM, Richard W.M. Jones wrote: > On Thu, Jul 12, 2018 at 02:10:37PM -0400, Cole Robinson wrote: >> On 07/11/2018 04:37 PM, Kevin Fenzi wrote: >>> On 07/11/2018 12:57 PM, Mikolaj Izdebski wrote: On 07/11/2018 09:26 PM, Kevin Fenzi wrote: > I don't see the cache=unsafe

Re: [HEADS UP] Removal of GCC from the buildroot

On 13.7.2018 12:39, Igor Gnatenko wrote: On Fri, Jul 13, 2018, 11:19 Miro Hrončok > wrote: On 8.7.2018 20:46, Igor Gnatenko wrote: > As per Changes/Remove GCC from BuildRoot > , I'm

Re: [HEADS UP] Removal of GCC from the buildroot

On Fri, Jul 13, 2018 at 12:39:55PM +0200, Igor Gnatenko wrote: > On Fri, Jul 13, 2018, 11:19 Miro Hrončok wrote: > > On 8.7.2018 20:46, Igor Gnatenko wrote: > > > As per Changes/Remove GCC from BuildRoot > > > , I'm > > > going to

Re: [HEADS UP] Removal of GCC from the buildroot

On Fri, Jul 13, 2018, 11:19 Miro Hrončok wrote: > On 8.7.2018 20:46, Igor Gnatenko wrote: > > As per Changes/Remove GCC from BuildRoot > > , I'm > > going to automatically add BuildRequires: gcc and/or BuildRequires: > > gcc-c++

Re: [HEADS UP] Removal of GCC from the buildroot

On 8.7.2018 20:46, Igor Gnatenko wrote: As per 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:

Re: [HEADS UP] Removal of GCC from the buildroot

On Thu, Jul 12, 2018 at 02:10:37PM -0400, Cole Robinson wrote: > On 07/11/2018 04:37 PM, Kevin Fenzi wrote: > > On 07/11/2018 12:57 PM, Mikolaj Izdebski wrote: > >> On 07/11/2018 09:26 PM, Kevin Fenzi wrote: > >>> I don't see the cache=unsafe anywhere (although the name sure makes me > >>> want to

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 04:37 PM, Kevin Fenzi wrote: > On 07/11/2018 12:57 PM, Mikolaj Izdebski wrote: >> On 07/11/2018 09:26 PM, Kevin Fenzi wrote: >>> On 07/11/2018 10:53 AM, Mikolaj Izdebski wrote: On 07/11/2018 07:31 PM, Andrew Lutomirski wrote: > On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 10:27 PM, Zbigniew Jędrzejewski-Szmek wrote: > The effects of fsync are impossible to see unless you hard-reboot the > machine. (OK, strictly speaking, you can time the fsync call, but let's > ignore that). I'd be more worried about some side-effects of the way > that nosync is

Re: [HEADS UP] Removal of GCC from the buildroot

Once upon a time, Petr Pisar said: > On 2018-07-11, Zbigniew Jędrzejewski-Szmek wrote: > > The effects of fsync are impossible to see unless you hard-reboot the > > machine. > > Are you sure non-fsynced changes are are guaranteed to be visible on > block cache level? E.g. if you mix read/write

Re: [HEADS UP] Removal of GCC from the buildroot

On Thu, 2018-07-12 at 07:32 +, Petr Pisar wrote: > On 2018-07-11, Zbigniew Jędrzejewski-Szmek wrote: > > The effects of fsync are impossible to see unless you hard-reboot > > the > > machine. > > Are you sure non-fsynced changes are are guaranteed to be visible on > block cache level? E.g.

Re: [HEADS UP] Removal of GCC from the buildroot

On Thu, Jul 12, 2018 at 07:32:19AM +, Petr Pisar wrote: > On 2018-07-11, Zbigniew Jędrzejewski-Szmek wrote: > > The effects of fsync are impossible to see unless you hard-reboot the > > machine. > > Are you sure non-fsynced changes are are guaranteed to be visible on > block cache level?

Re: [HEADS UP] Removal of GCC from the buildroot

On 2018-07-11, Zbigniew Jędrzejewski-Szmek wrote: > The effects of fsync are impossible to see unless you hard-reboot the > machine. Are you sure non-fsynced changes are are guaranteed to be visible on block cache level? E.g. if you mix read/write and mmaped I/O from different processes? > I

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 12:57 PM, Mikolaj Izdebski wrote: > On 07/11/2018 09:26 PM, Kevin Fenzi wrote: >> On 07/11/2018 10:53 AM, Mikolaj Izdebski wrote: >>> On 07/11/2018 07:31 PM, Andrew Lutomirski wrote: On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj Izdebski wrote: > > The slowest parts

Re: [HEADS UP] Removal of GCC from the buildroot

On Wed, Jul 11, 2018 at 08:27:22PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Wed, Jul 11, 2018 at 12:26:01PM -0700, Kevin Fenzi wrote: > > On 07/11/2018 10:53 AM, Mikolaj Izdebski wrote: > > > On 07/11/2018 07:31 PM, Andrew Lutomirski wrote: > > >> On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj

Re: [HEADS UP] Removal of GCC from the buildroot

On Wed, Jul 11, 2018 at 12:26:01PM -0700, Kevin Fenzi wrote: > On 07/11/2018 10:53 AM, Mikolaj Izdebski wrote: > > On 07/11/2018 07:31 PM, Andrew Lutomirski wrote: > >> On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj Izdebski > >> wrote: > >>> > >>> The slowest parts of setting up chroot is writing

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 09:26 PM, Kevin Fenzi wrote: > On 07/11/2018 10:53 AM, Mikolaj Izdebski wrote: >> On 07/11/2018 07:31 PM, Andrew Lutomirski wrote: >>> On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj Izdebski >>> wrote: The slowest parts of setting up chroot is writing packages to disk,

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 10:53 AM, Mikolaj Izdebski wrote: > On 07/11/2018 07:31 PM, Andrew Lutomirski wrote: >> On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj Izdebski >> wrote: >>> >>> The slowest parts of setting up chroot is writing packages to disk, >>> synchronously. This part can be speeded up a lot by

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 07:31 PM, Andrew Lutomirski wrote: > On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj Izdebski > wrote: >> >> On 07/11/2018 06:37 PM, Andrew Lutomirski wrote: >>> From my perspective as an occasional Fedora packager, I'm regularly >>> surprised by just how long it takes for Koji builders

Re: [HEADS UP] Removal of GCC from the buildroot

On Wed, Jul 11, 2018 at 10:08 AM, Mikolaj Izdebski wrote: > > On 07/11/2018 06:37 PM, Andrew Lutomirski wrote: > > From my perspective as an occasional Fedora packager, I'm regularly > > surprised by just how long it takes for Koji builders to install > > dependencies. I've never tried to dig in

Re: [HEADS UP] Removal of GCC from the buildroot

Jan Kratochvil wrote: > There is no C/C++ language. There are two orthogonal languages, C and > C++. (And some people say C++11 and C++03 are also orthogonal.) Yes, C and C++ are divergent languages (I wouldn't call them "orthogonal", but they are definitely different things), but gcc-c++

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 10:01 AM, Jan Kratochvil wrote: > On Wed, 11 Jul 2018 18:26:23 +0200, Josh Stone wrote: >> So I hear you like compile-time safety... >> >> No, I don't seriously want to get into a language comparison here, >> except to say that it's reasonable for the world to expand beyond C/C++, >

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 06:37 PM, Andrew Lutomirski wrote: > From my perspective as an occasional Fedora packager, I'm regularly > surprised by just how long it takes for Koji builders to install > dependencies. I've never tried to dig in too far, but it looks like the > builders download package metadata,

Re: [HEADS UP] Removal of GCC from the buildroot

On Wed, Jul 11, 2018, at 12:37 PM, Andrew Lutomirski wrote: > > (Hmm. Some future version of rpm/dnf could get really fancy and > *reflink* > package contents into the build chroot rather than untarring them every > time.) Try `rpm-ostree ex container` today and see just how fast it is to

Re: [HEADS UP] Removal of GCC from the buildroot

On Wed, 11 Jul 2018 18:26:23 +0200, Josh Stone wrote: > So I hear you like compile-time safety... > > No, I don't seriously want to get into a language comparison here, > except to say that it's reasonable for the world to expand beyond C/C++, There is no C/C++ language. There are two

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, Jul 10, 2018 at 1:13 PM, Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Tue, Jul 10, 2018 at 06:03:33PM +0200, Igor Gnatenko wrote: > > On Tue, Jul 10, 2018 at 5:52 PM Kevin Kofler > wrote: > > > > > Igor Gnatenko wrote: > > > > As per Changes/Remove GCC from BuildRoot > >

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/11/2018 07:37 AM, Kevin Kofler wrote: > Igor Gnatenko wrote: >> A lot of packages in 2018 are not written in C/C++ > > … and this is the problem that needs fixing. > > It is just a PITA to have packages dragging in more and more interpreters > and/or language runtimes. The slowness and

Re: [HEADS UP] Removal of GCC from the buildroot

On Wed, 2018-07-11 at 16:37 +0200, Kevin Kofler wrote: > Igor Gnatenko wrote: > > A lot of packages in 2018 are not written in C/C++ > > … and this is the problem that needs fixing. > > It is just a PITA to have packages dragging in more and more interpreters > and/or language runtimes. The

Re: [HEADS UP] Removal of GCC from the buildroot

Igor Gnatenko wrote: > A lot of packages in 2018 are not written in C/C++ … and this is the problem that needs fixing. It is just a PITA to have packages dragging in more and more interpreters and/or language runtimes. The slowness and lack of compile-time type safety of interpreted languages

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, 2018-07-10 at 08:42 +0100, Tomasz Kłoczko wrote: > On Tue, 10 Jul 2018 at 06:37, David Tardon > wrote: > [..] > > > My proposition is *not* to add gcc/g++ explicit to BuildReequires > > > and > > > use instead glibc-devel and libstdc++-devel modifications and ban > > > use > > >

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, Jul 10, 2018 at 06:03:33PM +0200, Igor Gnatenko wrote: > On Tue, Jul 10, 2018 at 5:52 PM Kevin Kofler wrote: > > > Igor Gnatenko wrote: > > > As per Changes/Remove GCC from BuildRoot > > > , I'm > > > going to

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, Jul 10, 2018 at 5:52 PM Kevin Kofler wrote: > Igor Gnatenko wrote: > > As per Changes/Remove GCC from BuildRoot > > , I'm > > going to automatically add BuildRequires: gcc and/or BuildRequires: > > gcc-c++ to packages

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, Jul 10, 2018 at 05:44:50PM +0200, Kevin Kofler wrote: > I still think that this change is absolutely counterproductive, because it > will actually INCREASE local mock build times for all C/C++ programs for all > packagers, because gcc and gcc-c++ will no longer be included in the root

Re: [HEADS UP] Removal of GCC from the buildroot

On Tuesday, July 10, 2018 5:44:50 PM CEST Kevin Kofler wrote: > Igor Gnatenko wrote: > > > As per Changes/Remove GCC from BuildRoot > > , I'm > > going to automatically add BuildRequires: gcc and/or BuildRequires: > > gcc-c++ to

Re: [HEADS UP] Removal of GCC from the buildroot

Igor Gnatenko wrote: > As per 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

Re: [HEADS UP] Removal of GCC from the buildroot

- Original Message - > From: "Tomasz Kłoczko" > To: "Development discussions related to Fedora" > > Sent: Tuesday, July 10, 2018 2:27:40 PM > Subject: Re: [HEADS UP] Removal of GCC from the buildroot > > On Tue, 10 Jul 2018 at 12:52, Till M

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, Jul 10, 2018 at 3:12 PM Vít Ondruch wrote: > > > Dne 10.7.2018 v 14:03 Tomasz Kłoczko napsal(a): > > On Tue, 10 Jul 2018 at 12:26, Tomasz Kłoczko > wrote: > > [..] > >> # dnf -C repoquery --qf "%{name}.%{arch} %{source_name} %{reponame}" | > >> grep -w rawhide | grep x86_64 | awk

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, 10 Jul 2018 at 10:57, Vít Ondruch wrote: [..] > Explicit "BR: gcc" definitely does the switch to other compiler easier, > because one of the main question for this change was actually "how many > packages actually requires C/C++" and it was quite tricky to answer such > question. Now it

Re: [HEADS UP] Removal of GCC from the buildroot

Dne 10.7.2018 v 14:03 Tomasz Kłoczko napsal(a): > On Tue, 10 Jul 2018 at 12:26, Tomasz Kłoczko wrote: > [..] >> # dnf -C repoquery --qf "%{name}.%{arch} %{source_name} %{reponame}" | >> grep -w rawhide | grep x86_64 | awk '{print $2}' | sort | uniq | wc -l >> Last metadata expiration check:

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, 10 Jul 2018 at 13:35, Tomasz Kłoczko wrote: > IMO even if he has some potential I'm guessing that he is still > relatively young and if it is true he may still need proper mentoring Not cool, you stepped over the line. Igor has done some great work in Fedora in the last few months.

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, 10 Jul 2018 at 12:52, Till Maas wrote: [..] > > PS. And really I don't care that again above will be taken as kind of > > personal attack (which is not my intention). > > The Fedora Code of Conduct is not optional therefore I expect you to > care about this. If you believe your e-mail

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, 10 Jul 2018 at 12:26, Tomasz Kłoczko wrote: [..] > # dnf -C repoquery --qf "%{name}.%{arch} %{source_name} %{reponame}" | > grep -w rawhide | grep x86_64 | awk '{print $2}' | sort | uniq | wc -l > Last metadata expiration check: 0:03:06 ago on Tue 10 Jul 2018 12:17:44 BST. > 9314 Just

Re: [HEADS UP] Removal of GCC from the buildroot

Hi, On Tue, Jul 10, 2018 at 08:42:09AM +0100, Tomasz Kłoczko wrote: > At the bottom I want only flag that people like Igor as they have > proven packager perms are able to make at the end more harm than good. > I don't know him (how experienced developer he really is) as my only > personal

Re: [HEADS UP] Removal of GCC from the buildroot

Dne 10.7.2018 v 09:42 Tomasz Kłoczko napsal(a): > On Tue, 10 Jul 2018 at 06:37, David Tardon wrote: > [..] >>> My proposition is *not* to add gcc/g++ explicit to BuildReequires and >>> use instead glibc-devel and libstdc++-devel modifications and ban use >>> gcc/gcc-c++ in BuildRequires (in

Re: [HEADS UP] Removal of GCC from the buildroot

On Tue, 10 Jul 2018 at 06:37, David Tardon wrote: [..] > > My proposition is *not* to add gcc/g++ explicit to BuildReequires and > > use instead glibc-devel and libstdc++-devel modifications and ban use > > gcc/gcc-c++ in BuildRequires (in most of the cases all current > > gcc/g++ > >

Re: [HEADS UP] Removal of GCC from the buildroot

On Mon, 2018-07-09 at 17:45 +0100, Tomasz Kłoczko wrote: > On Mon, 9 Jul 2018 at 16:42, Przemek Klosowski > wrote: > [..] > > > > After which, I'm going to ask rel-eng to finally remove it from > > > > buildroot. This will happen before mass rebuild. Stay tuned. > > > > > > After adding

Re: [HEADS UP] Removal of GCC from the buildroot

- Original Message - > From: "Tomasz Kłoczko" > To: "Development discussions related to Fedora" > > Sent: Monday, July 9, 2018 6:45:28 PM > Subject: Re: [HEADS UP] Removal of GCC from the buildroot > > On Mon, 9 Jul 2018 at 16:42, Przemek Klos

Re: [HEADS UP] Removal of GCC from the buildroot

On Mon, 9 Jul 2018 at 16:42, Przemek Klosowski wrote: [..] > >> After which, I'm going to ask rel-eng to finally remove it from buildroot. > >> This will happen before mass rebuild. Stay tuned. > > After adding explicite gcc/g++ in BuildRequires it will be extreamly > > hard to switch use for

Re: [HEADS UP] Removal of GCC from the buildroot

On 07/09/2018 11:15 AM, Tomasz Kłoczko wrote: On Sun, 8 Jul 2018 at 19:57, Igor Gnatenko wrote: As per 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

Re: [HEADS UP] Removal of GCC from the buildroot

On Sun, 8 Jul 2018 at 19:57, Igor Gnatenko wrote: > > As per 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

[HEADS UP] Removal of GCC from the buildroot

As per 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