Re: Re: Re: Re: Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

2018-03-01 Thread Nicolas Mailhot
Le mercredi 28 février 2018 à 21:11 -0500, Orcan Ogetbil a écrit : > On 28 February 2018 at 10:03, Nicolas Mailhot wrote: > > Le 2018-02-28 15:28, Orcan Ogetbil a écrit : > > > > > > On 28 February 2018 at 09:19, Nicolas Mailhot wrote: > > > > > > > These are all _very_ edge use-cases. > > > >

Re: Re: Re: Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

2018-02-28 Thread Orcan Ogetbil
On 28 February 2018 at 10:03, Nicolas Mailhot wrote: > Le 2018-02-28 15:28, Orcan Ogetbil a écrit : >> >> On 28 February 2018 at 09:19, Nicolas Mailhot wrote: > > >> These are all _very_ edge use-cases. > > > Those are *not* edge-cases. We have a few thousand build failures. If you cannot find as

Re: Re: Re: Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

2018-02-28 Thread Nicolas Mailhot
Le 2018-02-28 16:03, Nicolas Mailhot a écrit : Most system libraries are written in C/C++ so pretty much all the language toolchains we ship (except for toy languages not intended to produce complex apps) will read C/C++ header files from their compilers to use those system libraries, and will B

Re: Re: Re: Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

2018-02-28 Thread Nicolas Mailhot
Le 2018-02-28 15:28, Orcan Ogetbil a écrit : On 28 February 2018 at 09:19, Nicolas Mailhot wrote: These are all _very_ edge use-cases. Those are *not* edge-cases. Most system libraries are written in C/C++ so pretty much all the language toolchains we ship (except for toy languages not int

Re: Re: Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

2018-02-28 Thread Panu Matilainen
On 02/28/2018 04:28 PM, Orcan Ogetbil wrote: On 28 February 2018 at 09:19, Nicolas Mailhot wrote: My point was *non-C-compilers* can read *C/C++* header files because they need to read the ABI definitions to use it from their non C/C++ code. That makes a C/C++ header file consumable by pretty m

Re: Re: Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

2018-02-28 Thread Orcan Ogetbil
On 28 February 2018 at 09:19, Nicolas Mailhot wrote: > My point was *non-C-compilers* can read *C/C++* header files because they > need to read the ABI definitions to use it from their non C/C++ code. > > That makes a C/C++ header file consumable by pretty much any kind of > compiler, so it's *comp

Re: Re: Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

2018-02-28 Thread Nicolas Mailhot
My point was *non-C-compilers* can read *C/C++* header files because they need to read the ABI definitions to use it from their non C/C++ code. That makes a C/C++ header file consumable by pretty much any kind of compiler, so it's *completely useless* to try to make C/C++ devel packages pull