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: g2news2.google.com!postnews.google.com!v12g2000vby.googlegroups.com!not-for-mail From: jrmarino Newsgroups: comp.lang.ada Subject: Re: Ada cross-compiler (Windows) to Android Date: Fri, 15 Jul 2011 09:51:22 -0700 (PDT) Organization: http://groups.google.com Message-ID: 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> <2f757ea6-a681-463a-ab0e-dd29ae089276@u26g2000vby.googlegroups.com> NNTP-Posting-Host: 90.38.172.56 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1310748682 12131 127.0.0.1 (15 Jul 2011 16:51:22 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 15 Jul 2011 16:51:22 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: v12g2000vby.googlegroups.com; posting-host=90.38.172.56; posting-account=Zsf4jwoAAADEqwCydv835KU9-S3h_Y26 User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HNKRUAELSC X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.112 Safari/534.30,gzip(gfe) Xref: g2news2.google.com comp.lang.ada:21179 Date: 2011-07-15T09:51:22-07:00 List-Id: On Jul 15, 12:06=A0pm, Ludovic Brenta wrote: > > Could you explain how your repository is organized? =A0I 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]? =A0This technique allows you to make your patches available to > anyone who wants them, even before you submit them to the FSF. =A0(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. Sure, Ludovic. I need to first make a distinction between gcc 4.6 series and 4.7 series. For the 4.6 series, I basically dumped gcc/ada (and subdirs) and the two Ada testsuites along with some key files (e.g. config.gcc), maintaining the same hierarchy. When it's time to build a tarball, I overlay these files on top of a stock gcc. (for c++ testsuite and a few key files, I also apply a set of patches). That technique basically forced me to use "meld" a lot and manually maintain a list of files that differs. It is painful to do. So solve that, and to prepare proper patches for import into gcc, I created a new branch for gcc 4.7 that only contains patches. To produce 4.7 tarball, I just apply the patches to a copy of the stock gcc. That way I can just send the patch to gcc and remove it from the repository after it gets accepted. That was the plan anyway, and the idea is that over time the number of patches would decrease to a very low number. I took a quick glance at that quilt site which I had never heard of before, but it wasn't immediately obvious to me how it is supposed to work.