From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: MS-Windows build using Posix configury Date: Mon, 13 May 2013 19:23:13 +0300 Message-ID: <83wqr297da.fsf@gnu.org> References: <83d2tu49lu.fsf@gnu.org> <834nezzzma.fsf@gnu.org> <8361z2psr1.fsf@gnu.org> <83zjweo5dh.fsf@gnu.org> <83sj25nym2.fsf@gnu.org> <837gjhnowi.fsf@gnu.org> <8338u4o39r.fsf@gnu.org> <83zjwbkmt2.fsf@gnu.org> <83wqrfkjvo.fsf@gnu.org> <838v3qebns.fsf@gnu.org> <83wqr9csah.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1368462222 9229 80.91.229.3 (13 May 2013 16:23:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 13 May 2013 16:23:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andy Moreton Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 13 18:23:40 2013 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 1UbvXE-0007Wq-Hn for ged-emacs-devel@m.gmane.org; Mon, 13 May 2013 18:23:36 +0200 Original-Received: from localhost ([::1]:42440 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UbvXE-00059T-4q for ged-emacs-devel@m.gmane.org; Mon, 13 May 2013 12:23:36 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:36732) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UbvXA-00059O-SI for emacs-devel@gnu.org; Mon, 13 May 2013 12:23:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UbvX9-0004xy-Ha for emacs-devel@gnu.org; Mon, 13 May 2013 12:23:32 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:46608) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UbvX9-0004uA-8n for emacs-devel@gnu.org; Mon, 13 May 2013 12:23:31 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MMQ00E00VSE2I00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Mon, 13 May 2013 19:23:23 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MMQ00DGFW6YTN80@a-mtaout22.012.net.il>; Mon, 13 May 2013 19:23:23 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:159543 Archived-At: > From: Andy Moreton > Date: Mon, 13 May 2013 13:23:30 +0100 > > >> The only new information I have about this issue is that today, after > >> doing a whole bootstrap and a "make install" (with my MSYS Texinfo, as > >> always), the resulting Info directory looks good (it has only > >> UNIX-type EOLs). > >> > >> I'm thinking that probably this problem appears when, at the time you > >> do a "make install", your PREFIX/share/info directory already has some > >> info manuals with DOS-type EOLs. (For example, the GnuTLS library I > >> downloaded from ezwinports has an info manual with DOS-type EOLs) > >> > >> I think that the other day, while testing things, I deleted all the > >> files in PREFIX/share/info, and therefore now all the info manuals are > >> the installed with Emacs, and they have all the same EOL-type: UNIX. > > > > But then the problem is not really solved: anyone who would install > > Emacs into an already populated tree will get the mixed EOLs issue > > back. > > Hi Eli, > > This sounds like its a minor enough issue that it could be solved after > the changes are committed. Not only is it minor, its solution is perfectly clear: use the native Windows build of Texinfo. I will update the instructions accordingly. > If you are not comfortable doing that yet, could you please post the > latest version of your patch so I can help test it ? The above is not what is holding the merge. I needed to leave the branch alone for a while, because both GNU Make and Gawk have, or are about to, release a new version which includes features that needed me to do some non-trivial coding to support them. That took a week or two of my time. With this out of my way, I need to update the branch to handle the changes in the configury committed lately to the trunk, to handle the ACL portability. (I was actually hoping that something like this would happen, because I want to see how much effort is needed to make such adaptations.) Before I adapt to that change, I cannot merge my branch onto the trunk, because the result will most probably fail to compile. I hope to do that in a couple of days, and then I'll merge and announce. Stay tuned, and thanks for encouragement.