[Setting Reply-To to powerpc-discuss] ken mays wrote: > Update a review of the current toolchain and a few > surgical tools: > > Ref: > http://www.opensolaris.org/os/community/power_pc/ppc_tools/ > 1. binutils 2.16.1 (2.16) > 2. GCC 4.0.2 (4.0.0)
Right. Since then both tools moved forward. > > > Have we done a clean build of binutils 2.16.1 and GCC > 4.0.2 with the diffs?? > No, I didn't have time. You are very welcome to have a try. Cyril > ~K > > > > > > > --- Cyril Plisko <cyril.plisko at gmail.com> wrote: > > >>Brilliant, Ken ! >> >> >> >> >>ken mays wrote: >> >>>--- Cyril Plisko <cyril.plisko at gmail.com> wrote: >>> >>> >>> >>>>ken mays wrote: >>>> >>>> >>>>>Let me know what needs to be done and I can >>>> >>>>assist. >>>> >>>>Ken, >>>> >>>>I assume you are talking about #5, right ? >>>>So - we have GCC 4.0.0 and binutils 2.16 >> >>configured >> >>>>for cross compilation (host solaris/x86, target >>>>solaris/ppc) >>>>Everything is built for 32 bit. biarch >> >>configuration >> >>>>(the single binary that can emit both 32 and 64 >>>>code) is >>>>a green field. I tried to build it, but failed. >>>>Diffs against the stock gcc and binutils releases >>>>are >>>>posted on PPC community website. >>>>I thing there are still things to be done to make >>>>the compiler >>>>more Solaris friendly - the Solaris/PPC support in >>>>it very >>>>amateur. For example, I think the cpp doesn't >> >>define >> >>>>__powerpc[__] and __ppc[__] symbols at all - >>>>something is >>>>wrong with the spec file. >>>> >>>>I believe that in the early stages we will need >>>>tweak >>>>compiler quite a lot until we'll reach some >>>>stabilization >>>>point. And this requires a dedicated maintainer. >>>> >>>>Would you like to get that task ? >>> >>> >>>Yes. I'll start start reviewing this one. >>> >>>~ Ken >>> >>> >>> >>> >>>>>~Ken M. >>>>> >>>>> >>>>>--- Cyril Plisko <cyril.plisko at gmail.com> wrote: >>>>> >>>>> >>>>> >>>>> >>>>>>Here is the current status of the source tree >>>>>>(svn://svn.genunix.org/polaris) >>>>>> >>>>>>1. The current tree is synced up with the Nevada >>>> >>>>b29 >>>> >>>> >>>>>>2. The cross compilation environment assumes >>>> >>>>Solaris >>>> >>>> >>>>>>x86 >>>>>> host and Solaris ppc target >>>>>>3. Current trunk successfully passes "make >> >>setup" >> >>>>>>which >>>>>> creates proto area for ppc arch. Which means >>>> >>>>we >>>> >>>> >>>>>>have >>>>>> a build environment (more or less) >>>>>>4. The directory structure under usr/src/uts is >>>>>>seeded >>>>>> (see /usr/src/README.ppc) >>>>>>5. The cross-toolchain published on PPC >> >>community >> >>>>>>website >>>>>> is usable, but is far from being polished. In >>>>>>fact we >>>>>> desperately need someone to take ownership of >>>>>>the >>>>>> [cross]toolchain to keep it in a good shape. >>>>> >>>>> >>>>>Let me know what needs to be done on #5 >>>>>(cross-toolchain) and I can assist. >>>>> >>>>>~Ken M. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>6. I would like to have someone to repeat my >> >>"make >> >>>>>>setup" >>>>>> build environment creation to make sure I >>>> >>>>didn't >>>> >>>> >>>>>>missed >>>>>> something critical in the process. Anyone ? >>>>>> >>>>>>Steps to get it: >>>>>> >>>>>>Prerequisites: >>>>>>1. Solaris x86 (SXCR b28 is what I have) >>>>>>2. Subversion (you can get it from Blastwave or >>>>>>compile yourself) >>>>>>3. SUNWonbld package (20051219) >>>>>>4. Cross toolchain from PowerPC community site >>>>>>(binutils + gcc) >>>>>> >>>>>>Actual steps: >>>>>>1. Create your own source tree by checking out >> >>the >> >>>>>>trunk: >>>>>> svn co svn://svn.genunix.org/polaris/trunk >>>>>>/full/path/to/workingcopy >>>>>>2. Edit polaris.sh found in the root of the >>>> >>>>working >>>> >>>> >>>>>>copy to reflect >>>>>> you path, username and mail (GATE, STAFFER, >>>>>>MAILTO) >>>>>>3. bldenv -d polaris.sh >>>>>>4. setenv BUILD64 "#" >>>>>>5. setenv GNU_ROOT /opt/polaris/powerpc-solaris2 >>>>>>6. cd usr/src >>>>>>7. make setup >>>>>>8. mail/irc me in case of problem >>>>>> >>>>>> >>>>>> >>>>>>_______________________________________________ >>>>>>blastware-discuss mailing list >>>>>>blastware-discuss at lists.blastwave.org >>>>>> >>>>> >>>>> > https://lists.blastwave.org/mailman/listinfo/blastware-discuss > >>>>> >>>>__________________________________________________ >>>> >>>>>Do You Yahoo!? >>>>>Tired of spam? Yahoo! Mail has the best spam >>>> >>>>protection around >>>> >>>> >>>>>http://mail.yahoo.com >>>>>_______________________________________________ >>>>>blastware-discuss mailing list >>>>>blastware-discuss at lists.blastwave.org >>>>> >>>> > https://lists.blastwave.org/mailman/listinfo/blastware-discuss > >>>>_______________________________________________ >>>>blastware-discuss mailing list >>>>blastware-discuss at lists.blastwave.org >>>> >>> >>> > https://lists.blastwave.org/mailman/listinfo/blastware-discuss > >>> >>> >>>__________________________________________________ >>>Do You Yahoo!? >>>Tired of spam? Yahoo! Mail has the best spam >> >>protection around >> >>>http://mail.yahoo.com >>>_______________________________________________ >>>blastware-discuss mailing list >>>blastware-discuss at lists.blastwave.org >>> >> > https://lists.blastwave.org/mailman/listinfo/blastware-discuss > >>_______________________________________________ >>blastware-discuss mailing list >>blastware-discuss at lists.blastwave.org >> > > https://lists.blastwave.org/mailman/listinfo/blastware-discuss > > === message truncated === > > > > > > __________________________________ > Yahoo! for Good - Make a difference this year. > http://brand.yahoo.com/cybergivingweek2005/ > _______________________________________________ > blastware-discuss mailing list > blastware-discuss at lists.blastwave.org > https://lists.blastwave.org/mailman/listinfo/blastware-discuss >
