Bug#875703: debcrossgen defaults to a non-default gcc

2017-10-11 Thread Jussi Pakkanen
On Wed, Oct 11, 2017 at 8:23 PM, Helmut Grohne wrote: >> Is cpu_family intended to describe a CPU family, or an ABI? Some CPU >> families have more than one incompatible ABI: > > It's not clear to me what the intention is. My experience matches yours > though: cpu and cpu_family are incapable of

Bug#875703: debcrossgen defaults to a non-default gcc

2017-10-11 Thread Simon McVittie
On Wed, 11 Oct 2017 at 19:23:09 +0200, Helmut Grohne wrote: > On Wed, Oct 11, 2017 at 09:37:42AM +0100, Simon McVittie wrote: > > If possible (and if it's not too late!) it would be great if this > > vocabulary reused some existing one (for example GNU CPU types, which > > in fact debcrossgen assum

Bug#875703: debcrossgen defaults to a non-default gcc

2017-10-11 Thread Helmut Grohne
Hi Simon, Thanks for looking into this issue! On Wed, Oct 11, 2017 at 09:37:42AM +0100, Simon McVittie wrote: > On Wed, 13 Sep 2017 at 21:01:43 +0200, Helmut Grohne wrote: > > debarch cpu cpu_family > > armel arm armv7l > > Is this a typo, or is this really what Meson does? I would exp

Bug#875703: debcrossgen defaults to a non-default gcc

2017-10-11 Thread Simon McVittie
On Wed, 13 Sep 2017 at 21:01:43 +0200, Helmut Grohne wrote: > debarch cpu cpu_family > armel arm armv7l Is this a typo, or is this really what Meson does? I would expect cpu=armv7hl and cpu_family=arm. Is cpu_family intended to describe a CPU family, or an ABI? Some CPU families have mo

Bug#875703: debcrossgen defaults to a non-default gcc

2017-09-14 Thread Jussi Pakkanen
On Thu, Sep 14, 2017 at 7:52 AM, Helmut Grohne wrote: >> This script should probably do the same thing as that one. With a bit >> of refactoring it could even import that function since it ships in >> the same (private) directory as the code itself. The problem here is that I don't have access t

Bug#875703: debcrossgen defaults to a non-default gcc

2017-09-13 Thread Helmut Grohne
On Thu, Sep 14, 2017 at 12:26:04AM +0300, Jussi Pakkanen wrote: > When compiling with Meson, CC and CXX must point to the native > compilers, not to cross compilers. If the crossgen tool uses CC that > means that debuild needs to first set it to the cross compiler, run > crossgen and then set it to

Bug#875703: debcrossgen defaults to a non-default gcc

2017-09-13 Thread Jussi Pakkanen
On Wed, Sep 13, 2017 at 10:01 PM, Helmut Grohne wrote: > I'm not sure why you felt the need to append a version, but my attached > patch supports your need by adding a --gccsuffix option to debcrossgen > while defaulting to an unversioned gcc as is expected by most Debian > packages. I also made

Bug#875703: debcrossgen defaults to a non-default gcc

2017-09-13 Thread Helmut Grohne
Package: meson Version: 0.42.1-1 File: /usr/share/meson/debcrossgen Tags: patch User: helm...@debian.org Usertags: rebootstrap Hi Jussi, Thanks for uploading debcrossgen. Unfortunately, the present debcrossgen is not useable, because it hard codes a non-default gcc (-6). Such a gcc is not install