From MAILER-DAEMON Sun Aug 04 11:31:27 2019 Received: from list by lists.gnu.org with archive (Exim 4.86_2) id 1huITn-0002mt-6V for mharc-mingw-cross-env-list@gnu.org; Sun, 04 Aug 2019 11:31:27 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:53469) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1huITk-0002kB-2n for mingw-cross-env-list@nongnu.org; Sun, 04 Aug 2019 11:31:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1huITi-00074T-Ml for mingw-cross-env-list@nongnu.org; Sun, 04 Aug 2019 11:31:24 -0400 Received: from mail.notjusthosting.com ([2a01:4f8:a0:10c3:1::1]:60688) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1huITi-00070E-G1 for mingw-cross-env-list@nongnu.org; Sun, 04 Aug 2019 11:31:22 -0400 Received: from [46.114.35.154] (helo=vlap) by mail.notjusthosting.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1huITd-00044l-LB for mingw-cross-env-list@nongnu.org; Sun, 04 Aug 2019 17:31:17 +0200 Date: Sun, 4 Aug 2019 17:31:16 +0200 From: Volker Diels-Grabsch To: mingw-cross-env-list@nongnu.org Message-ID: <20190804153116.GA16528@6153f789-1cf1-4ca3-8cea-6fa7ae195a8b.njh.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a01:4f8:a0:10c3:1::1 Subject: Re: [Mingw-cross-env-list] MXE: best thing since ice-cream X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Aug 2019 15:31:25 -0000 Dear bliako, Gilles and all others who shared their story, Thanks a lot for your congrats to MXE. As the creator of this project, I'm very proud of how MXE developed over the 12 years if its existence, even though I'm no longer active. While I was active, I was lucky that this project attracted some very skilled volunteers, who played astonishingly well in a team. When I realized that it becomes harder and harder for me to keep pace and to find enough spare time to manage and to improve MXE, I handed this project gradually over to this team. This team grew, with new people adding new packages, fighting until those work, ensuring these continue to work, and introducing modern ideas into the core of MXE, as well as modernizing the infrastructure around MXE. In short, this is the best development of the project I could have wished for. I'm very proud of the whole team. It is you who make me smile every time I look at MXE. I rarely build for Windows anymore. But from time to time I have to. It is you who ensured that whenever I needed MXE, it was still there, very alive and up to date. It is you who keep it alive, make it grow and ensure MXE becomes better every day. Thank you! Volker ah via Mingw-cross-env-list schrieb: > Dear MXE, > > Last night you saved me from the most humiliating, degrading, frustrating > and time-wasting experience a human developer could have. > > I am developing a Qt application to target both Linux, OSX and windows. My > development is done entirely in and for Linux, occassionally OSX. Buit this > time they needed that 3rd "OS" too. > > And so, last night I thought it was time I produced a windows executable to > give to testers. Coming from the unix world I thought that would be > straight-forward. Having not used windows for the last 5 years I thought > developing in/for them must have improved. I mean the world improves and > goes on. Alas, little I knew. > > I started a virtual machine of windows 8.1 and spent two hours removing > privacy infringement and opting out from all perverted use of my private > data. Then it was time to install Qt and visual studio and what not. > > QtCreator kept coming up with all these pathetic messages like clang++ can > not produce executables, cl can not be found, mingw-g++ targets a different > ABI, libQtXYZ.a can not be found (obviously because the Qt installed > QtXYZ.a) and on and on the ordeal went until the early hours. Windows > runtime detector can not be found. I tried everything included re-installing > Qt 4 or 5 times. I tried the command line but there things were not only > worse but that thing they call a terminal was plain hell to navigate, to > copy-paste, to retype commands, to copy paste paths with unix-separators, > QtCreator complained about. I had enough and re-installed the windows > virtual machine so that I never be tempted to try it again. > > Then I saw on the Qt forum someone advising that mxe could do > cross-compiling. And I said, yeah right! The whole micro$oft corporation can > not put this right and some hackers managed to put together and distribute > for free a system to not only compile this but CROSS-COMPILE??? That's a > mean task even for hardened hackers. > > I let the computer compile mxe and went to sleep without any expectations. > > Now I am back on the console and pleasantly surprised to see it did compile > and it did fetched hundreds of 3rd party packages and did compiled them too > without complain or a miss! Wow! (*) > > By following some very simple instructions, I managed to cross-compile my > application and all its 3rd-party dependencies without a glitch or a > complain. It even works on that platform from lleh. > > Guys and girls from MXE you are indispensable and you add good karma unlike > the corporate execs with the suits and the ties. > > Keep the good work you do, > > XXX > > bliako > > (*) with the exception of gcc. This was the very first package to be > downloaed and installed. But it failed with the message: > > Assembler messages: > Fatal error: no compiled in support for x86_64 > > But thankfully I found the solution in mxe forum here: > https://github.com/mxe/mxe/issues/173 > > Something in my PATH caused it to fail. By just setting it to something > minimal like: > > export PATH='/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin' > > it worked like a charm. > -- Volker Diels-Grabsch ----<<<((()))>>>---- From MAILER-DAEMON Mon Aug 05 13:29:47 2019 Received: from list by lists.gnu.org with archive (Exim 4.86_2) id 1hugnr-00040A-2T for mharc-mingw-cross-env-list@gnu.org; Mon, 05 Aug 2019 13:29:47 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:46503) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hugks-0003l2-DK for mingw-cross-env-list@nongnu.org; Mon, 05 Aug 2019 13:26:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hugkr-0005NB-7H for mingw-cross-env-list@nongnu.org; Mon, 05 Aug 2019 13:26:42 -0400 Received: from mail-wr1-x433.google.com ([2a00:1450:4864:20::433]:32940) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hugkq-0005Mr-QW for mingw-cross-env-list@nongnu.org; Mon, 05 Aug 2019 13:26:41 -0400 Received: by mail-wr1-x433.google.com with SMTP id n9so85333044wru.0 for ; Mon, 05 Aug 2019 10:26:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:date:message-id:subject:to; bh=wrbKUeJzujXBzWinCx2fvcxjyDwrx+ngCy648lzMGjA=; b=fFob3qRh6tkwO2tljde07VWANuBrhim9w8GFyV66lxuPGd54gKWbfMNYNBaTgHgWBC +wtEfdjDU92w4LpFzr8SW5vpIFohE7djZBs42VRLD09jj+4f+1JAvwTYHHrQK75pgzCP rO/Ls3uu2IbByeEHGdU16LwvV7JQDlA2AEaWkrxcraWVZD+gqlUunHOqV8FqsRymkvE7 NAeJiBlTbbGMJ+gh9wnQfyqwIlsdKAPnqJTthx/OsknQGOYchX/BMZJNiTu7FVkzucC1 xyPRghNqLv7nceorepXONtDjjjon8uKu8ctShW6zvdecJNZWF/1aMmayZmZlq8WqJKda cCWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=wrbKUeJzujXBzWinCx2fvcxjyDwrx+ngCy648lzMGjA=; b=IKaVwosfbirbfVS+kb00AveLCMv4SDM6TLJOQmzQhDrGImgOyU5ZEwM7jc3QFYPT43 uVx+/Rd4aY5P2irD3LEHg4sc+W/uFfDWFrc7qUZ49xwsf6rpOC9MjzAKZapUNtnqX5Ra cgPv4pXZqi22GNTzBvbZvpNiY2RUuxqRQspRv02HyZLieBuqxSPq4z5xJqn6dMwbtkk7 MB1Qsbw6mSrZQWSrS1jbiWsi7vTc7/urj4nfyoaTcF9PyTOoxi1uRRXjgDYnYvqt4rd2 dd5kuvzqi3FnKFLmM2FZXzr6v87JI/BgBN8lVk2wwNSqvj0FP+AH0sKtzBciJHLozyiy 6Kvw== X-Gm-Message-State: APjAAAVpp9E4Njy8FWwpnIgtjxvgXtNKY3T56s+jQkUg7jcEeSEWW/zg eAodlU7rtXMBo3b8adXTvgzg84OuOizILsnfnfcasSqD X-Google-Smtp-Source: APXvYqzTg1A6eVQr62MClZGjHpiglhXlshOPRQP/HfBnzoKw30YHpGF9WYrwNsIiQMHFpx3TrPSqzzLVMONPVT8IKk8= X-Received: by 2002:adf:de8e:: with SMTP id w14mr43701257wrl.79.1565025999029; Mon, 05 Aug 2019 10:26:39 -0700 (PDT) Received: from 895490483151 named unknown by gmailapi.google.com with HTTPREST; Mon, 5 Aug 2019 10:26:38 -0700 From: Gregorio Litenstein MIME-Version: 1.0 Date: Mon, 5 Aug 2019 10:26:38 -0700 Message-ID: To: mingw-cross-env-list@nongnu.org Content-Type: multipart/alternative; boundary="000000000000bc8b9a058f6202a9" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::433 X-Mailman-Approved-At: Mon, 05 Aug 2019 13:29:45 -0400 Subject: [Mingw-cross-env-list] On creating packages, source files and checksums. X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2019 17:26:43 -0000 --000000000000bc8b9a058f6202a9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I am asking this again since it got lost/ignored last time. Is it possible to create a package so that it downloads more than one source package? The reason I'm asking is because I'm trying to port rust; the problem is rust requires a bootstrap compiler that cannot be built from scratch, we _need_ to either download it or provide it somehow. One possible solution of course would be to have a package for each bootstrap component (there's 3; rustc, rust-std and cargo). That would probably work but would mean keeping bootstrap compilers around on the system after building the real compiler so it's far from ideal. Another solution maybe would be to make a single package containing both the source and the bootstrap binaries and host it somewhere; this is also not ideal because there would have to be one for each different OS supported by MXE. The ideal solution of course, would be to be able to have more than one source file for a package. Then I'd be able to pull all required components, check their checksum and get rid of them once they're no longer needed. Is that last option possible? And, in case it's not; is it possible to get around the no-download thing (I know this is very discouraged but if there's no other solution...) I promise to be good and verify checksums for anything I download! --=20 Gregorio Litenstein Goldzweig [image: glit_ind.png] M=C3=A9dico Cirujano - Fono: +56 9 96343643 <+56%209%2096343643> - E-Mail: g.litenstein@gmail.com --000000000000bc8b9a058f6202a9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I am asking this again since it got lost/ignored l= ast time.

Is it possible to create a package so that it = downloads more than one source package?

