On 11/5/05, Martin Bochnig <mb1x at gmx.com> wrote: > ### PUBLIC e-mail to powerpc-discuss at opensolaris.org ### > ### and blastware-discuss at lists.blastwave.org ### > > > Martin Bochnig wrote: > > Cyril Plisko wrote: > > > >> On 11/5/05, Martin Bochnig <mb1x at gmx.com> wrote: > >> ... > > > > > >> You may want to start with the current set (powerpc community web page). > >> I only built it to support 32 bit. > > > > > > > > I already did so a month ago. > > But I was unable to configure/gmake/build the most trivial application > > as it was (of course) build without (target-)standard-includes (as they > > don't exist yet). > > How can it be of any (further) use(, than maybe doing most basic stuff)? > > Sorry for my dumb question. > > > > > > -- > > regards, > > martin > > Cyril, > > this time you did not respond in an instant manner.
Man, should I have some time with my family, shouldn't I :) ? > This may have any reason of course. > Nevertheless, if I remember correctly I had been asking you the same > includes-related question weeks ago and you also didn't give me an answer. > > Does this mean that I'll have to adjust the x86 or sparc includes to > meet the requirements of the MSB PowerPC ABI? > Or did I overlook something? Ok, let's see what do we know about that. There is an ABI published by SunSoft (http://opensolaris.org/os/community/power_pc/powerpc_doc_library/elfspec_ppc.pdf) it was created when Solaris was ported to PPC originally (2.5 and 2.5.1). It does not specify MSB or LSB, instead it declares that implementation must choose one. That ABI covers only 32 bit environment, since then 64 bit PPC architecture was not available. Since Sun dropped PPC that spec never evolved further. However the ABI itself is used quite extensively. When 64 bit PPC architecture arose new ABI was created (by IBM ?) (http://opensolaris.org/os/community/power_pc/powerpc_doc_library/ppc-elf64abi-1.7.1.pdf) a 32 bit ABI was used as one source of input as well as PowerOpen ABI and AIX ABI to create a new standard. Once again both MSB and LSB are legal citizens and implementation must choose which one to implement. Our [pretty obvious] choice was MSB. Now let's get back to include files. While compiling Solaris only includes from the source tree are used (at least in theory). And that is what I tried to start with - implementing those files that are absolutely must. While building the toolchain, however, these includes not necessary need to be available - binutils has its own ELF handling library (libbfd) and it already provides support for the existing PPC ABI. Since we are not trying to create an our own ABI that serves us well. That said the toolchain published on PPC community site is only good for initial kernel compilation and it (toolchain) would definitely evolve together with the progress of the port itself. Hope that clears the picture. Regards, Cyril
