From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,d1e954ab22509c0a X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Path: g2news1.google.com!postnews.google.com!u26g2000vby.googlegroups.com!not-for-mail From: Ludovic Brenta Newsgroups: comp.lang.ada Subject: Re: Ada cross-compiler (Windows) to Android Date: Fri, 15 Jul 2011 03:06:18 -0700 (PDT) Organization: http://groups.google.com Message-ID: <2f757ea6-a681-463a-ab0e-dd29ae089276@u26g2000vby.googlegroups.com> References: <12f3f5b7-5289-45c4-a346-7dc6ee2f274b@glegroupsg2000goo.googlegroups.com> <01b8c553-42e5-4ddc-877e-ef8f85361ac1@s17g2000yqs.googlegroups.com> <09b8124a-a200-407f-9e5f-4877d50088f1@r18g2000vbs.googlegroups.com> NNTP-Posting-Host: 153.98.68.197 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1310724735 29788 127.0.0.1 (15 Jul 2011 10:12:15 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 15 Jul 2011 10:12:15 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: u26g2000vby.googlegroups.com; posting-host=153.98.68.197; posting-account=pcLQNgkAAAD9TrXkhkIgiY6-MDtJjIlC User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HUALESRCNK X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101206 Red Hat/3.6-2.el5 Firefox/3.6.13,gzip(gfe) Xref: g2news1.google.com comp.lang.ada:20206 Date: 2011-07-15T03:06:18-07:00 List-Id: jrmarino wrote on comp.lang.ada: >> In short (if possible!) what is missing from stock GCC sources to preven= t >> this? > > Way too much to list. =A0There's a reason why a separate repository > exists. > >> Could the code you added be available in e.g. the form of patches to >> apply to stock GCC? > > This question indicates that you are unfamiliar with the process to > submit patches to gcc. Could you explain how your repository is organized? I would think you'd cloned the upstream git repository[1] and created a branch of your own where you maintain a stack of patches using quilt[2] or StGit[3]? This technique allows you to make your patches available to anyone who wants them, even before you submit them to the FSF. (The Debian patches are similarly maintained in a monotone repository, using quilt.) [1] http://gcc.gnu.org/git/ [2] http://savannah.nongnu.org/projects/quilt [3] http://git.or.cz/course/stgit.html -- Ludovic Brenta. The enabler generates a wide-spectrum, agile, bottom line, while siloed tactics enable the enablers.