Re: [dev] Re: Needed patches for building on PPC?
Hi,
I have an even better solution:
How about somebody there (a debian developer) who understands the ppc
linux sys v abi well and who knows something about virtual method tables
and exception handling changes from gcc 2.95.4 to gcc 3.1 takes a shot at
writing this and contributing it to the port (or someone who wants to
learn all of these things!)
(i.e. create a gcc3_linux_powerpc directory using the abi pieces from
gcc2_linux_powerpc and examining what changed from gcc2_linux_x86 to
gcc3_linux_x86 and incorporating those changes for ppc linux) to allow
support for gcc 3.X by the time it is released.
That would certainly be a big help to me and the ppc linux port in
general. In fact, I would love to have some long-term official help from
Debian ppc developers to help support the ppc Linux port itself.
What do you say? Is there anyone there who wants to step up to the plate
and begin to help out on the bridges code and eventually even take over
(or at least become co-maintainer of the ppc Linux port?).
Any qualified developer would be welcomed! I think this is one of the
those projects that the distributions themselves should take an active
hand in (there is no StarOffice for ppc Linux, only OpenOffice) and I
would welcome the help since I am being stretched a bit thin.
Thanks,
Kevin
On April 19, 2002 07:35, Kevin B. Hendricks wrote:
> Hi,
>
> Yes, the solution is to NOT use gcc 3.X under ppc Linux.
>
> Compilers are not interchangeable in the OOo build. There is in fact
> compiler specific bridge code that has to be written to handle virtual
> methods and the new way exceptions are handled in gcc 3.X (the gcc 3.x
> abi is incompatible with gcc 2.95.X).
>
> So the short answer is stick with gcc 2.95.4 with ppc linux.
>
> The long answer is I will rewrite the bridges code once gcc 3.1 is
> officially released and Franz Sirl puts his completed version up there
> (which he has tested and incorporated all of his fixes).
>
> I won't use anyone else's tool chain since Franz is the only one I know
> contributing consistently to gcc development for ppc linux.
>
> Then I will write the new bridges code and create a gcc3_ directory with
> it.
>
> Sorry about that, but IMHO, gcc 3.0.X are simply not ready for use under
> ppc Linux for heavy C++ development.
>
> Thanks,
>
> Kevin
>
> On April 19, 2002 04:12, you wrote:
> > Hi all ...
> >
> > I wanted to build OpenOffice.org again on Linux, debian-unstable, with
> > (I know I should not do it) gcc3.
> >
> > I tried to compile and had to drop the -nostdinc cflag in the
> > unxlgppc.mak.
> > To compile oo_src/bridges/source/cpp_uno/gcc2_linux_ppc I got some
> > errors with undeclared variables, because, I compile with gcc3. For
> > example, this:
> >
> > /home/palic/OpenOffice/debian/openoffice.org-0.641d.cvs20020418/build-
> >tr
> > ee/oo_stable1_cvs20020418_src/bridges/source/cpp_uno/gcc2_linux_powerp
> >c/u no2cpp.cxx: In
> > function `Void gcc3::callVirtualMethod(void*, long int, void*,
> > _typelib_TypeClass, char*, sal_Int32*, long int, uno_Any**,
> > uno_Mapping*)':
> > /home/palic/OpenOffice/debian/openoffice.org-0.641d.cvs20020418/build-
> >tr
> > ee/oo_stable1_cvs20020418_src/bridges/source/cpp_uno/gcc2_linux_powerp
> >c/u no2cpp.cxx:309: ^_cp_eh_info'
> > undeclared (first use this function) ....
> >
> > but _cp_eh_info is declared in the gcc2_linux_ppc.hxx, but I think,
> > dmake does not recognize it.
> >
> > Are there any work to fix it? Are there patches, which can be tested?
> >
> > Kevin, do you have something for me? :)))
> >
> > Regards
> > Jan
> > PS: I attached the whole errormessages.....
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.org
> For additional commands, e-mail: dev-help@openoffice.org
--
To UNSUBSCRIBE, email to debian-openoffice-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: