> On Nov 27, 2016, at 2:14 PM, Matthias Klose wrote:
>
> The patches to configure --with-cpu-32= and --with-cpu-64= are availabe in GCC
> 6, so we should use them and ensure that the defaults for the sparc/64 and
> sparc64, and sparc and sparc64/32 targets match. Just forcing
On 24.11.2016 19:10, Jose E. Marchesi wrote:
>
> I'm pretty confident that --with-cpu=ultrasparc won't do any harm in
> 64-bit mode, but Jose (CC'ed as gcc upstream) will hopefully correct
> me here if I'm wrong.
>
> The cpu selected in --with-cpu impacts both -m64 and -m32 in a
I'm pretty confident that --with-cpu=ultrasparc won't do any harm in
64-bit mode, but Jose (CC'ed as gcc upstream) will hopefully correct
me here if I'm wrong.
The cpu selected in --with-cpu impacts both -m64 and -m32 in a biarch
compiler. However, I can't say anything about the
> On Nov 24, 2016, at 7:07 PM, Jose E. Marchesi
> wrote:
>
> Ah, I thought you said that GCC 6 was not building anymore with
> --mcpu=ultrasparc due to some bug. You mean that the debian package is
> no longer using that option.
Yes, but only the Debian package on
> Currently, rebootstrap fails on sparc-linux-gnu because the gcc-6
> package no longer builds with --mcpu=ultrasparc on this target.
> This was previously with the sparc-force-cpu.diff patch which
> got removed while fixing the multilib issue on sparc64.
>
On 11/24/2016 06:34 PM, Jose E. Marchesi wrote:
>
> Currently, rebootstrap fails on sparc-linux-gnu because the gcc-6
> package no longer builds with --mcpu=ultrasparc on this target.
> This was previously with the sparc-force-cpu.diff patch which
> got removed while fixing
Currently, rebootstrap fails on sparc-linux-gnu because the gcc-6
package no longer builds with --mcpu=ultrasparc on this target.
This was previously with the sparc-force-cpu.diff patch which
got removed while fixing the multilib issue on sparc64.
What is the issue with GCC 6
Control: tags -1 - patch
On 23.11.2016 18:58, John Paul Adrian Glaubitz wrote:
> Hi Matthias!
>
> On 11/23/2016 06:09 PM, Matthias Klose wrote:
>> why do you set this for the 64bit multilib as well?
>
> I was actually hoping you would comment on this :). I wasn't sure whether the
> conditional
Processing control commands:
> tags -1 - patch
Bug #845461 [src:gcc-6] gcc-6: Please build with --with-cpu=ultrasparc on sparc
Removed tag(s) patch.
--
845461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi Matthias!
On 11/23/2016 06:09 PM, Matthias Klose wrote:
> why do you set this for the 64bit multilib as well?
I was actually hoping you would comment on this :). I wasn't sure whether the
conditional is correct, I just had a look at a previous change in debian/rules2
which mentioned v9 in
On 23.11.2016 17:52, John Paul Adrian Glaubitz wrote:
> Currently, rebootstrap fails on sparc-linux-gnu because the gcc-6
> package no longer builds with --mcpu=ultrasparc on this target.
> This was previously with the sparc-force-cpu.diff patch which
> got removed while fixing the multilib issue
Source: gcc-6
Version: 6_6.2.1-4
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Hello!
Currently, rebootstrap fails on sparc-linux-gnu because the gcc-6
package no longer builds with --mcpu=ultrasparc on this target.
This was previously with the sparc-force-cpu.diff
12 matches
Mail list logo