On 06.01.20 15:02, Wilco Dijkstra wrote:
>> However, this is an undocumented change in the current NEWS, and seeing
>>> literally hundreds of package failures, I doubt that's the right thing to
>>> do, at
>>> least without any deprecation warning first. Could that be handled,
>>> deprecating
>>>
On Mon, 6 Jan 2020 at 13:37, Martin Liška wrote:
>
> On 1/6/20 2:29 PM, Matthias Klose wrote:
> > On 06.01.20 13:30, Wilco Dijkstra wrote:
> >> On 06.01.20 11:03, Andrew Pinski wrote:
> >>> +GCC
> >>>
> >>> On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose wrote:
>
> In an archive test rebu
On Mon, Jan 6, 2020 at 6:02 AM Wilco Dijkstra wrote:
>
>
> Hi,
>
> > However, this is an undocumented change in the current NEWS, and seeing
> >> literally hundreds of package failures, I doubt that's the right thing to
> >> do, at
> >> least without any deprecation warning first. Could that be
Hi,
> However, this is an undocumented change in the current NEWS, and seeing
>> literally hundreds of package failures, I doubt that's the right thing to
>> do, at
>> least without any deprecation warning first. Could that be handled,
>> deprecating
>> in GCC 10 first, and the changing t
On Mon, Jan 6, 2020 at 5:29 AM Matthias Klose wrote:
>
> On 06.01.20 13:30, Wilco Dijkstra wrote:
> > On 06.01.20 11:03, Andrew Pinski wrote:
> >> +GCC
> >>
> >> On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose wrote:
> >>>
> >>> In an archive test rebuild with binutils and GCC trunk, I see a lot of
On 1/6/20 2:29 PM, Matthias Klose wrote:
On 06.01.20 13:30, Wilco Dijkstra wrote:
On 06.01.20 11:03, Andrew Pinski wrote:
+GCC
On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose wrote:
In an archive test rebuild with binutils and GCC trunk, I see a lot of build
failures on both aarch64-linux-gnu
On 06.01.20 14:29, Matthias Klose wrote:
> On 06.01.20 13:30, Wilco Dijkstra wrote:
>> On 06.01.20 11:03, Andrew Pinski wrote:
>>> +GCC
>>>
>>> On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose wrote:
In an archive test rebuild with binutils and GCC trunk, I see a lot of
build
fai
On 06.01.20 13:30, Wilco Dijkstra wrote:
> On 06.01.20 11:03, Andrew Pinski wrote:
>> +GCC
>>
>> On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose wrote:
>>>
>>> In an archive test rebuild with binutils and GCC trunk, I see a lot of build
>>> failures on both aarch64-linux-gnu and arm-linux-gnueabihf
On 06.01.20 11:03, Andrew Pinski wrote:
> +GCC
>
> On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose wrote:
>>
>> In an archive test rebuild with binutils and GCC trunk, I see a lot of build
>> failures on both aarch64-linux-gnu and arm-linux-gnueabihf failing with
>> "multiple definition of symbols"
On 06.01.20 11:03, Andrew Pinski wrote:
> +GCC
>
> On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose wrote:
>>
>> In an archive test rebuild with binutils and GCC trunk, I see a lot of build
>> failures on both aarch64-linux-gnu and arm-linux-gnueabihf failing with
>> "multiple definition of symbols"
+GCC
On Mon, Jan 6, 2020 at 1:52 AM Matthias Klose wrote:
>
> In an archive test rebuild with binutils and GCC trunk, I see a lot of build
> failures on both aarch64-linux-gnu and arm-linux-gnueabihf failing with
> "multiple definition of symbols" when linking executables, e.g.
THIS IS NOT A BIN
11 matches
Mail list logo