The reason= I'm asking is because I'm trying to port rust; the problem is rust= requires a bootstrap compiler that cannot be built from scratch, we _need_= to either download it or provide it somehow. One possible solution of cour= se would be to have a package for each bootstrap component (there's 3; = rustc, rust-std and cargo). That would probably work but would mean keeping= bootstrap compilers around on the system after building the real compiler = so it's far from ideal.

Another solution maybe= would be to make a single package containing both the source and the boots= trap binaries and host it somewhere; this is also not ideal because there w= ould have to be one for each different OS supported by MXE.

<= /div>
The ideal solution of course, would be to be able to have more th= an one source file for a package. Then I'd be able to pull all required= components, check their checksum and get rid of them once they're no l= onger needed.

Is that last option possible?
<= div>
And, in case it's not; is it possible to get around = the no-download thing (I know this is very discouraged but if there's n= o other solution...) I promise to be good and verify checksums for anything= I download!

--=C2=A0
=
Gregorio Litenstein Goldzweig=C2=A0
3D"glit_ind.p=
M=C3=A9dico Cirujano
=C2=A0
--000000000000bc8b9a058f6202a9-- From MAILER-DAEMON Sun Aug 11 05:42:36 2019 Received: from list by lists.gnu.org with archive (Exim 4.86_2) id 1hwkN2-0001fq-ES for mharc-mingw-cross-env-list@gnu.org; Sun, 11 Aug 2019 05:42:36 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:41891) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hwkMz-0001fh-9R for mingw-cross-env-list@nongnu.org; Sun, 11 Aug 2019 05:42:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hwkMx-0003up-ND for mingw-cross-env-list@nongnu.org; Sun, 11 Aug 2019 05:42:33 -0400 Received: from mail.notjusthosting.com ([2a01:4f8:a0:10c3:1::1]:54606) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hwkMx-0003sO-GY for mingw-cross-env-list@nongnu.org; Sun, 11 Aug 2019 05:42:31 -0400 Received: from p200300e22bd07d0028b7b80653f568bc.dip0.t-ipconnect.de ([2003:e2:2bd0:7d00:28b7:b806:53f5:68bc] helo=vlap) by mail.notjusthosting.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hwkMs-00033I-7L; Sun, 11 Aug 2019 11:42:26 +0200 Date: Sun, 11 Aug 2019 11:42:25 +0200 From: Volker Diels-Grabsch To: Gregorio Litenstein Cc: mingw-cross-env-list@nongnu.org Message-ID: <20190811094225.GA4203@6153f789-1cf1-4ca3-8cea-6fa7ae195a8b.njh.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a01:4f8:a0:10c3:1::1 Subject: Re: [Mingw-cross-env-list] On creating packages, source files and checksums. X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Aug 2019 09:42:34 -0000 Dear Gregorio, If I haven't missed a new feature in the MXE core, there's currently no way to have multiple source file per package. I believe in the past we solved similar issues as follows: Provide one dummy-package per source file, so they are downloaded and checked. The last ("main") package then depends on all others and performs the actual build(s). Alas, I wasn't able to find a concrete example of that approach at a first glance. But maybe you do. However, it is also possible that all packages which previously used the above approach were replaced by separate builds which were percieved to be "cleaner". If you don't want to go that route, I'd sugest to go your first approach: I don't see a huge problem in keeping bootstrap compilers around, as long as their binariy names are properly and consistently prefixed. Either way, if you have further questions, feel free to open an issue tracker entry on that. Maybe you'll get more/better responses there: https://github.com/mxe/mxe/issues Regards, Volker Gregorio Litenstein schrieb: > I am asking this again since it got lost/ignored last time. > > Is it possible to create a package so that it downloads more than one > source package? > > The reason I'm asking is because I'm trying to port rust; the problem is > rust requires a bootstrap compiler that cannot be built from scratch, we > _need_ to either download it or provide it somehow. One possible solution > of course would be to have a package for each bootstrap component (there's > 3; rustc, rust-std and cargo). That would probably work but would mean > keeping bootstrap compilers around on the system after building the real > compiler so it's far from ideal. > > Another solution maybe would be to make a single package containing both > the source and the bootstrap binaries and host it somewhere; this is also > not ideal because there would have to be one for each different OS > supported by MXE. > > The ideal solution of course, would be to be able to have more than one > source file for a package. Then I'd be able to pull all required > components, check their checksum and get rid of them once they're no longer > needed. > > Is that last option possible? > > And, in case it's not; is it possible to get around the no-download thing > (I know this is very discouraged but if there's no other solution...) I > promise to be good and verify checksums for anything I download! > > -- > Gregorio Litenstein Goldzweig > [image: glit_ind.png] > Médico Cirujano > > > > - Fono: +56 9 96343643 <+56%209%2096343643> > - E-Mail: g.litenstein@gmail.com -- Volker Diels-Grabsch ----<<<((()))>>>---- From MAILER-DAEMON Sat Aug 17 06:17:45 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1hyvmL-0000JI-89 for mharc-mingw-cross-env-list@gnu.org; Sat, 17 Aug 2019 06:17:45 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57826) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hyvmH-0000J9-T3 for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 06:17:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hyvmF-00035d-PZ for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 06:17:41 -0400 Received: from dd21736.kasserver.com ([85.13.141.168]:50490) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hyvmD-00031f-W6 for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 06:17:39 -0400 Received: from [10.80.131.186] (unknown [195.30.193.36]) by dd21736.kasserver.com (Postfix) with ESMTPSA id 7DD312F4088B for ; Sat, 17 Aug 2019 12:10:18 +0200 (CEST) To: mingw-cross-env-list@nongnu.org From: Thomas Mayer Openpgp: preference=signencrypt Autocrypt: addr=thomas@residuum.org; prefer-encrypt=mutual; keydata= mQENBEtnSKMBCAD3PmU1ZGS0g/7ATO5HUF5v4Wi+x3YoQW+j7UFckowIN9ParE7eNjhc0IIM Oj1Z5s/NoHXRSpMYiEh9hGLJnY1nM/huwc1/OOe4d33tXKs7x2WC4wTUlUFU5etyu1KX0N4b 3HJjM9xd1rhRqDPexY6TO+4KUZvc0dE4DhSbBYRpIt8lakKQhmh0225gm+BOLko+WTxe5ueR I3tyKalmj+q0moCZqwGOOoGRikuBRqS+Md9NhKvgpQF0iG5O83MWENlBeZax59R4udt6tKps j9p0/JK4pCXJLosmw3QF7txhCrK9fxB9BSDAbRWeM2FV+TxPftRJ6eMKjZjT2o/ADkrjABEB AAG0IlRob21hcyBNYXllciA8dGhvbWFzQHJlc2lkdXVtLm9yZz6JAVUEEwEKAD8CGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheAFiEEZALp8DNWzXpWqmKZygwha+WknJkFAl03RTIFCRWS Y44ACgkQygwha+WknJmUyAgAx8ybwWuuI76olvMklHd+flUUnuVxJW3+7vpuJ2bNJT4fudPd KpgbXxISm+rr71CS9KWWMz/0wpW2HfPG1Cyh4iclJ4qODBMj4yNx3ul9zZg2hTG27sCVLQuv 9rPagE+BZycr61pRo78sT8WmwFNidpTFFWcTMSow7JRn09RrtcwJcb9xLfA/mEUDxOKSuCS2 S7MhJEcnYDbnSY1ZJaEOmxP+1snLq5LkTm57+f0eGPocvtQmSPatxbwRwpSteV4F1sEYNWJz HQ73fr5y3g5g39YVGHXfkJYEPpCDg3LhoPgx5asQPyzhwek7hFjs5JcLtwTEh0LP2zB22qFm gUff4bkBDQRLZ0ijAQgA78R68OoQvYXRvxgtySrZAeu+Ov13HztPWbMrYSRTHpYuXWPiDayq B7vtmKzygMdiI3/ygBB96OoNNuH8TVkWoNBGpJWHcQpPU5fBvbC07bWkEqM8xY0eo4lmCaW1 JobDiH/gaKYZVwOx5JT3uARizxI14pztq7H6okpShHZhU0tHg79WRe503NnMagyqUfjMPGGe bSq1ahwqHVeeiCGvQ17Ak1t9bju61vzK0kAzyUmcvleShOa5ruUlGFo8++ORut5OUdFa9Bab RhpvQVZ2MFjAjctEVI1kZppaxrroJ9xqOBxxsas01jy6ZfWz9jO5RanKK8dTxeX5keJ60RHi qQARAQABiQE8BBgBCgAmAhsMFiEEZALp8DNWzXpWqmKZygwha+WknJkFAl03RTIFCRWSY48A CgkQygwha+WknJmkYggA5ilGs60OcIXF0krzN2eC5me1gmU0BGFGIRYC1hsyvvCal24DcRae kpYr4Bb1bqRVlWM8VqWy67F4Wl7c835Xe+spVSLHdq8p8PTsinT7tdLJ3YMTVOw9HVPQswpS jmn46ZYrz4JMO8SWeKlfgqqS1FodLml02EPqriV0oY8PSyW1q4ABXeZv8foInBp6R75M6cnu 8/UE/kDWZftDDmuW0x3O1hXLyw6FIyZRXrWpki/Be1ia4Sny46VLJSA59UrSSW5kQphXo41H XBp8WRaQMV98nM6NErAnn3fYDK5kN/GG/fqqMWRJMDQhkGB41gSlWU081Td4GMMykn9Orz7M Jg== Message-ID: Date: Sat, 17 Aug 2019 12:10:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 85.13.141.168 Subject: [Mingw-cross-env-list] Usage of Debian packages X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Aug 2019 10:17:43 -0000 Hi, I tried to use the apt packages from pkg.mxe.cc. I have added the following line to my sources: deb http://pkg.mxe.cc/repos/apt bionic main Unfortunately, neither adding [ trusted=3Dtrue ] or calling apt-get with --allow-unauthenticated and/or --allow-insecure-repositories and/or -o Acquire::AllowInsecureRepositories=3Dtrue made it possible to apt-get update the list of packages. The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C6BF758A33A3A276 W: GPG error: http://pkg.mxe.cc/repos/apt bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C6BF758A33A3A276 E: The repository 'http://pkg.mxe.cc/repos/apt bionic InRelease' is not signed. There is a key at https://pkg.mxe.cc/repos/apt/client-conf/mxeapt.gpg, but apt-key cannot import it: wget -qO - https://pkg.mxe.cc/repos/apt/client-conf/mxeapt.gpg\ | sudo apt-key add - How can I import the key or add the repository without authentication? Thanks, Thomas --=20 "It seems to me, Golan, that the advance of civilization is nothing but an exercise in the limiting of privacy." (Janov Pelorat in: Isaac Asimov - Foundation's Edge) http://www.residuum.org/ From MAILER-DAEMON Sat Aug 17 11:07:34 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1hz0Io-0006Ai-5N for mharc-mingw-cross-env-list@gnu.org; Sat, 17 Aug 2019 11:07:34 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57439) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hz0Il-0006AS-S0 for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 11:07:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hz0Ik-0005mS-Ju for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 11:07:31 -0400 Received: from mail-wr1-x42c.google.com ([2a00:1450:4864:20::42c]:33644) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hz0Ik-0005lQ-Dw for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 11:07:30 -0400 Received: by mail-wr1-x42c.google.com with SMTP id u16so4351317wrr.0 for ; Sat, 17 Aug 2019 08:07:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:openpgp:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dY3zldbmQss2zvLdG4sYpomqgSRLDkPNociGt95H0Fo=; b=LOrMaeYuvYwkik6CIOKWxD4foCbVfwIXzA8E8m34dPyiOR3H98Vrss9qmdnnVljAPY FnK5FdBPrm4ox5uaewt56NoLOrGuDHUCiT1ss37AeGEj3pv45UKnyV8GVyXFYhed6ly3 C7ao3aY/ZEn4qEBd61BbapQtrA7RKWoERrtVp7x1IcgLvPjrtPDa3mMaTmgTEXNIgnUC V08cmdLzxhcPaEVlPsIzUPWdweDLfYQk7Pr+saRrN6LRi16QqHBzrW7BlI8W8CTDu9yb OgWLdTWJwVAI+PdRCbdfYf5Wtrdrd5R0zDJZJ94mh5lLe/5zfck7znfUde7SrWI3lRA1 RIWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dY3zldbmQss2zvLdG4sYpomqgSRLDkPNociGt95H0Fo=; b=d3/zC+CsThv2oniCNVmPbBJ/jQYhwZYCGCYooxBaOm3ci7EvM5dTfxF6Vgh6EjGQDL x3ffnhQafpiOtrTTeZGN5QY8ag5jH2U8u2P2E+xDOMTqJi35noC8p1l3l/hgJ3pTxXfP 7tv3+8p6MMIYpdGhSBUVl25BBlNxDoYGHSr2jon35U8ZvJrA28obnNwnpuSgTGUabnLH 8EMgASUos+9LwHx7cX6gUXgb85BNY6i/N1hluZzLw/4KWFHAKI2TrTmMY9lm3qw36YuW J08L6h6qLtVt6xO1JD14GkJebvU0QL3jV6QoDdxgnB3vMunMssuG5/Hq02jzOvmMpdpZ WyhQ== X-Gm-Message-State: APjAAAXje73jD/QLW4+5erf/zoW6xsQAb7V4jCmlBGSeNSY9sThaNf61 nNOyw/6BWLcA1he9mXEmi7X5wAxDJtU= X-Google-Smtp-Source: APXvYqxVaNb4eMi31W6ffaiP0VgbJpDFxxN7oyXFWyvMkT9o/jjSHRm4aY5y5+kyDwX9GKi8yfP5XA== X-Received: by 2002:adf:f991:: with SMTP id f17mr16121179wrr.233.1566054448195; Sat, 17 Aug 2019 08:07:28 -0700 (PDT) Received: from ?IPv6:2003:f1:6718:ca74:125:38f2:d09f:2df7? (p2003000611D5E574012538F2D09F2DF7.dip0.t-ipconnect.de. [2003:6:11d5:e574:125:38f2:d09f:2df7]) by smtp.gmail.com with ESMTPSA id q124sm8525579wma.33.2019.08.17.08.07.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Aug 2019 08:07:27 -0700 (PDT) To: mingw-cross-env-list@nongnu.org References: From: Lothar Serra Mari Openpgp: preference=signencrypt Message-ID: <3471cf74-70cc-cdf7-0ad7-3c9099efcae7@gmail.com> Date: Sat, 17 Aug 2019 17:07:26 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::42c Subject: Re: [Mingw-cross-env-list] Usage of Debian packages X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Aug 2019 15:07:33 -0000 Hi Thomas, > There is a key at https://pkg.mxe.cc/repos/apt/client-conf/mxeapt.gpg, > but apt-key cannot import it: > > wget -qO - https://pkg.mxe.cc/repos/apt/client-conf/mxeapt.gpg\ > | sudo apt-key add - > > How can I import the key or add the repository without authentication? which error message do you get when trying to import the key? I just tried on Ubuntu 18.04 WSL (yeah, not exactly accurate...), and it just adds the key with a simple "OK" message. However, it seems that the key in mxeapt.gpg is either outdated or somehow broken since "apt update" failed. This solved it for me: > sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C6BF758A33A3A276 With best regards Lothar From MAILER-DAEMON Sat Aug 17 20:16:15 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1hz8rm-0000rS-VJ for mharc-mingw-cross-env-list@gnu.org; Sat, 17 Aug 2019 20:16:14 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57677) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hz8rk-0000rM-NV for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 20:16:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hz8rj-0001qL-9d for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 20:16:12 -0400 Received: from dd21736.kasserver.com ([85.13.141.168]:58112) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hz8rj-0001ox-2c for mingw-cross-env-list@nongnu.org; Sat, 17 Aug 2019 20:16:11 -0400 Received: from [192.168.178.53] (aftr-62-216-209-12.dynamic.mnet-online.de [62.216.209.12]) by dd21736.kasserver.com (Postfix) with ESMTPSA id 047782F4250E for ; Sun, 18 Aug 2019 02:16:06 +0200 (CEST) To: mingw-cross-env-list@nongnu.org References: <3471cf74-70cc-cdf7-0ad7-3c9099efcae7@gmail.com> From: Thomas Mayer Openpgp: preference=signencrypt Message-ID: <296859db-c999-6650-54e6-9643d5fc924b@residuum.org> Date: Sun, 18 Aug 2019 02:16:05 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.22) Gecko/20090706 Lightning/0.9 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666 MIME-Version: 1.0 In-Reply-To: <3471cf74-70cc-cdf7-0ad7-3c9099efcae7@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 85.13.141.168 Subject: Re: [Mingw-cross-env-list] Usage of Debian packages X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Aug 2019 00:16:14 -0000 Hi Lothar, On 17.08.19 17:07, Lothar Serra Mari wrote: > Hi Thomas, > >> There is a key at https://pkg.mxe.cc/repos/apt/client-conf/mxeapt.gpg, >> but apt-key cannot import it: >> >> wget -qO - https://pkg.mxe.cc/repos/apt/client-conf/mxeapt.gpg\ >> | sudo apt-key add - >> >> How can I import the key or add the repository without authentication? > > which error message do you get when trying to import the key? I just > tried on Ubuntu 18.04 WSL (yeah, not exactly accurate...), and it just > adds the key with a simple "OK" message. I was unclear, because apt-key could import the key, but it was not C6BF758A33A3A276. > > However, it seems that the key in mxeapt.gpg is either outdated or > somehow broken since "apt update" failed. > > This solved it for me: > >> sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys > C6BF758A33A3A276 Yes, that was it. I was using a wrong key server (keys.gnupg.net) before trying the rest. Thanks, Thomas -- "Theoretically, [the amount of money in circulation] is watched carefully by clever, serious economists. In practice, all the world's money is one big swirling, whirling pool." (Cory Doctorow - For The Win) http://www.residuum.org/ From MAILER-DAEMON Fri Aug 23 13:14:03 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i1D8V-0003Wi-52 for mharc-mingw-cross-env-list@gnu.org; Fri, 23 Aug 2019 13:14:03 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:56278) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i1D8S-0003WY-RI for Mingw-cross-env-list@nongnu.org; Fri, 23 Aug 2019 13:14:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i1D8R-0007HP-G4 for Mingw-cross-env-list@nongnu.org; Fri, 23 Aug 2019 13:14:00 -0400 Received: from mail-yw1-xc42.google.com ([2607:f8b0:4864:20::c42]:36688) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i1D8R-0007Fr-8H for Mingw-cross-env-list@nongnu.org; Fri, 23 Aug 2019 13:13:59 -0400 Received: by mail-yw1-xc42.google.com with SMTP id m11so4109707ywh.3 for ; Fri, 23 Aug 2019 10:13:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=W5yR522PYhhsPyy4uqEL/DBR/VKLYmvYsBpo0U/TMJY=; b=XKixxjpCTO4I9LyagOt9kxqtQ508hujueL7X5WH7UaIjl6jLzFyqE8k9+jGh+SRvjZ 5izgL0hcfFrmrHjDbtJ5frxjCSRJAGbEHAobmJO9LhzVSIat7f3TBLryt8AO6XHYlmGz Q5XqoEePbyjJh81mYfk1fddYQg1GIOcUHFOF5xdf+iaUbdPkJkib+0OnJuz3dZlXtIlA Poq9jct6mbxcNq59XNsMiuWmAltBj5iWrSsMcAPMJdGjW6WRhp/BHb5JDatFse3mn1SI gW0Qz3FQwczAXueKdUpkUEpHRYg306FrAiYS/yve3Fdxn0wI+5A/TKilkNlxPqhsWqaS 1IAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=W5yR522PYhhsPyy4uqEL/DBR/VKLYmvYsBpo0U/TMJY=; b=qh/yRAZKAr91eXhCBqc/kVPFA7+SRw6IxyZ77rIvVt/1lWi+uj5FcyAFkTrUWNUX+R SkyUg43mDC79f1E+YfpbNU9T1Lh95AhYN8P6Sea77w8NtwVXrUaXQGmlv4jZ+O0IHWVi bV2Q4BuDGvEc/GgvMSgyQQKwiV9xtlgS0lq7rK2mHeNtOVBC8MWGBIVKZrqcCnrA3n0Y r9a65D09hxg4A0dfe5edSz7Mg3pGK16KCGW74bIeeAkel0t0LYdy2RoQ1B+dzJetccHK E8VusrcuQZPN9jwGv1yxfw6vPKN+GdaF9bU/uCxtGrY1KVAtXkcRrW5Nq09v33QU6sTb kwjA== X-Gm-Message-State: APjAAAW/4EwhIfYNf/fPlP/OBdZpq1bT9LdEhejUrAPXZkxlDz9coDaB 8cSf/U/7RjmMuSHByn8Y4UTQqmFOqjuRA81kw854XGBU X-Google-Smtp-Source: APXvYqxpqH2iiYJUxZv2B38mx9+e5vj/YVE9UgJZia4obZFch5Lj++XDNuSMlOPFsjY7odKXhPot6TxotFFDLUgnWMY= X-Received: by 2002:a81:4414:: with SMTP id r20mr4175720ywa.288.1566580437536; Fri, 23 Aug 2019 10:13:57 -0700 (PDT) MIME-Version: 1.0 From: Paul Buxton Date: Fri, 23 Aug 2019 18:13:46 +0100 Message-ID: To: Mingw-cross-env-list@nongnu.org Content-Type: multipart/alternative; boundary="0000000000007dd33e0590cbee4c" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::c42 Subject: [Mingw-cross-env-list] Am I doing something wrong? X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Aug 2019 17:14:02 -0000 --0000000000007dd33e0590cbee4c Content-Type: text/plain; charset="UTF-8" So I am trying to use MXE to build subsurface using their instructions @ https://github.com/Subsurface-divelog/subsurface/blob/master/packaging/windows/mxe-based-build.sh during the MXE make process I get a failure building qtbase. Log here https://gist.github.com/buxtonpaul/50f1bab873591c31685b36a3221d0a7c This is building on a Ubuntu 16 system. What is interesting is that I got what looks like exactly the same problem attempting to build on WSL.... I am wondering if I have misunderstood something. Should I have already installed the packages locally that I am trying to setup via MXE? My impression is that the MXE make process fetches the packages it needs, am I wrong? Thanks, Paul --0000000000007dd33e0590cbee4c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
So I am trying to use MXE to build subsurface using t= heir instructions @ https://github.com/S= ubsurface-divelog/subsurface/blob/master/packaging/windows/mxe-based-build.= sh

during the MXE make process I get a failure= building qtbase.

This is bui= lding on=C2=A0 a Ubuntu 16 system.
What is interesting is that I = got what looks like exactly the same problem attempting to build on WSL....=
I am wondering if I have misunderstood something. Should I have = already installed the packages locally that I am trying to setup via MXE? M= y impression is that the MXE make process fetches the packages it needs, am= I wrong?

Thanks,
Paul
--0000000000007dd33e0590cbee4c-- From MAILER-DAEMON Sat Aug 24 20:53:23 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i1gmZ-0000KT-FJ for mharc-mingw-cross-env-list@gnu.org; Sat, 24 Aug 2019 20:53:23 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:57086) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i1gmW-0000Hr-NH for Mingw-cross-env-list@nongnu.org; Sat, 24 Aug 2019 20:53:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i1gmV-0002vh-GH for Mingw-cross-env-list@nongnu.org; Sat, 24 Aug 2019 20:53:20 -0400 Received: from mail6.webfaction.com ([31.170.123.134]:52832 helo=smtp.webfaction.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i1gmV-0002tt-B8 for Mingw-cross-env-list@nongnu.org; Sat, 24 Aug 2019 20:53:19 -0400 Received: from 192-168-1-111.tpgi.com.au (194-193-174-42.tpgi.com.au [194.193.174.42]) by smtp.webfaction.com (Postfix) with ESMTPSA id C562C6003D993; Sun, 25 Aug 2019 00:52:37 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Tony Theodore In-Reply-To: Date: Sun, 25 Aug 2019 10:53:11 +1000 Cc: Mingw-cross-env-list@nongnu.org Content-Transfer-Encoding: quoted-printable Message-Id: <46BA726C-22FF-497B-90C2-4367095B7581@logyst.com> References: To: Paul Buxton X-Mailer: Apple Mail (2.3445.104.11) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 31.170.123.134 Subject: Re: [Mingw-cross-env-list] Am I doing something wrong? X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 00:53:21 -0000 > On 24 Aug 2019, at 03:13, Paul Buxton via Mingw-cross-env-list = wrote: >=20 > So I am trying to use MXE to build subsurface using their instructions = @ = https://github.com/Subsurface-divelog/subsurface/blob/master/packaging/win= dows/mxe-based-build.sh >=20 > during the MXE make process I get a failure building qtbase. > Log here = https://gist.github.com/buxtonpaul/50f1bab873591c31685b36a3221d0a7c It seems to be having trouble with `-debug-and-release`, this was tricky = to get working and may have changed subtly in recent updates. In the meantime, try = removing/commenting the line: qtbase_CONFIGURE_OPTS=3D-debug-and-release in `settings.mk`. Cheers, Tony From MAILER-DAEMON Sun Aug 25 05:37:11 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i1oxT-0006a9-SJ for mharc-mingw-cross-env-list@gnu.org; Sun, 25 Aug 2019 05:37:11 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45300) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i1oxR-0006a3-Rs for Mingw-cross-env-list@nongnu.org; Sun, 25 Aug 2019 05:37:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i1oxQ-0005C5-Jd for Mingw-cross-env-list@nongnu.org; Sun, 25 Aug 2019 05:37:09 -0400 Received: from mail-yw1-xc2f.google.com ([2607:f8b0:4864:20::c2f]:39710) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i1oxQ-0005BI-F1 for Mingw-cross-env-list@nongnu.org; Sun, 25 Aug 2019 05:37:08 -0400 Received: by mail-yw1-xc2f.google.com with SMTP id x74so5713074ywx.6 for ; Sun, 25 Aug 2019 02:37:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HyVlimW3ZW5m5l7KRL/tBBV6ChaSvndMKcoxducpagI=; b=eZl3VEmmIqpWK1OhmXG6m06NOD6ZN20opnpdDN7gDsMadxWM0jo4XIqOUJ2cYczegc Yz6kBWCwISYyB9koiOHsdqcZzFk1k6VKAGSnvm8iOOsZvcMK45XxQpp6vQJci0t+HOj1 8ddUqyohixKruA5FAX1V9Z4OQ4mnpRkdu98lEKVS8fA7P2wujfxlX4nGFujl8qZiHdtW wqanZzLcg8Mx2XEUDZyyjqzcsiUv+sR4nA/B+Z8ET/cckENmYwlImEMH8LtSdO/4hRFQ v+NAgIpDpUng/CDPSjVzvAjuK1HYHVpGVS8ySBDejdqgKxybXEYIzLB4yKVc+Yl1Jsrd Vhxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HyVlimW3ZW5m5l7KRL/tBBV6ChaSvndMKcoxducpagI=; b=JXqMWSjVfStd7P/JlJys2Nxm55E0gEb2myNWCNcyShpXvVIAeOYJqMaJTqa41x1unq TfizAIH0JyKeA1UXgajXE2/DujAh+B/paHbNaPCI6tZrwhPxr/SqlNVyX6OEe1l5tHyB YDU6AHdJSaxS4k4uQvojnwypvb27Ktcj8mdwbFkRF8+IX0W+eFbOu/q7re9yLQAp8YZf pKwa3nzcyq3bBbUYif4dO6ZoeGKq9ZDPVDI6jyDkMH+hwnD79dTTWfKumQ3N84tn0KeL qG5GD2itKPLv8UV/P4rTEK8yb0Kes/fwuEf9F3PWoXYNNEm0nyqxWzZoz/Lhr/aegOxI /pGQ== X-Gm-Message-State: APjAAAUX6KCwvwttioos0r4CutV9a+wQPyLAS4a0mCZ6NjMX8qcoCRn1 8v6VeD5oM8IPPeJzQ8vaxQrLZPnXriz0k7opQFTlLg== X-Google-Smtp-Source: APXvYqxvuBKbSKGnRXy8izIj4xJqXOkMfLusey23ggmscNnL9240sDPDoto8GVqjaApbnzIIHqK/XqJs6gnChGdyr2Q= X-Received: by 2002:a81:120e:: with SMTP id 14mr8897935yws.407.1566725826541; Sun, 25 Aug 2019 02:37:06 -0700 (PDT) MIME-Version: 1.0 References: <46BA726C-22FF-497B-90C2-4367095B7581@logyst.com> In-Reply-To: <46BA726C-22FF-497B-90C2-4367095B7581@logyst.com> From: Paul Buxton Date: Sun, 25 Aug 2019 10:36:59 +0100 Message-ID: To: Tony Theodore Cc: Mingw-cross-env-list@nongnu.org Content-Type: multipart/alternative; boundary="00000000000059fd580590edc86a" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::c2f Subject: Re: [Mingw-cross-env-list] Am I doing something wrong? X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 09:37:11 -0000 --00000000000059fd580590edc86a Content-Type: text/plain; charset="UTF-8" Hi, Removing that line from the settings does work. Thanks. On Sun, 25 Aug 2019, 01:53 Tony Theodore, wrote: > > > > On 24 Aug 2019, at 03:13, Paul Buxton via Mingw-cross-env-list < > mingw-cross-env-list@nongnu.org> wrote: > > > > So I am trying to use MXE to build subsurface using their instructions @ > https://github.com/Subsurface-divelog/subsurface/blob/master/packaging/windows/mxe-based-build.sh > > > > during the MXE make process I get a failure building qtbase. > > Log here > https://gist.github.com/buxtonpaul/50f1bab873591c31685b36a3221d0a7c > > It seems to be having trouble with `-debug-and-release`, this was tricky > to get working and may have > changed subtly in recent updates. In the meantime, try > removing/commenting the line: > > qtbase_CONFIGURE_OPTS=-debug-and-release > > in `settings.mk`. > > Cheers, > > Tony > > --00000000000059fd580590edc86a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
Removing that line from the settings= does work.
Thanks.

On Sun, 25 Aug 2019, 01:53 = Tony Theodore, <tonyt@logyst.com= > wrote:


> On 24 Aug 2019, at 03:13, Paul Buxton via Mingw-cross-env-list <mingw-cross-env-list@nongnu.org> wrote:
>
> So I am trying to use MXE to build subsurface using their instructions= @ https://github.com/Subsurface-divelog/subsurface/blob/master/pa= ckaging/windows/mxe-based-build.sh
>
> during the MXE make process I get a failure building qtbase.
> Log here https://= gist.github.com/buxtonpaul/50f1bab873591c31685b36a3221d0a7c

It seems to be having trouble with `-debug-and-release`, this was tricky to= get working and may have
changed subtly in recent updates. In the=C2=A0 meantime, try removing/comme= nting the line:

qtbase_CONFIGURE_OPTS=3D-debug-and-release

in `settings.mk`.

Cheers,

Tony

--00000000000059fd580590edc86a-- From MAILER-DAEMON Sun Aug 25 08:40:16 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i1roe-0003W4-IQ for mharc-mingw-cross-env-list@gnu.org; Sun, 25 Aug 2019 08:40:16 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:47969) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i1pLV-0003uf-GE for Mingw-cross-env-list@nongnu.org; Sun, 25 Aug 2019 06:02:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i1pLS-0004Ds-8n for Mingw-cross-env-list@nongnu.org; Sun, 25 Aug 2019 06:02:00 -0400 Received: from mail-io1-xd2d.google.com ([2607:f8b0:4864:20::d2d]:47089) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i1pLR-0004DS-Rw for Mingw-cross-env-list@nongnu.org; Sun, 25 Aug 2019 06:01:58 -0400 Received: by mail-io1-xd2d.google.com with SMTP id x4so30223862iog.13 for ; Sun, 25 Aug 2019 03:01:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=mszJRCUCeJjg9h5S4mdzgN5rmihUlciYiS71esJb5DU=; b=Wf+AqCf0SDpQYPaYBduaxuGOMsSPYTwtnPWAHT2ZYBkiLK70qs99eVDFfJmHMLWUOh n80GU06UG/wQKmzSzUiBHRHmiTOWvpPXDm8Wf5rtMF3I50Dtr1QVxMnPLBpiDRyya0jk 4y6zes/nBXpOCBcNFse/J84NaXKWAYf3oUQ3BoJCVK+K5MFEC2XhBMJd/SoL9ihGgD3g W9H+v5fe3iK6f3OpfP7j94wMz9xNIzEO8ErB06G9w3Z/zJltiLK5TSgNIBejv4X3dHAn xdKHZ2YoTZaVGfx2ZRJPjrogL80T58FKgJW1xaQOqj3MMvZSl4M+Jkomius1bn71jDog wfXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=mszJRCUCeJjg9h5S4mdzgN5rmihUlciYiS71esJb5DU=; b=kfTPJDGai0mNolnJXgXNxOR9QorHa1/zwsRidJXLfsR84rGYBNwumdLbxzxT50CrAz /TD1drYH+t+nZmODhtOikLb66VHnq68IEWxMlcZD4r2pVHwCv/82K9lTDGTnEAeZypVl URaFxxyaV5J4DkCaEdQFuZz31jCTXG37mBYnowEPhspR1aQ8/zQ3UbpN3q10thGskJA+ sJZ7LG1vQFtB5OXZ29TP2AjyNwK2pzUdr1llvyEjqz1KkJ6WLiH4tdzOxsRaqr+4Q/3e 3nQJongde6HCksa8Ng8si2qkVO6DSQHg4oiuuagbnBoosLhbbk0zOj98XVy0JloqN4bD 1nUA== X-Gm-Message-State: APjAAAV5WCBcdPlpp8mVibr2q7O4WXvEWj1nT6xvBivlY2McQTnjms3r 36XmWz2q9iLtioGdmdabyoIUPVYQ6kcb/+RFrv8= X-Google-Smtp-Source: APXvYqzrG51unynHDV3ktlEAv8G0iYIImUJoVvL05vliq7AkuaIs11sLV5ZNV8/W5kuVTwR7oYfmwzTJ0FHgLsycIiU= X-Received: by 2002:a02:a503:: with SMTP id e3mr13013181jam.134.1566727315811; Sun, 25 Aug 2019 03:01:55 -0700 (PDT) MIME-Version: 1.0 References: <46BA726C-22FF-497B-90C2-4367095B7581@logyst.com> In-Reply-To: Reply-To: k.s.matheussen@notam02.no From: Kjetil Matheussen Date: Sun, 25 Aug 2019 12:01:44 +0200 Message-ID: To: Paul Buxton Cc: Tony Theodore , Mingw-cross-env-list@nongnu.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::d2d X-Mailman-Approved-At: Sun, 25 Aug 2019 08:40:15 -0400 Subject: Re: [Mingw-cross-env-list] Am I doing something wrong? X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 10:02:05 -0000 On Sun, Aug 25, 2019 at 11:37 AM Paul Buxton via Mingw-cross-env-list wrote: > > Hi, > Removing that line from the settings does work. > Thanks. > The error you have is a missing alloca.h. I think I may have seen that error, but I don't remember the solution. Maybe it rings a bell for someone else on this list... Checking for alloca() in alloca.h... + cd /home/paul/src/mxe/tmp-qtbase-i686-w64-mingw32.shared.posix.dw2/qtbase= -everywhere-src-5.13.0/config.tests/alloca_h && /home/paul/src/mxe/tmp-qtbase-i686-w64-mingw32.shared.posix.dw2/qtbase-e= verywhere-src-5.13.0/bin/qmake "CONFIG -=3D qt debug_and_release app_bundle lib_bundle" "CONFIG +=3D shared warn_off console single_arch" 'DEFINES +=3D Q_USE_SYBASE' -early "CONFIG +=3D cross_compile" /home/paul/src/mxe/tmp-qtbase-i686-w64-mingw32.shared.posix.dw2/qtbase-ever= ywhere-src-5.13.0/config.tests/alloca_h + cd /home/paul/src/mxe/tmp-qtbase-i686-w64-mingw32.shared.posix.dw2/qtbase= -everywhere-src-5.13.0/config.tests/alloca_h && MAKEFLAGS=3D /usr/bin/make > make[2]: Entering directory '/home/paul/src/mxe/tmp-qtbase-i686-w64-mingw= 32.shared.posix.dw2/qtbase-everywhere-src-5.13.0/config.tests/alloca_h' > i686-w64-mingw32.shared.posix.dw2-g++ -c -pipe -fno-keep-inline-dllexport= -O2 -std=3Dgnu++11 -w -fexceptions -mthreads -DUNICODE -D_UNICODE -DWIN32 = -DMINGW_HAS_SECURE_API=3D1 -DQ_USE_SYBASE -I. -I/home/paul/src/mxe/tmp-qtba= se-i686-w64-mingw32.shared.posix.dw2/qtbase-everywhere-src-5.13.0/mkspecs/w= in32-g++ -o main.o main.cpp > main.cpp:2:20: fatal error: alloca.h: No such file or directory > compilation terminated. From MAILER-DAEMON Mon Aug 26 20:11:34 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i2P5C-0004HN-JW for mharc-mingw-cross-env-list@gnu.org; Mon, 26 Aug 2019 20:11:34 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:34127) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i2P59-0004Ae-24 for mingw-cross-env-list@nongnu.org; Mon, 26 Aug 2019 20:11:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i2P58-00019j-35 for mingw-cross-env-list@nongnu.org; Mon, 26 Aug 2019 20:11:30 -0400 Received: from sender-of-o52.zoho.com ([135.84.80.217]:21411) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i2P57-00018j-QB for mingw-cross-env-list@nongnu.org; Mon, 26 Aug 2019 20:11:30 -0400 ARC-Seal: i=1; a=rsa-sha256; t=1566864682; cv=none; d=zoho.com; s=zohoarc; b=a/e8asqz4wI9s3GpXinekSNTtOrzryCcwzNWo/KGJRdu+wVKNr2fpy3rwvybj7NJNfKcu1ZGoIhRNeNiaeC3JPw4urmYPur3ld5E7bzjBSBizBZlSEb5nFaKD8i5Zdoo0j1nSAOUIeEhnkdSJb4Jfk2RPPHBqozbPS3PnNIpi3Y= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zoho.com; s=zohoarc; t=1566864682; h=Content-Type:Date:From:MIME-Version:Message-ID:Subject:To:ARC-Authentication-Results; bh=1ukadUJDSi9nCcT9N57VM+Evfw45TpH7x09BlghS1mQ=; b=kZOmVJms7y/GJmPH+V9VfXrPzmcoxpyozd3/ApTQASf4/xpDCKm9l1kJpzmSk49sU53BIY/OJ//scnwXphSjXKmt7NllyL1CRyw8h4O3p3sJ5uY5up0U/n+bISFEyD+rE7R7KDIOmVHrBhEVxfudX6F4SpW+9wKagTsbCKuglXU= ARC-Authentication-Results: i=1; mx.zoho.com; dkim=pass header.i=vba-m.com; spf=pass smtp.mailfrom=zachbacon@vba-m.com; dmarc=pass header.from= header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1566864682; s=zoho; d=vba-m.com; i=zachbacon@vba-m.com; h=Date:From:To:Message-Id:In-Reply-To:Subject:MIME-Version:Content-Type; l=1006; bh=1ukadUJDSi9nCcT9N57VM+Evfw45TpH7x09BlghS1mQ=; b=kBcHU3Ii5Oomaqg2VFxrPb3traMq93+SXlLRSp5v5XK5D3V2gvuWJLX8/NYg39Xm ml2NoMsRhnTBc8jGvZDcVn3IUEvIMC+Zd3slmTL9V4ip33+qZi4XMbxYe3ZEnSizaX3 8seoAogAp5zuEmjTeBgPxeGH/YnZHYoQl99tOrd4= Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1566864681078895.2261936362165; Mon, 26 Aug 2019 17:11:21 -0700 (PDT) Date: Mon, 26 Aug 2019 17:11:21 -0700 From: Zach Bacon To: "mingw-cross-env-list" Message-Id: <16cd069a874.bfec7500702998.5020263846623538963@vba-m.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2259070_1634676240.1566864681076" X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 135.84.80.217 Subject: [Mingw-cross-env-list] building a package that requires meson X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Aug 2019 00:11:33 -0000 ------=_Part_2259070_1634676240.1566864681076 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit So I've been looking at updating the gtk stack and the patches therein and newer versions of glib etc moved to meson. Is there a case where there's a project makefile includes support for building with meson yet? ------=_Part_2259070_1634676240.1566864681076 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 7bit
So I've been looking at updating the gtk stack and the patches therein and newer versions of glib etc moved to meson. Is there a case where there's a project makefile includes support for building with meson yet?


