Re: [gentoo-amd64] openoffice 2 compiles?

Re: [gentoo-amd64] openoffice 2 compiles?

[Dmitri Pogosyan]

The claim is amd64 compilation is planned for 2.0.2

> Greetings,
> Just curious if anyone has had any success actually /compiling/ 
> openoffice 2.0 (from the portage ebuild) on an amd64 platform?
> or are people using openoffice-bin or a chroot environment?
> 
> Cheers,
> Chris
> -- 
> gentoo-amd64@gentoo.org mailing list



--
Dmitri Pogosyan            Department of Physics
Associate Professor        University of Alberta
tel 1-780-492-2150         412 Avadh Bhatia Physics Labs
fax 1-780-492-0714         Edmonton, AB, T6G 2J1, CANADA


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] openoffice 2 compiles?

[Chris Smart]

Dmitri Pogosyan wrote:

>The claim is amd64 compilation is planned for 2.0.2
>  
>
cheers, for some reason I thought you could compile it on an amd64 arch 
but not as an actual 64bit app (ie in 32bit mode using emul).
-c
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: openoffice 2 compiles?

[Duncan]

Chris Smart posted <437050B6.7000208@internode.on.net>, excerpted below, 
on Tue, 08 Nov 2005 18:16:06 +1100:

> Dmitri Pogosyan wrote:
> 
>>The claim is amd64 compilation is planned for 2.0.2
>>  
>>
> cheers, for some reason I thought you could compile it on an amd64 arch 
> but not as an actual 64bit app (ie in 32bit mode using emul).

You should be able to compile it as 32-bit, tho from what I've read it's
easier to do the 32-bit chroot and do it there than chase down whatever
32-bit stuff on 64-bit outside of a chroot.

Among other things, the java stuff is problematic, again, from what I've
read.  For both running the binary package and for compiling from source,
the Java stuff tries to use 64-bit Java, which naturally won't work trying
to link that against 32-bit OOo.  Do it in the chroot, and it can't see
anything 64-bit, so it can't link against it.  It has no choice but to go
32-bit.

Of course, the problem is that if this is your first and only 32-bit app
you really want to compile, doing an entire chroot just for it is a /lot/
of work.  In that case, even I'd probably go with the 32-bit pre-packaged
binary.

Now what might be  the /interesting/ way to do it, for those that have
several machines including some x86 machines, would be to compile it from
source on them, then try to move it over.  (As usual, be very careful
about merging 32-bit packages, binary or not, on 64-bit -- they say don't
do it at all, but if you manually verify that it's not overwriting
anything 64-bit, and manually verify dependencies, it /might/ be made to
work.  If it breaks, tho, you get to keep the pieces!)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list