On Tue, 29 Nov 2011 12:17:54 +, Wookey wrote:
> I know almost nothing about mingw* use and variants, but it does strike
> me that it just another cross-compiler, and choices about package
> names and triplets should be at least influenced by what we do for all
> the other cross-toolchains, mul
+++ Ron [2011-11-14 03:03 +1030]:
> On Sun, Nov 13, 2011 at 01:17:43AM +0100, Stephen Kitt wrote:
> > I thought it better to follow the MinGW-w64 project's recommendations,
> > including using their triplets.
>
> > I'll try a build with the old triplets to see how that goes, and to figure
> > out
On Mon, 14 Nov 2011 03:03:16 +1030, Ron wrote:
> On Sun, Nov 13, 2011 at 01:17:43AM +0100, Stephen Kitt wrote:
> > There is one major difference I know of: i686-pc-mingw32 (the official
> > MinGW triplet) builds with Dwarf2 exception handling, whereas the
> > -w64-mingw32 (the official MinGW-w64 t
On Sun, Nov 13, 2011 at 01:17:43AM +0100, Stephen Kitt wrote:
> > On Thu, Nov 10, 2011 at 08:16:01PM +0100, Stephen Kitt wrote:
> > > As far as the naming is concerned, see #622276 for details. I've thought
> > > about splitting the packages up, with separate 32- and 64-bit targets, but
> > > I'm n
Hi Ron,
On Fri, 11 Nov 2011 07:36:28 +1030, Ron wrote:
> I was hoping you'd actually been cc'd on this :)
I was a few days behind debian-devel so I found out aboud the discussion
thanks to Fabian's bug report, which you will have received too ;-).
> On Thu, Nov 10, 2011 at 08:16:01PM +0100, Ste
Hi Stephen,
I was hoping you'd actually been cc'd on this :)
On Thu, Nov 10, 2011 at 08:16:01PM +0100, Stephen Kitt wrote:
> As far as the naming is concerned, see #622276 for details. I've thought
> about splitting the packages up, with separate 32- and 64-bit targets, but
> I'm not sure wheth
6 matches
Mail list logo