------=_Part_2259070_1634676240.1566864681076-- From MAILER-DAEMON Wed Aug 28 07:27:38 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i2w70-00075G-L4 for mharc-mingw-cross-env-list@gnu.org; Wed, 28 Aug 2019 07:27:38 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:38856) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i2w6y-000758-QS for mingw-cross-env-list@nongnu.org; Wed, 28 Aug 2019 07:27:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i2w6x-0008ER-DU for mingw-cross-env-list@nongnu.org; Wed, 28 Aug 2019 07:27:36 -0400 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]:33097) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i2w6w-0008D9-VE for mingw-cross-env-list@nongnu.org; Wed, 28 Aug 2019 07:27:35 -0400 Received: by mail-wm1-x329.google.com with SMTP id r17so1533326wme.0 for ; Wed, 28 Aug 2019 04:27:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:date:message-id:subject:to; bh=gzyf3NZogzwIcAp1h0lrO05wLJqoQ19jCDeNOZCV0Yo=; b=RyA9hd1rhVC6L3H2yXvEvTtyUklqO6vAUjHlLmB+KVTtXsUwQo/5XhZPriri5+8CkQ qUt0kDtxu4j5AxLZP0sAkmPN0q9Cf0pJhEE6fknOyPME+usvjg8fSwIq3WrRulbjtvgi jBIXfvsMlqd4WMjszODvx1xpfSqWNlNhQZf2pUem7Tj1ojmhvTZTJh5s6dsfVq3Ciqk3 WFFczNtBlKc4RYLqDryN/Z7MN09jII6jf9B0osUwzwI9Ljy9tYqaMByR9mU7N2jO3vcs vlGVUdb9ywgnWCpSpXjCXVzUq9ZTPzDGLn3/5jRWmeTs4cMKdzC3gielwdtRc5nsRqp2 jtrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=gzyf3NZogzwIcAp1h0lrO05wLJqoQ19jCDeNOZCV0Yo=; b=RTgJhfJlsNpUlV8IbM024vm9kPAdSIjmCsx8YZo8aWLI+dSFnTf6HUsWxnjINeK14c U0API1TRjWWsoxKflVmGl+MVbUVQT06gQn3hzMf/V+EugqMg/xdF94NLa82QvxVr2d7U Z/OaS97B3YqD+xHZRawNNj5WHo6q5nDfpqqUbizF2XV22ZbvG7KeoefQlHH3b+1wNBmQ pmEKUOmWIQCjZZAU+rNSARVNXr/h+BtJPPS2mQC2cCY+yFeMNO7ZxoUxGcGJOkXmuXMB Eo981KTqfGzT+hnF5duBLjKyhZUaDk23s42FIW6VXknkBjbLlcYCuK0ETrGyGkGJqkad dWqA== X-Gm-Message-State: APjAAAXLlGdSuGdquKZaHZgcmLGUnJ0prETxn0ivRacBJTAFuAtqZaVb JLtfvYY46jA4pKu7zWZcAHXvstFhoKIVv+ubFCKH4r29UGI= X-Google-Smtp-Source: APXvYqyyGVIalUZrTewonQMpJeK2ZfcSTNxP3um8O8DKhcCUFdfN4nu/JNMoB+LRbA2Bda39zO8m7b5l8bDPUQ7Z2i0= X-Received: by 2002:a1c:1b97:: with SMTP id b145mr4076144wmb.158.1566991652214; Wed, 28 Aug 2019 04:27:32 -0700 (PDT) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 28 Aug 2019 07:27:30 -0400 From: Gregorio Litenstein MIME-Version: 1.0 Date: Wed, 28 Aug 2019 07:27:30 -0400 Message-ID: To: mingw-cross-env-list@nongnu.org Content-Type: multipart/alternative; boundary="000000000000cbdebd05912bac5b" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::329 Subject: [Mingw-cross-env-list] Default GCC version X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2019 11:27:37 -0000 --000000000000cbdebd05912bac5b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable About a month ago, I naively submitted a PR to update the gcc package to 8.3.0; I was then told gcc8 actually existed and lived in plugins. Something I=E2=80=99ve been asking myself since, though (and frankly also b= efore, or I wouldn=E2=80=99t have made the PR in the first place) is=E2=80=A6 does= it actually serve any purpose to keep a three-year old compiler as the default? Wouldn=E2=80=99t it make more sense to update the default to 8.3.0 (or 9.2.= 0) and keep GCC5 as a plug-in instead? There comes a point when keeping an old compiler just becomes a drag because it makes updating other packages more difficult (it=E2=80=99s already been happening for a while probably, I=E2= =80=99d say) Is there something I=E2=80=99m missing? --=20 Gregorio Litenstein Goldzweig [image: glit_ind.png] M=C3=A9dico Cirujano - Fono: +56 9 96343643 - E-Mail: g.litenstein@gmail.com --000000000000cbdebd05912bac5b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =
Abou= t a month ago, I naively submitted a PR to update the gcc package to 8.3.0;= I was then told gcc8 actually existed and lived in plugins.

