* Matthias Klose:
> ok, now removing that leads to:
>
> $ cat foo.c
> #include
>
> $ gcc -c foo.c
> In file included from foo.c:1:
> /usr/include/limits.h:124:26: error: no include path in which to search for
> limits.h
> 124 | # include_next
> | ^
>
>
On 3/4/20 9:48 AM, Florian Weimer wrote:
> * Matthias Klose:
>
>> On 3/4/20 9:33 AM, Florian Weimer wrote:
>>> * Matthias Klose:
>>>
The __glibc_has_include macro needs to be restored until GCC is rebuilt. At
least on s390x, you get a non-wrorking compiler, which at least cannot
On 3/4/20 10:04 PM, Aurelien Jarno wrote:
> On 2020-03-04 09:33, Matthias Klose wrote:
>> Package: src:glibc
>> Version: 2.30-0experimental2
>> Severity: important
>> Tags: sid bullseye patch
>>
>> The __glibc_has_include macro needs to be restored until GCC is rebuilt. At
>
> I am fine reverting
On 2020-03-04 09:33, Matthias Klose wrote:
> Package: src:glibc
> Version: 2.30-0experimental2
> Severity: important
> Tags: sid bullseye patch
>
> The __glibc_has_include macro needs to be restored until GCC is rebuilt. At
I am fine reverting temporarily that commit. But it fixes a real issue,
* Matthias Klose:
> On 3/4/20 9:33 AM, Florian Weimer wrote:
>> * Matthias Klose:
>>
>>> The __glibc_has_include macro needs to be restored until GCC is rebuilt. At
>>> least on s390x, you get a non-wrorking compiler, which at least cannot glibc
>>> anymore. The macro is still referenced in the
On 3/4/20 9:33 AM, Florian Weimer wrote:
> * Matthias Klose:
>
>> The __glibc_has_include macro needs to be restored until GCC is rebuilt. At
>> least on s390x, you get a non-wrorking compiler, which at least cannot glibc
>> anymore. The macro is still referenced in the include-fixed directory.
Package: src:glibc
Version: 2.30-0experimental2
Severity: important
Tags: sid bullseye patch
The __glibc_has_include macro needs to be restored until GCC is rebuilt. At
least on s390x, you get a non-wrorking compiler, which at least cannot glibc
anymore. The macro is still referenced in the
7 matches
Mail list logo
