On 2/7/06, Noah yan <noah.yan at gmail.com> wrote:
>
>
> On 2/6/06, Cyril Plisko <cyril.plisko at gmail.com> wrote:
> > Hello !
> >
> > I want to give a brief overview of what the status of powerpc-solaris
> > support for GCC I am spending last month on.
> > Before I am going any further I want to emphasize that I am not a
> > compiler specialist, so it possible that I am overlooking or ignoring
> > something important. If you spot things like that - speak up.
> > I very much welcome it.
> >
> > Back to the toolchain. During the genunix building quest a month ago
> > it became quite evident that current cross tool chain is not adequate
> > for the job. It wasn't really a surprise for me, since I made it as
> > a quick'n'dirty solution just to see that it can be used with Solaris
> > code base in general. As long as we are simply compiling kernel modules
> > it hardly matters too much, but as soon as we're going to actually _run_
> > it on the real hardware the tool chain becomes a serious road blocker.
> Cyril,
>
> I am sure that I have no idea of the existence of such problem. And it is
> must be related to some fundentamentals of gcc that I am lack of. can you
> elaborate what the problems would be when actually _run_ those code built by
> current toolchains on the real hardware (consider me as a newbies without
> any such experience, which is true:)?
Ok. The kit we use right now configured to produce freebsd style
powerpc ELF binaries. Predefined CPP symbol list is wrong for Solaris.
crt*.o are absent. As long as the only thing we are building are .o files
for kernel most of the problems are screened, but it wouldn't work for user-land
applications. Solaris 10+ supplies its own crt?.o and the compiler needs to
take that into account.
--
Regards,
Cyril