Something I=E2=80=99ve been askin= g myself since, though (and frankly also before, or I wouldn=E2=80=99t have= made the PR in the first place) is=E2=80=A6 does it actually serve any pur= pose to keep a three-year old compiler as the default? Wouldn=E2=80=99t it = make more sense to update the default to 8.3.0 (or 9.2.0) and keep GCC5 as = a plug-in instead? There comes a point when keeping an old compiler just be= comes a drag because it makes updating other packages more difficult (it=E2= =80=99s already been happening for a while probably, I=E2=80=99d say)
=

Is there something I=E2=80=99m missing?

<= /div>
=20 --=C2=A0
Gregorio Litenstein Goldzweig=C2=A0
3D"glit_ind.png"
M=C3=A9dico Cirujano
=C2=A0

=20
--000000000000cbdebd05912bac5b-- From MAILER-DAEMON Fri Aug 30 06:47:19 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i3eR5-0000PG-L8 for mharc-mingw-cross-env-list@gnu.org; Fri, 30 Aug 2019 06:47:19 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:43994) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3eR0-0000Mp-HP for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 06:47:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i3eQy-0000hp-UF for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 06:47:14 -0400 Received: from mail6.webfaction.com ([31.170.123.134]:39190 helo=smtp.webfaction.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i3eQy-0000Sw-GL for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 06:47:12 -0400 Received: from 192-168-1-111.tpgi.com.au (unknown [220.240.154.226]) by smtp.webfaction.com (Postfix) with ESMTPSA id 02A116006F712; Fri, 30 Aug 2019 10:46:29 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Tony Theodore In-Reply-To: Date: Fri, 30 Aug 2019 20:47:00 +1000 Cc: mingw-cross-env-list@nongnu.org Content-Transfer-Encoding: quoted-printable Message-Id: <57133D8B-8A78-44FC-9C76-D1DB79A17844@logyst.com> References: To: Gregorio Litenstein X-Mailer: Apple Mail (2.3445.104.11) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 31.170.123.134 Subject: Re: [Mingw-cross-env-list] Default GCC version X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 10:47:16 -0000 Hi Gregorio, > On 28 Aug 2019, at 21:27, Gregorio Litenstein = wrote: >=20 > About a month ago, I naively submitted a PR to update the gcc package = to 8.3.0; I was then told gcc8 actually existed and lived in plugins. >=20 > Something I=E2=80=99ve been asking myself since, though (and frankly = also before, or I wouldn=E2=80=99t have made the PR in the first place) = is=E2=80=A6 does it actually serve any purpose to keep a three-year old = compiler as the default? Wouldn=E2=80=99t it make more sense to update = the default to 8.3.0 (or 9.2.0) and keep GCC5 as a plug-in instead? = There comes a point when keeping an old compiler just becomes a drag = because it makes updating other packages more difficult (it=E2=80=99s = already been happening for a while probably, I=E2=80=99d say) >=20 > Is there something I=E2=80=99m missing? We=E2=80=99re missing a roadmap of planned development;) gcc version = tracking is a long-time issue trying to balance stability and new features. Currently, gcc5 is the only version that builds all mxe packages, though later versions build a very large subset. The plugin mechanism isn't ideal for several reasons: - not immediately obvious for users - not easily visible in logs etc. - doesn't provide separation of gcc deps - hard to test new versions/fallback to old - doesn't provide package makefiles with awareness of compiler =20 I plan to make compiler selection part of the target spec i.e: x86_64-w64-mingw32.static.gcc8 This has many advantages: - users who want stability can just stay on a tested version - testing new versions is simple to enable and revert - complier deps are properly isolated - package makefiles can set appropriate compiler-based flags - makes it easier to introduce clang toolchain In this scenario, mxe will no longer have a "default" compiler, just a version that currently builds all packages. There'll be no pressure to update that; we can keep it stable for (say) binary packages used in CI environments, while giving users who want to build their own more options. For that matter, we could build binaries for newer versions to push the ecosystem along. Keeping the current default at gcc5 gives us a strong forcing function to deprecate the plugin mechanism. I've had this working before (but lost all my WIP a few months ago), if it's not ready again by December - we'll update the default. Cheers, Tony From MAILER-DAEMON Fri Aug 30 09:47:22 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i3hFK-0003gY-EI for mharc-mingw-cross-env-list@gnu.org; Fri, 30 Aug 2019 09:47:22 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:47186) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3hFG-0003dp-Mh for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 09:47:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i3hFF-0005Wa-4b for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 09:47:18 -0400 Received: from mailrelay4.webfaction.com ([185.20.51.6]:51948) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i3hFE-0005LL-Nm for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 09:47:16 -0400 Received: from mailrelay3.webfaction.com (mailrelay3.webfaction.com [207.38.93.110]) by mailrelay4.webfaction.com (Postfix) with ESMTPS id 548828748F for ; Fri, 30 Aug 2019 11:21:58 +0000 (UTC) Received: from mailrelay1.webfaction.com (mailrelay1.webfaction.com [207.38.86.46]) by mailrelay3.webfaction.com (Postfix) with ESMTPS id 23731280BE4 for ; Fri, 30 Aug 2019 11:21:57 +0000 (UTC) Received: from smtp.webfaction.com (mail6.webfaction.com [31.170.123.134]) by mailrelay1.webfaction.com (Postfix) with ESMTPS id BC7BF1A04F8 for ; Fri, 30 Aug 2019 11:21:56 +0000 (UTC) Received: from 192-168-1-111.tpgi.com.au (unknown [220.240.154.226]) by smtp.webfaction.com (Postfix) with ESMTPSA id 01DF260073B81; Fri, 30 Aug 2019 11:21:15 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Tony Theodore X-Priority: Medium In-Reply-To: <16cd069a874.bfec7500702998.5020263846623538963@vba-m.com> Date: Fri, 30 Aug 2019 21:21:47 +1000 Cc: mingw-cross-env-list Content-Transfer-Encoding: quoted-printable Message-Id: References: <16cd069a874.bfec7500702998.5020263846623538963@vba-m.com> To: Zach Bacon X-Mailer: Apple Mail (2.3445.104.11) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 185.20.51.6 Subject: Re: [Mingw-cross-env-list] building a package that requires meson X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 13:47:21 -0000 > On 27 Aug 2019, at 10:11, Zach Bacon wrote: >=20 > So I've been looking at updating the gtk stack and the patches therein = and newer versions of glib etc moved to meson. Is there a case where = there's a project makefile includes support for building with meson yet? There=E2=80=99s a plugin for a meson wrapper[1] that uses native = installs of meson/ninja, and an attempt to install those as part of mxe[2]. Not sure how to use them though. Cheers, Tony [1] https://github.com/mxe/mxe/pull/1995 [2] https://github.com/mxe/mxe/pull/1996 From MAILER-DAEMON Fri Aug 30 09:49:13 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i3hH7-0004x5-Pk for mharc-mingw-cross-env-list@gnu.org; Fri, 30 Aug 2019 09:49:13 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:52836) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3hH2-0004qP-Oj for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 09:49:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i3hGz-0000zS-OI for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 09:49:07 -0400 Received: from mail-qk1-x741.google.com ([2607:f8b0:4864:20::741]:43780) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i3hGz-0000uu-Eb for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 09:49:05 -0400 Received: by mail-qk1-x741.google.com with SMTP id m2so6128556qkd.10 for ; Fri, 30 Aug 2019 06:49:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version; bh=zzjf0aCR8TDBSRB0ccxUq5z8UuJa8pp/kxs8b+fW0N8=; b=rhq/lo7WNjw1MPCcGy9M+nLcGKcj3/j6sTO7p1LZdaRfVZzvV2hy61O5BcO0LpSShp cxLwG4zV3NU6fintMKPgSY/z8vQJb+Y3kTuH+2XcqpITSahVLqclzjQHGYCQWTnvM6bo /oZdFXQvPGtasdVk9j1X79GuDw3kBv00DHN/nEavP2gRwAxOITMtlHwsvBLJFGflle8T lC0aWsN6Z52kdzBlWzmN6Bege4fqqX9qhxPu3VCpTFbl4cThe3F4Kt+clYbc/itAHYD8 no6Kvx81PKkFXdBp0P9wJVoHjsJKOxc8m3rWDN7O9b/ywNRp4MG/L2HpmXwId8Bybm+5 7KkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version; bh=zzjf0aCR8TDBSRB0ccxUq5z8UuJa8pp/kxs8b+fW0N8=; b=HKKKxr1y+CvRsU3e+vT69HbZ4NfpmsqFTGJop9iXyn8FXMe1PYb4Xum+q5BfU6F0WD pPoV3VWWr76EQ83r4iVwL4p2jpkVd64xZYNo+oOWbqa0AieiJIkppTaApRDmTTa5ULU3 qFxgM1aAU2Tgt9dIrw5op4pZx4j0VhFS50yqBUXfeehKz1x7FxmaJCj9SLl7APgDzVCB jywjCic7o24lmmaSZLwBO/dSOgd5f29tDE0+/L5gpX1uBaynSqdmiqCfddhr1n3W43L5 3q8e1oZ+nKpeCGJwsgfNL7NcNAgLRyB4LP9wwU5tmlgxO4NY5gMOPXKiEe+je4L2Kvp/ B2Kg== X-Gm-Message-State: APjAAAUTVSd3KlWaetKosZcVSe6IC3lhVDdBaFztlmLRhXgELyxVhSdY YRDwoa80zNikKZRiZOhBMUwctquz9L0= X-Google-Smtp-Source: APXvYqxETffx3BLf2vxneNiCMxscxCWRVhIsmbUeEw7gebiZ1gotsZCt5TXCtE4QRyihAv0drtDQLw== X-Received: by 2002:a37:4a95:: with SMTP id x143mr15090026qka.357.1567165956984; Fri, 30 Aug 2019 04:52:36 -0700 (PDT) Received: from [10.127.223.119] (ip-199-234-219-201.nextelmovil.cl. [201.219.234.199]) by smtp.gmail.com with ESMTPSA id h52sm3144526qte.73.2019.08.30.04.52.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Aug 2019 04:52:35 -0700 (PDT) Date: Fri, 30 Aug 2019 07:52:11 -0400 From: Gregorio Litenstein To: Tony Theodore Cc: mingw-cross-env-list@nongnu.org Message-ID: <12e47d41-7902-4947-8b2e-136f103d6543@Spark> In-Reply-To: <57133D8B-8A78-44FC-9C76-D1DB79A17844@logyst.com> References: <57133D8B-8A78-44FC-9C76-D1DB79A17844@logyst.com> X-Readdle-Message-ID: 12e47d41-7902-4947-8b2e-136f103d6543@Spark MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5d690e01_1190cde7_40c4" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::741 Subject: Re: [Mingw-cross-env-list] Default GCC version X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 13:49:12 -0000 --5d690e01_1190cde7_40c4 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hey there=21 yeah, I definitely like this idea and I agree it would be ti= dy and flexible. I personally wouldn't want to see the plug-in mechanism gone completely a= s I use it for performous but then again I could probably find some other= solution if it were to be done away with. Now I wonder... Which percentage of packages don't build because a newer = gcc and which percentage don't because because of a newer gcc AND the fac= t they're ancient=3F What I mean is... I'm fairly sure at least some of t= he =46TB=46S would probably be fixed by updating the packages themselves = to newer versions. Take the case of icu4c (for which I also made a PR btw= ); mxe currently ships 56.1, which was released in 2015. On Aug 30, 2019, 06:47 -0400, Tony Theodore , wrote: > Hi Gregorio, > > > On 28 Aug 2019, at 21:27, Gregorio Litenstein wrote: > > > > About a month ago, I naively submitted a PR to update the gcc package= to 8.3.0; I was then told gcc8 actually existed and lived in plugins. > > > > Something I=E2=80=99ve been asking myself since, though (and frankly = also before, or I wouldn=E2=80=99t have made the PR in the first place) i= s=E2=80=A6 does it actually serve any purpose to keep a three-year old co= mpiler as the default=3F Wouldn=E2=80=99t it make more sense to update th= e default to 8.3.0 (or 9.2.0) and keep GCC5 as a plug-in instead=3F There= comes a point when keeping an old compiler just becomes a drag because i= t makes updating other packages more difficult (it=E2=80=99s already been= happening for a while probably, I=E2=80=99d say) > > > > Is there something I=E2=80=99m missing=3F > > We=E2=80=99re missing a roadmap of planned development;) gcc version tr= acking > is a long-time issue trying to balance stability and new features. > > Currently, gcc5 is the only version that builds all mxe packages, thoug= h > later versions build a very large subset. The plugin mechanism isn't > ideal for several reasons: > - not immediately obvious for users > - not easily visible in logs etc. > - doesn't provide separation of gcc deps > - hard to test new versions/fallback to old > - doesn't provide package makefiles with awareness of compiler > > I plan to make compiler selection part of the target spec i.e: > x86=5F64-w64-mingw32.static.gcc8 > > This has many advantages: > - users who want stability can just stay on a tested version > - testing new versions is simple to enable and revert > - complier deps are properly isolated > - package makefiles can set appropriate compiler-based flags > - makes it easier to introduce clang toolchain > > In this scenario, mxe will no longer have a =22default=22 compiler, jus= t a > version that currently builds all packages. There'll be no pressure to > update that; we can keep it stable for (say) binary packages used in CI= > environments, while giving users who want to build their own more > options. =46or that matter, we could build binaries for newer versions > to push the ecosystem along. > > Keeping the current default at gcc5 gives us a strong forcing function > to deprecate the plugin mechanism. > > I've had this working before (but lost all my WIP a few months ago), if= > it's not ready again by December - we'll update the default. > > Cheers, > > Tony > --5d690e01_1190cde7_40c4 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hey there=21 yeah, I definitely like this idea and = I agree it would be tidy and flexible.

