From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4032 invoked by alias); 26 Feb 2014 23:39:52 -0000 Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org Received: (qmail 4019 invoked by uid 89); 26 Feb 2014 23:39:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qc0-f175.google.com Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com) (209.85.216.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Wed, 26 Feb 2014 23:39:50 +0000 Received: by mail-qc0-f175.google.com with SMTP id m20so1746722qcx.6 for ; Wed, 26 Feb 2014 15:39:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7Xp7zSREnbxBoe7NFHcby3JUCZ+D3CSg8gI9W6dsKBI=; b=aB982mIJytK9ZfhWCMrZpRlxEyYNlBA/kX15qhUq7j3YTVAiUtd8JYSUNibgaT9DYP KYxQVBcIjRnowFUvdu4jd+K+7v3t0hkXQvBAs2LKUBj29QLZQrtnsJMMjMvqUdYbiZ5K hwLCTHyWaSpXAil9a3s3pmcGmMh3QauyjjorJv9MAvXSPhcoTH1n0Nz2diMLJ+jOTalz sTXeOtNFM1Pe7hrvoWHNcyUusXKVKFnsRBhauhcV4N57Mzel4nj26m0E1Kdqku/ZC8Ry CI6cQHMqGlY4a0o+8OH0cAILkd6VDlleMtFQjXDGIFUhfpNFrL7DpViLSB4B317yj2g8 3FTg== X-Gm-Message-State: ALoCoQnDgpzS1KdrKv+csYXGf4tsLukfNWQfjVgWqni9JGVoedPjVsLAAS3dqP93MAXNYdlmB8Sy X-Received: by 10.140.49.210 with SMTP id q76mr2937352qga.103.1393457988009; Wed, 26 Feb 2014 15:39:48 -0800 (PST) Received: from [192.168.141.83] (69-165-220-158.dsl.teksavvy.com. [69.165.220.158]) by mx.google.com with ESMTPSA id d15sm7500552qaq.4.2014.02.26.15.39.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Feb 2014 15:39:47 -0800 (PST) Message-ID: <530E7B42.5070409@linaro.org> Date: Wed, 26 Feb 2014 23:39:00 -0000 From: Trevor Woerner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Ray Donnelly CC: "crossgcc@sourceware.org" Subject: Re: multilib-list References: <530E2237.50603@linaro.org> <530E45F5.1040404@linaro.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-02/txt/msg00075.txt.bz2 Hello Ray, Brian, and everyone else, On 02/26/14 15:05, Ray Donnelly wrote: > AFAIK, Bryan Hundven was going to exclude --with-multilib-list for arm > if gcc < 4.9, and exclude it altogether for all arches other than Intel, > arm and sh. It seems like a lot of initial (and on-going) work (multilib_add_archs) to keep track of which architectures and which versions have multilib support. I guess it would help users from accidentally creating invalid configurations, but on the other hand I can't help think it would be easier and more flexible to have the option always available (when multilib is selected) and include a strongly worded help message instead :-) In my case I'd like to use it to build multilib toolchains using the "custom" version. Could that scenario be added too? It looks like that won't be easy. I think it would be safe to assume if a user is performing a build using custom versions that they're knowledgeable enough to know if they want multilib. It reminds me of the patches you have to add snapshots and additional versions. I still think it would just be best to provide the list option if the user selects multilib since there's a decent chance they might know what they're doing and a missing multilib list isn't a problem. It looks like your focus is on 32-bit versus 64-bit tools and libraries. All I'm looking for is to specify multiple architectures (e.g. armv6-m armv7e-m). I'm not sure the work you're doing will accommodate my use-case too. But I'll do some investigation and testing and let you know how it goes. > Any chance you could point me to some information on how to use a second > remote patch queue with mercurial? I would like to work with these > patches, but I'm rather new to mercurial, never mind its queue add-on. > > > I'm also quite new to mercurial, so someone may need to correct me. > Tutorial: > http://mercurial.selenic.com/wiki/MqTutorial Thank you so much for that list! The "qclone" and "qpush -a" commands were especially helpful! Best regards, Trevor -- For unsubscribe information see http://sourceware.org/lists.html#faq