From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?UTF-8?Q?=C3=93scar?= Fuentes Newsgroups: gmane.emacs.bugs Subject: bug#19111: 25.0.50; 32 bits temacs.exe is linked with wrong image-base when built on 64 bit Windows host Date: Thu, 20 Nov 2014 17:23:14 +0100 Message-ID: <87a93lrgct.fsf@wanadoo.es> References: <87fvdfrl4p.fsf@telefonica.net> <83k32q7wkl.fsf@gnu.org> <87bno2swxp.fsf@wanadoo.es> <83egsy7d2x.fsf@gnu.org> <87siheqzq9.fsf@wanadoo.es> <83389d7t89.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1416500679 8497 80.91.229.3 (20 Nov 2014 16:24:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Nov 2014 16:24:39 +0000 (UTC) Cc: 19111@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Nov 20 17:24:32 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XrUWp-0003aq-KJ for geb-bug-gnu-emacs@m.gmane.org; Thu, 20 Nov 2014 17:24:19 +0100 Original-Received: from localhost ([::1]:36155 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XrUWp-0001Aa-6P for geb-bug-gnu-emacs@m.gmane.org; Thu, 20 Nov 2014 11:24:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50081) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XrUWf-00017Q-BK for bug-gnu-emacs@gnu.org; Thu, 20 Nov 2014 11:24:15 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XrUWY-0000dj-ME for bug-gnu-emacs@gnu.org; Thu, 20 Nov 2014 11:24:09 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:42493) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XrUWY-0000df-Jh for bug-gnu-emacs@gnu.org; Thu, 20 Nov 2014 11:24:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1XrUWY-0002Z2-2e for bug-gnu-emacs@gnu.org; Thu, 20 Nov 2014 11:24:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=C3=93scar?= Fuentes Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 20 Nov 2014 16:24:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 19111 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 19111-submit@debbugs.gnu.org id=B19111.14165006019808 (code B ref 19111); Thu, 20 Nov 2014 16:24:02 +0000 Original-Received: (at 19111) by debbugs.gnu.org; 20 Nov 2014 16:23:21 +0000 Original-Received: from localhost ([127.0.0.1]:39706 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1XrUVs-0002Y5-45 for submit@debbugs.gnu.org; Thu, 20 Nov 2014 11:23:20 -0500 Original-Received: from relaycp04.dominioabsoluto.net ([217.116.26.100]:59879) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1XrUVp-0002Xs-HR for 19111@debbugs.gnu.org; Thu, 20 Nov 2014 11:23:19 -0500 Original-Received: from smtp.movistar.es (smtp10.acens.net [86.109.99.134]) by relaycp04.dominioabsoluto.net (Postfix) with ESMTP id C3DDE64FED; Thu, 20 Nov 2014 17:23:15 +0100 (CET) X-CTCH-RefID: str=0001.0A0B0205.546E1573.030A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-Spam: Unknown Original-Received: from qcore (79.158.48.132) by smtp.movistar.es (8.6.122.03) (authenticated as 981711563$telefonica.net) id 5453978C00A4EC87; Thu, 20 Nov 2014 16:23:15 +0000 In-Reply-To: <83389d7t89.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 20 Nov 2014 18:05:26 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:96327 Eli Zaretskii writes: >> Since we already special-case MinGW on the configure script, and fixing >> the problem there only changes how the special case is implemented >> without touching new areas, I'll very much prefer to apply the patch >> shown on my previous message and keep the nice and simple "configure && >> make" procedure working on all cases. > > OK, but at least let's keep the build/host/target triplet correct. > It's not right for us to disregard it when it doesn't fit our needs, > because the entire configure script is based on the notion that the > triplet is the starting point on which all the rest is based. > > So, if we want to fix that, let's fix the triplet early on, to specify > a i686 build, and let the rest of the script do its job as usual. I suspect that you have a point here which I don't entirely grasp. Are you thinking on a scenario where the user sets --host/--build on the configure script to something that doesn't correlate to the contents of $MSYSTEM? > Besides, I came to a conclusion that I don't understand how your > suggestion will work anyway. AFAICT, you just replace tests based on > one wrong string (x86_64-*-*) with another wrong string (MINGW64). > > Or are you saying that MSYS2 somehow magically does not give $MSYSTEM > the value MINGW64 when you configure for a 32-bit build? If so, how > does this magic work? Because if MSYS2 always sets MSYSTEM=MINGW64, > then your suggestion isn't going to work, is it? > > More generally, how do you tell configure that you want a 32-bit build > using MinGW64 toolchain? That requires some special compiler switches > (like -m32 or some such), no? We are using $MSYSTEM to special-case MinGW(-w64). $MSYSTEM is MINGW32 when using the 32 bit toolset and MINGW64 when using the 64 bit toolset. That's true for MSYS2/MinGW-w64. I'm not sure if MSYS sets $MSYSTEM to MINGW or MINGW32, but any of it should be ok with the patch. The -m32 switch is actively discouraged by the MinGW-w64 community and the official builds does not support it. Does this answer your questions?