I personally wouldn't want to see the plug-in mecha= nism gone completely as I use it for performous but then again I could pr= obably find some other solution if it were to be done away with.

Now I wonder... Which percentage of packages don't = build because a newer gcc and which percentage don't because because of a= newer gcc AND the fact they're ancient=3F What I mean is... I'm fairly s= ure at least some of the =46TB=46S would probably be fixed by updating th= e packages themselves to newer versions. Take the case of icu4c (for whic= h I also made a PR btw); mxe currently ships 56.1, which was released in = 2015.
On Aug 30, 2019, 06:47 -0400, Tony = Theodore <tonyt=40logyst.com>, wrote:
Hi= Gregorio,

On= 28 Aug 2019, at 21:27, Gregorio Litenstein <g.litenstein=40gmail.com&= gt; wrote:

About a month ago, I naively submitted a PR to update the gcc package to = 8.3.0; I was then told gcc8 actually existed and lived in plugins.

Something I=E2=80=99ve been asking myself since, though (and frankly also= before, or I wouldn=E2=80=99t have made the PR in the first place) is=E2= =80=A6 does it actually serve any purpose to keep a three-year old compil= er as the default=3F Wouldn=E2=80=99t it make more sense to update the de= fault to 8.3.0 (or 9.2.0) and keep GCC5 as a plug-in instead=3F There com= es a point when keeping an old compiler just becomes a drag because it ma= kes updating other packages more difficult (it=E2=80=99s already been hap= pening for a while probably, I=E2=80=99d say)

