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.devel Subject: Re: Building Emacs on MSYS2 Date: Thu, 14 Apr 2016 22:09:50 +0200 Message-ID: <87r3e8x88h.fsf@wanadoo.es> References: <56CCD91E.6070507@alice.it> <56CD8408.1000701@alice.it> <83wppuggb4.fsf@gnu.org> <56CE2CA7.5050906@alice.it> <83io1cg2pt.fsf@gnu.org> <56DA0327.2030009@alice.it> <83oaatxu72.fsf@gnu.org> <570C4307.6050907@alice.it> <83k2k2g82s.fsf@gnu.org> <570EA823.1010404@alice.it> <570EBADD.2060604@cs.ucla.edu> <570EC198.5090407@alice.it> <570EF300.3050104@cs.ucla.edu> <570F4EC7.3060403@alice.it> <83twj4dx7q.fsf@gnu.org> <878u0gyyge.fsf_-_@wanadoo.es> <570FC0BC.8030709@cs.ucla.edu> <874mb4yxqi.fsf@wanadoo.es> <83potsduv5.fsf@gnu.org> <87vb3kxho5.fsf@wanadoo.es> <83mvowdru7.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1460664646 2824 80.91.229.3 (14 Apr 2016 20:10:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 14 Apr 2016 20:10:46 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Apr 14 22:10:38 2016 Return-path: Envelope-to: ged-emacs-devel@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 1aqnb3-0003fn-Lv for ged-emacs-devel@m.gmane.org; Thu, 14 Apr 2016 22:10:37 +0200 Original-Received: from localhost ([::1]:45913 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqnb2-0004o7-M1 for ged-emacs-devel@m.gmane.org; Thu, 14 Apr 2016 16:10:36 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40786) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqnaZ-0004he-LJ for emacs-devel@gnu.org; Thu, 14 Apr 2016 16:10:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aqnaW-0003C7-D0 for emacs-devel@gnu.org; Thu, 14 Apr 2016 16:10:07 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:45686) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aqnaW-0003Bw-74 for emacs-devel@gnu.org; Thu, 14 Apr 2016 16:10:04 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aqnaU-0003OS-2r for emacs-devel@gnu.org; Thu, 14 Apr 2016 22:10:02 +0200 Original-Received: from 120.red-88-22-75.staticip.rima-tde.net ([88.22.75.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Apr 2016 22:10:02 +0200 Original-Received: from ofv by 120.red-88-22-75.staticip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Apr 2016 22:10:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 31 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 120.red-88-22-75.staticip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.92 (gnu/linux) Cancel-Lock: sha1:yXi7SgWpW1dS6ym0AkjAWPfvYgc= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:202933 Archived-At: Eli Zaretskii writes: >> >> >> local with_wide_int='no' >> >> >> >> >> >> if test "${CARCH}" == 'x86_64'; then >> >> >> with_wide_int='yes' >> >> >> fi >> >> > >> >> > You shouldn't need this. --with-wide-int is effective only on 32-bit >> >> > platforms; integers are always wide on 64-bit platforms. >> >> >> >> Right. Maybe the person who introduced that code on the PKGBUILD worried >> >> about the possibility of changing the default on x86 to wide-int. IIRC >> >> there was some discussion about that on the past. >> > >> > The discussions were about the 32-bit build. If anything, the script >> > should use --with-wide-int in the 32-bit build, i.e. exactly the >> > opposite of what it does now. >> >> My point is that the PKGBUILD author possibly was "protecting" the >> package against upstream changing the x86 default to --with-wide-int. > > It does exactly the opposite, and to the non-x86 build, so I don't > understand how did you reach that conclusion. You misread the code. It unconditionally sets with_wide_int='no' and *then* checks if the arch is x86_64, in which case sets with_wide_int='yes'. Hence the code is explicitly setting --with-wide-int on both cases to a value which happens to coincide with the default *for now*.