This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 05/10] Remove __need macros from errno.h (__need_Emath, __need_error_t).


On 05/15/2017 10:11 AM, Andreas Schwab wrote:
On Mai 12 2017, Florian Weimer <fweimer@redhat.com> wrote:

On 05/11/2017 07:25 PM, Andreas Schwab wrote:
On Mai 11 2017, Florian Weimer <fweimer@redhat.com> wrote:

On 05/11/2017 05:42 PM, Andreas Schwab wrote:
On Mai 11 2017, Joseph Myers <joseph@codesourcery.com> wrote:

* Requiring GCC 5 as minimum GCC version for building glibc on the basis
of what's maintained upstream (though that's more aggressive than we've
previously been on increasing GCC version requirements).  (Versions before
4.9 don't work with build-many-glibcs.py anyway.)

openSUSE Leap 42.2 (aka SLE 12) has gcc 4.8 as the system compiler.

Is it possible to use the Toolchain Module to get a newer GCC version?

Both Leap and the toolchain module offer gcc5 and gcc6.  But what you
call as gcc will remain 4.8.

Do you think that results in a major inconvenience?

You have to remember to point both CC and CXX to the newer compiler.

Sure, but that doesn't answer my question. I think it's just a minor burden which isn't much of a problem and should not block bumping the minimum GCC requirement.

Do you agree?

Is the toolchain module GCC available on PATH? Maybe we could add some fallback detection logic for a suitable compiler, similar to how a Bourne shell is located on Solaris.

Thanks,
Florian


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]