Is there something I=E2=80=99m missing=3F

We=E2=80=99re missing a roadmap of planned development;) gcc version trac= king
is a long-time issue trying to balance stability and new features.

Currently, gcc5 is the only version that builds all mxe packages, though<= br /> later versions build a very large subset. The plugin mechanism isn't
ideal for several reasons:
- not immediately obvious for users
- not easily visible in logs etc.
- doesn't provide separation of gcc deps
- hard to test new versions/fallback to old
- doesn't provide package makefiles with awareness of compiler

I plan to make compiler selection part of the target spec i.e:
x86=5F64-w64-mingw32.static.gcc8

This has many advantages:
- users who want stability can just stay on a tested version
- testing new versions is simple to enable and revert
- complier deps are properly isolated
- package makefiles can set appropriate compiler-based flags
- makes it easier to introduce clang toolchain

In this scenario, mxe will no longer have a =22default=22 compiler, just = a
version that currently builds all packages. There'll be no pressure to update that; we can keep it stable for (say) binary packages used in CI environments, while giving users who want to build their own more
options. =46or that matter, we could build binaries for newer versions to push the ecosystem along.

Keeping the current default at gcc5 gives us a strong forcing function to deprecate the plugin mechanism.

I've had this working before (but lost all my WIP a few months ago), if it's not ready again by December - we'll update the default.

