On Sat, Nov 05, 2016 at 11:44:00AM +, Ximin Luo wrote:
> >> Many software packages (e.g. see #833846) like to set optimisation flags
> >> based
> I was exaggerating sorry. "some" would match better what I saw myself
> directly.
ah. (happens all the time :)
> As for detection, we could get
Holger Levsen:
> Hi Ximin,
>
> On Tue, Aug 09, 2016 at 02:08:45PM +0200, Ximin Luo wrote:
>> Many software packages (e.g. see #833846) like to set optimisation flags
>> based
>> on autodetecting CPU features of the build machine.
>
> do you really say/think that *many* packages in *Debian* have
Control: reassign -1 gcc-6
[ Leaving enough context for gcc maintainers. ]
On Tue, 2016-08-09 at 14:08:45 +0200, Ximin Luo wrote:
> Package: dpkg-dev
> Version: 1.18.10
> Severity: wishlist
> Many software packages (e.g. see #833846) like to set optimisation
> flags based on autodetecting CPU fe
Ximin Luo:
> [..] in practise package maintainers will just disable all build-time CPU
> detection to avoid generating illegal instructions. [..]
A slight logical clarification here - not only do maintainers disable
build-time CPU detection, but in most cases they will end up disabling *all*
optim
Package: dpkg-dev
Version: 1.18.10
Severity: wishlist
Dear Maintainer,
Many software packages (e.g. see #833846) like to set optimisation flags based
on autodetecting CPU features of the build machine. Of course this is not
suitable for binary distributors in general, and for Debian package maint
5 matches
Mail list logo
