Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 95287 invoked from network); 20 Feb 2007 14:37:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Feb 2007 14:37:03 -0000 Received: (qmail 44580 invoked by uid 500); 20 Feb 2007 14:37:03 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 44550 invoked by uid 500); 20 Feb 2007 14:37:03 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 44538 invoked by uid 99); 20 Feb 2007 14:37:03 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Feb 2007 06:37:03 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of gcjhd-harmony-dev@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Feb 2007 06:36:51 -0800 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HJW5w-0001GQ-Gq for dev@harmony.apache.org; Tue, 20 Feb 2007 15:35:52 +0100 Received: from msfwpr01.ims.intel.com ([62.118.80.132]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 20 Feb 2007 15:35:52 +0100 Received: from gshimansky by msfwpr01.ims.intel.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 20 Feb 2007 15:35:52 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: dev@harmony.apache.org From: Gregory Shimansky Subject: Re: [general] Harmony enabling at Windows / x86_64 Date: Tue, 20 Feb 2007 17:34:33 +0300 Lines: 43 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: msfwpr01.ims.intel.com User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) In-Reply-To: Sender: news X-Virus-Checked: Checked by ClamAV on apache.org Geir Magnusson Jr. wrote: > > On Feb 20, 2007, at 7:24 AM, Gregory Shimansky wrote: > >> Ivan Zvolsky wrote: >>> On 2/19/07, Gregory Shimansky wrote: >>>> >>>> Ivan Zvolsky wrote: >>>> > I have also put my efforts with drlvm building to HARMONY-3196. The >>>> patch >>>> > makes drlvm buildable on windows/em64t (and shouldn't break >>>> building on >>>> > other platforms). >>>> > >>>> > It still has some things to do, which I described in subtasks for >>>> > HARMONY-3196. >>>> >>>> I looked at the patches and I have a question. You've added amd64 >>>> architecture in some select statements in the build along with em64t >>>> flag. I thought that from the build point they are equivalent, and >>>> build.arch property is defined in build.xml for all kinds of arch >>>> (x86_64, em64t, amd64) to be equal to "em64t". Why add another flag in >>>> build files? >>> I can't remember why I added this. But I just tried to modify all >>> selects >>> like "em64t,amd64" to simply "em64t" and the build worked fine. What >>> is the >>> best option to do: >>> 1) should I replace drlvm_build_system.patch with newer version? >>> 2) or add newer version without removing the old one? >>> 3) or prepare a patch for drlvm_build_system.patch file? >> >> I'll take care about it myself. I'll remove all amd64 flags. >> Converting em64t to x86_64 may be done later separately from enabling >> x86_64 windows. > > If you are going to be doing it anyway, why not convert to "x86_64"? I'll do it but I don't want to break things right now not to break Ivan's patches. Also I would like to change no more than needed at a time. -- Gregory