Cheers,

Tony

--5d690e01_1190cde7_40c4-- From MAILER-DAEMON Fri Aug 30 14:48:14 2019 Received: from list by lists.gnu.org with archive (Exim 4.90_1) id 1i3lwT-00022t-Te for mharc-mingw-cross-env-list@gnu.org; Fri, 30 Aug 2019 14:48:13 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:36627) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3lwQ-00020X-1g for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 14:48:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i3lwO-0001TR-5B for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 14:48:09 -0400 Received: from mout.kundenserver.de ([212.227.126.134]:59303) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i3lwN-0001SS-LP for mingw-cross-env-list@nongnu.org; Fri, 30 Aug 2019 14:48:08 -0400 Received: from localhost ([31.17.132.201]) by mrelayeu.kundenserver.de (mreue012 [213.165.67.97]) with ESMTPSA (Nemesis) id 1MoNMu-1iWTz046Rs-00orkO; Fri, 30 Aug 2019 20:48:03 +0200 To: Gregorio Litenstein , Tony Theodore Cc: mingw-cross-env-list@nongnu.org References: <57133D8B-8A78-44FC-9C76-D1DB79A17844@logyst.com> <12e47d41-7902-4947-8b2e-136f103d6543@Spark> From: Lars Holger Engelhard Message-ID: <7d9d3dc0-de92-3975-c759-9d30cff98032@lars-engelhard.de> Date: Fri, 30 Aug 2019 20:47:48 +0200 MIME-Version: 1.0 In-Reply-To: <12e47d41-7902-4947-8b2e-136f103d6543@Spark> Content-Type: multipart/alternative; boundary="------------5FB7E579EBF0607AAF44CB96" Content-Language: en-US X-Provags-ID: V03:K1:mZdYUXzVBrscQCmlDeXyVngN0o0+/enreqrLyOkpjVo+T/WEwya wSiWvRFK5IEEO0Oz7GhOR6vd67c1EbkCZSdymA7GN0t8gwNUt9yoQFLAOGDKc08KjdBR8as DbzOh823SgfY5U9ebG9x3/Qlz5pnp4elRhGBrxGiIbh3jSboCX5jcMXBogWAHpK1SSk9IZE Ww17sZsW3r7J6fYGdKxbQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:Yp4OTJgzyjk=:t/Um/jrvU2vxYN2XKs9i6H pCxnsOJZdIuuV775divPcGra5adLXGiXgRu0E/22CmERZz/H2Ewha8vUvQQwAPsOBo9LOhjNQ zjbb5HchVb/FK24RwtKANj34xu6QDzSQFDmtHbCzMG/TIpO7A7wuzcomtgSaY5HHWDKsODZgr 5HCXVSjAejn0yS+IpGbc0PNhsQatFmITMkD0nhQhIImMe6BPZ/CmQD7KSWdxTIQErcmtC8L+b nIZSwVt/9p2p0ruuDwrKq8efrc8hbFylseScyAszk34tbbAT/E+Iy1Iszr4wJXPo4dbOZGvGq 5JFVSFCtiMvj3Kgr+GbR6MjrPQjcWejbpu3Geo0soJbbAg1X1w/13Mo+Bv6quznlWiJLBEw9W REjfjGxFd5EFCv9EpnLJIKqsRTapPH9RvzL7Y+8ldQzd6Z06i5M6KDYdfTzCDs4QoS/UIMaay 7N8bAoYTOsQc6eNhsG0RpPZFAv5CxZox6srKX13BDEw9/SJ6gbrJ5OoXdEyJO/slM/HXF4AXq odziKDNbZLH386qEMGzhciwoptrfKVK9Rcdl4U1ZV9kCK86nriRwPdE+0OBH0Vzhz+EoqqfNY 97gV5G3BjjSu6yYV+YpOZDrYCyTz/dzdzVsPctnQtvUWpJlp1LgVHxiWQqoHL5ipXkmpGVJyo y1+/g+1GplNeWA6p2t/0BaSDvQH5S6sU9eydWMTF1Rg2RRboVaqP7AeEs9CS9EyylhesAfkVa kA3EP+Wm1tixKkUFedYH5E91Tb/bopCLlIxO6kHnrefIm/K1ggYoZapStiZQQY1nPEPTp9LbW hbWveu8GMWzvteeaPSrbwx4zOqzKWTVK6Z3jIlrgTiivX9komQ= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.126.134 Subject: Re: [Mingw-cross-env-list] Default GCC version X-BeenThere: mingw-cross-env-list@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Aug 2019 18:48:12 -0000 This is a multi-part message in MIME format. --------------5FB7E579EBF0607AAF44CB96 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hey everyone, makes sense and from architectural point of view a clear solution.    x86_64-w64-mingw32.static.gcc8 Maybe there should be a default that is 'rock solid' for the already known x86_64-w64-mingw32.static as a default for those who don't catch up in their build environments. Cheers,    Lars Am 30.08.2019 um 13:52 schrieb Gregorio Litenstein: > Hey there! yeah, I definitely like this idea and I agree it would be > tidy and flexible. > > I personally wouldn't want to see the plug-in mechanism gone > completely as I use it for performous but then again I could probably > find some other solution if it were to be done away with. > > Now I wonder... Which percentage of packages don't build because a > newer gcc and which percentage don't because because of a newer gcc > AND the fact they're ancient? What I mean is... I'm fairly sure at > least some of the FTBFS would probably be fixed by updating the > packages themselves to newer versions. Take the case of icu4c (for > which I also made a PR btw); mxe currently ships 56.1, which was > released in 2015. > On Aug 30, 2019, 06:47 -0400, Tony Theodore , wrote: >> Hi Gregorio, >> >>> On 28 Aug 2019, at 21:27, Gregorio Litenstein >>> wrote: >>> >>> About a month ago, I naively submitted a PR to update the gcc >>> package to 8.3.0; I was then told gcc8 actually existed and lived in >>> plugins. >>> >>> Something I’ve been asking myself since, though (and frankly also >>> before, or I wouldn’t have made the PR in the first place) is… does >>> it actually serve any purpose to keep a three-year old compiler as >>> the default? Wouldn’t it make more sense to update the default to >>> 8.3.0 (or 9.2.0) and keep GCC5 as a plug-in instead? There comes a >>> point when keeping an old compiler just becomes a drag because it >>> makes updating other packages more difficult (it’s already been >>> happening for a while probably, I’d say) >>> >>> Is there something I’m missing? >> >> We’re missing a roadmap of planned development;) gcc version tracking >> is a long-time issue trying to balance stability and new features. >> >> Currently, gcc5 is the only version that builds all mxe packages, though >> later versions build a very large subset. The plugin mechanism isn't >> ideal for several reasons: >> - not immediately obvious for users >> - not easily visible in logs etc. >> - doesn't provide separation of gcc deps >> - hard to test new versions/fallback to old >> - doesn't provide package makefiles with awareness of compiler >> >> I plan to make compiler selection part of the target spec i.e: >> x86_64-w64-mingw32.static.gcc8 >> >> This has many advantages: >> - users who want stability can just stay on a tested version >> - testing new versions is simple to enable and revert >> - complier deps are properly isolated >> - package makefiles can set appropriate compiler-based flags >> - makes it easier to introduce clang toolchain >> >> In this scenario, mxe will no longer have a "default" compiler, just a >> version that currently builds all packages. There'll be no pressure to >> update that; we can keep it stable for (say) binary packages used in CI >> environments, while giving users who want to build their own more >> options. For that matter, we could build binaries for newer versions >> to push the ecosystem along. >> >> Keeping the current default at gcc5 gives us a strong forcing function >> to deprecate the plugin mechanism. >> >> I've had this working before (but lost all my WIP a few months ago), if >> it's not ready again by December - we'll update the default. >> >> Cheers, >> >> Tony >> -- -------------------------------------- MBA B.Eng. Lars Holger Engelhard eMail: mail@lars-engelhard.com mobil: 0049 176 23120355 web: http://www.lars-engelhard.com --------------5FB7E579EBF0607AAF44CB96 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hey everyone,

makes sense and from architectural point of view a clear solution.
   x86_64-w64-mingw32.static.gcc8
Maybe there should be a default that is 'rock solid' for the already known
    x86_64-w64-mingw32.static
as a default for those who don't catch up in their build environments.

Cheers,
   Lars

Am 30.08.2019 um 13:52 schrieb Gregorio Litenstein:
Hey there! yeah, I definitely like this idea and I agree it would be tidy and flexible.

I personally wouldn't want to see the plug-in mechanism gone completely as I use it for performous but then again I could probably find some other solution if it were to be done away with.

Now I wonder... Which percentage of packages don't build because a newer gcc and which percentage don't because because of a newer gcc AND the fact they're ancient? What I mean is... I'm fairly sure at least some of the FTBFS would probably be fixed by updating the packages themselves to newer versions. Take the case of icu4c (for which I also made a PR btw); mxe currently ships 56.1, which was released in 2015.
On Aug 30, 2019, 06:47 -0400, Tony Theodore <tonyt@logyst.com>, wrote:
Hi Gregorio,

On 28 Aug 2019, at 21:27, Gregorio Litenstein <g.litenstein@gmail.com> wrote:

About a month ago, I naively submitted a PR to update the gcc package to 8.3.0; I was then told gcc8 actually existed and lived in plugins.

Something I’ve been asking myself since, though (and frankly also before, or I wouldn’t have made the PR in the first place) is… does it actually serve any purpose to keep a three-year old compiler as the default? Wouldn’t it make more sense to update the default to 8.3.0 (or 9.2.0) and keep GCC5 as a plug-in instead? There comes a point when keeping an old compiler just becomes a drag because it makes updating other packages more difficult (it’s already been happening for a while probably, I’d say)

Is there something I’m missing?

We’re missing a roadmap of planned development;) gcc version tracking
is a long-time issue trying to balance stability and new features.

Currently, gcc5 is the only version that builds all mxe packages, though
later versions build a very large subset. The plugin mechanism isn't
ideal for several reasons:
- not immediately obvious for users
- not easily visible in logs etc.
- doesn't provide separation of gcc deps
- hard to test new versions/fallback to old
- doesn't provide package makefiles with awareness of compiler

I plan to make compiler selection part of the target spec i.e:
x86_64-w64-mingw32.static.gcc8

This has many advantages:
- users who want stability can just stay on a tested version
- testing new versions is simple to enable and revert
- complier deps are properly isolated
- package makefiles can set appropriate compiler-based flags
- makes it easier to introduce clang toolchain

In this scenario, mxe will no longer have a "default" compiler, just a
version that currently builds all packages. There'll be no pressure to
update that; we can keep it stable for (say) binary packages used in CI
environments, while giving users who want to build their own more
options. For that matter, we could build binaries for newer versions
to push the ecosystem along.

Keeping the current default at gcc5 gives us a strong forcing function
to deprecate the plugin mechanism.

I've had this working before (but lost all my WIP a few months ago), if
it's not ready again by December - we'll update the default.

Cheers,

Tony


-- 
-------------------------------------- 
  MBA B.Eng. Lars Holger Engelhard 
  eMail: mail@lars-engelhard.com 
  mobil: 0049 176 23120355
  web:   http://www.lars-engelhard.com
--------------5FB7E579EBF0607AAF44CB96--