[gentoo-amd64] OpenOffice.org natively available for AMD64

[gentoo-amd64] OpenOffice.org natively available for AMD64

[Simon Stelling]

Hi all,

It finally happened: openoffice is expected to compile and work natively 
  on amd64. In fact, I have just removed the package.mask entry. 
Versions starting from 2.0.4 should work and are therefore marked 
testing on amd64 (i.e. there still might be problems - please file bugs 
if you find any). That also means that you no longer need to run a 
multilib profile just because you need openoffice.

Many thanks go to Jon Severinsson who provided us with patches and did a 
lot of testing!

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 developer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Sebastian Redl]

Simon Stelling wrote:
> Hi all,
>
> It finally happened: openoffice is expected to compile and work
> natively  on amd64. In fact, I have just removed the package.mask
> entry. Versions starting from 2.0.4 should work and are therefore
> marked testing on amd64 (i.e. there still might be problems - please
> file bugs if you find any). That also means that you no longer need to
> run a multilib profile just because you need openoffice.
That's fantastic news! I'll wait a few hours for the mirrors to
propagate the change, then I'll try it out. One more piece of nice
64-bit software for me. :-)

Sebastian Redl
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Lorenzo Milesi]

> It finally happened: openoffice is expected to compile and work natively
>   on amd64. In fact, I have just removed the package.mask entry.
> Versions starting from 2.0.4 should work and are therefore marked
> testing on amd64 (i.e. there still might be problems - please file bugs
> if you find any). That also means that you no longer need to run a
> multilib profile just because you need openoffice.

I had seen it this morning, and I though "What?!" :)

Which are the real advantages in compiling OOo instead of using -bin?
Except the multilib thing?
I've heard of aging compilation times... :)

thanks
maxxer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 687 bytes --]

On Monday 16 October 2006 06:30, Simon Stelling <blubb@gentoo.org> wrote 
about '[gentoo-amd64] OpenOffice.org natively available for AMD64':
> It finally happened: openoffice is expected to compile and work natively
>   on amd64.

Woot!

Of course, I've been using KOffice when I needed an office suite and it 
does everything I need.

> Many thanks go to Jon Severinsson who provided us with patches and did a
> lot of testing!

Mine included.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On Monday 16 October 2006 08:03, "Lorenzo Milesi" 
<lorenzo.milesi@gmail.com> wrote about 'Re: [gentoo-amd64] OpenOffice.org 
natively available for AMD64':
> > It finally happened: openoffice is expected to compile and work
> > natively on amd64.
> I had seen it this morning, and I though "What?!" :)
> Which are the real advantages in compiling OOo instead of using -bin?

Well, it certainly looks and feels different when compiled with the kde 
useflag, or at least did on my x86 laptop.

Also, the version I compiled on my memory-starved 2.4GHz P4 laptop started 
5-10 times faster then the binary version installed on my 2.2GHz 4GB RAM 
2x Dual-core Opteron monster.

OOo-bin sucked so much on AMD64 (for me, it's subjective) that I loved it 
when KOffice finally became usable for me.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Michael Weyershäuser]

Lorenzo Milesi wrote:
>
> Which are the real advantages in compiling OOo instead of using -bin?
> Except the multilib thing?
> I've heard of aging compilation times... :)

7h here on a 3200+, so yes, this is an ebuild to start before going to
bed :)
>
> thanks
> maxxer

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Christoph Mende]

On Mon, 2006-10-16 at 15:03 +0200, Lorenzo Milesi wrote:
> I've heard of aging compilation times... :)

Well, it's getting better, this is with -j1 (forced by ebuild, didn't
set WANT_MP) on my Athlon64 3000+:

     Sat Oct 14 08:01:44 2006 >>> app-office/openoffice-2.0.4
     merge time: 4 hours, 49 minutes and 49 seconds.

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Juergen Schinker]

Am Mo, 16.10.2006, 12:30, schrieb Simon Stelling:
> Hi all,
>
> It finally happened: openoffice is expected to compile and work natively
>   on amd64. In fact, I have just removed the package.mask entry.
> Versions starting from 2.0.4 should work and are therefore marked
> testing on amd64 (i.e. there still might be problems - please file bugs
> if you find any). That also means that you no longer need to run a
> multilib profile just because you need openoffice.

Yeah thanks it needed me ca 3h to compile and now it runs like
a dream (it starts in 2s)...
another package on native 64bit...
but what about grub?

Juergen
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Felipe Ribeiro]

I've had problems compiling openoffice, here is the trace


register component
'file:///var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest/../../unxlngx6.pro/class/testComponent.jar'
in registry '../../unxlngx6.pro/lib/uno_services.rdb' failed!
error (RuntimeException): JNI exception occurred
dmake:  Error code 1, while making '../../unxlngx6.pro/lib/uno_services.rdb'
dmake:  '../../unxlngx6.pro/lib/uno_services.rdb' removed.
'---* tg_merge.mk *---'

ERROR: Error 65280 occurred while making
/var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest
make: *** [stamp/build] Error 1

!!! ERROR: app-office/openoffice-2.0.4 failed.
Call stack:
  ebuild.sh, line 1564:   Called dyn_compile
  ebuild.sh, line 937:   Called src_compile
  openoffice-2.0.4.ebuild, line 271:   Called die

!!! Build failed
!!! If you need support, post the topmost build error, and the call
stack if relevant.

!!! When you file a bug report, please include the following information:
GENTOO_VM=sun-jdk-1.5  CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.08"
JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""



On 10/16/06, Christoph Mende <ch.mende@googlemail.com> wrote:
> On Mon, 2006-10-16 at 15:03 +0200, Lorenzo Milesi wrote:
> > I've heard of aging compilation times... :)
>
> Well, it's getting better, this is with -j1 (forced by ebuild, didn't
> set WANT_MP) on my Athlon64 3000+:
>
>      Sat Oct 14 08:01:44 2006 >>> app-office/openoffice-2.0.4
>      merge time: 4 hours, 49 minutes and 49 seconds.
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Jean-Marc Hengen]

Hello,

Felipe Ribeiro wrote:
> I've had problems compiling openoffice, here is the trace
> 
> 
> register component
> 'file:///var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest/../../unxlngx6.pro/class/testComponent.jar' 
> 
> in registry '../../unxlngx6.pro/lib/uno_services.rdb' failed!
> error (RuntimeException): JNI exception occurred
> dmake:  Error code 1, while making 
> '../../unxlngx6.pro/lib/uno_services.rdb'
> dmake:  '../../unxlngx6.pro/lib/uno_services.rdb' removed.
> '---* tg_merge.mk *---'
> 
> ERROR: Error 65280 occurred while making
> /var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest 
> 
> make: *** [stamp/build] Error 1
> 
> !!! ERROR: app-office/openoffice-2.0.4 failed.
> Call stack:
>  ebuild.sh, line 1564:   Called dyn_compile
>  ebuild.sh, line 937:   Called src_compile
>  openoffice-2.0.4.ebuild, line 271:   Called die
> 
> !!! Build failed
> !!! If you need support, post the topmost build error, and the call
> stack if relevant.
> 
> !!! When you file a bug report, please include the following information:
> GENTOO_VM=sun-jdk-1.5  CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.08"
> JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""

Seems to be a problem, with sun-jdk-1.5, see 
http://bugs.gentoo.org/show_bug.cgi?id=151225

Use blackdown-jdk-1.4 and it should work (at least for me).

Greetings,
Jean-Marc
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Vladimir G. Ivanovic]

On Wed, 2006-10-18 at 20:14 +0200, Jean-Marc Hengen wrote:
> Seems to be a problem, with sun-jdk-1.5, see 
> http://bugs.gentoo.org/show_bug.cgi?id=151225
> 
> Use blackdown-jdk-1.4 and it should work (at least for me).
        
Using the blackdown compiler did not work for me.

        ...
        cd ../../unxlngx6.pro/lib &&  regcomp -register -br
        uno_types.rdb -r uno_services.rdb\
                -c acceptor.uno.so \
                -c bridgefac.uno.so \
                -c connector.uno.so \
                -c remotebridge.uno.so \
                -c uuresolver.uno.so \
                -c bridgetest.uno.so \
                -c cppobj.uno.so \
                -c uriproc.uno.so \
                -c constructors.uno.so
        register component 'acceptor.uno.so' in registry
        'uno_services.rdb' succesful!
        register component 'bridgefac.uno.so' in registry
        'uno_services.rdb' succesful!
        register component 'connector.uno.so' in registry
        'uno_services.rdb' succesful!
        register component 'remotebridge.uno.so' in registry
        'uno_services.rdb' succesful!
        register component 'uuresolver.uno.so' in registry
        'uno_services.rdb' succesful!
        register component 'bridgetest.uno.so' in registry
        'uno_services.rdb' succesful!
        register component 'cppobj.uno.so' in registry
        'uno_services.rdb' succesful!
        register component 'uriproc.uno.so' in registry
        'uno_services.rdb' succesful!
        register component 'constructors.uno.so' in registry
        'uno_services.rdb' succesful!
        regcomp -register -br ../../unxlngx6.pro/lib/uno_types.rdb
        -r ../../unxlngx6.pro/lib/uno_services.rdb \
                -c javaloader.uno.so -c javavm.uno.so
        register component 'javaloader.uno.so' in registry
        '../../unxlngx6.pro/lib/uno_services.rdb' succesful!
        register component 'javavm.uno.so' in registry
        '../../unxlngx6.pro/lib/uno_services.rdb' succesful!
        regcomp -register
        -br ../../unxlngx6.pro/misc/bridgetest/bootstrap.rdb
        -r ../../unxlngx6.pro/lib/uno_services.rdb -c \
        
        file:///var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest/../../unxlngx6.pro/class/testComponent.jar \
        
        -env:URE_INTERNAL_JAVA_DIR=file:///var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/solver/680/unxlngx6.pro/bin
        using loader com.sun.star.loader.Java2
        register component
        'file:///var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest/../../unxlngx6.pro/class/testComponent.jar' in registry '../../unxlngx6.pro/lib/uno_services.rdb' failed!
        error (RuntimeException): JNI exception occurred
        dmake:  Error code 1, while making
        '../../unxlngx6.pro/lib/uno_services.rdb'
        dmake:  '../../unxlngx6.pro/lib/uno_services.rdb' removed.
        '---* tg_merge.mk *---'
        
        ERROR: Error 65280 occurred while
        making /var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest
        make: *** [stamp/build] Error 1
        
        !!! ERROR: app-office/openoffice-2.0.4 failed.
        Call stack:
          ebuild.sh, line 1568:   Called dyn_compile
          ebuild.sh, line 937:   Called src_compile
          openoffice-2.0.4.ebuild, line 271:   Called die
        
        !!! Build failed
        !!! If you need support, post the topmost build error, and the
        call stack if relevant.
        
        !!! When you file a bug report, please include the following
        information:
        GENTOO_VM=sun-jdk-1.5  CLASSPATH=""
        JAVA_HOME="/opt/sun-jdk-1.5.0.08"
        JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""
        and of course, the output of emerge --info
        
        # eselect java-vm list
        Available Java Virtual Machines:
          [1]   blackdown-jdk-1.4.2  system-vm
          [2]   emul-linux-x86-java-1.4.2 
          [3]   emul-linux-x86-java-1.5 
          [4]   sun-jdk-1.5 

--- Vladimir

        -- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Gary E. Miller]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yo Vladimir!

On Wed, 18 Oct 2006, Vladimir G. Ivanovic wrote:

> Using the blackdown compiler did not work for me.

I uninstalled sun-java, installed blackdown-jdk, and OO compiled for
me.  Surely there is a better way, but it worked for me.  Native OO is
amazing.  Instead of the tedious startup of the binary it just goes BANG
and it is up.  Amazing.

>         GENTOO_VM=sun-jdk-1.5  CLASSPATH=""
                    ^^^^^^^^^^^

Looks to me like you are still using the sun-jdk.

RGDS
GARY
- ---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Ave., Suite E-3, Bend, OR 97701
	gem@rellim.com  Tel:+1(541)382-8588

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFNu/N8KZibdeR3qURAs8oAKDxZ6qAKnMIecnNKFzSSnLxYkNApACdHlZB
XHBujmPOSYqyCcu349b1hD8=
=hErX
-----END PGP SIGNATURE-----

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Vladimir G. Ivanovic]

Correction. 

I was still using the Sun compiler. It seem that setting 'eselect
java-vm set system 1' does not change the Java compiler that is used
during emerges. I ended up doing:

        # env GENTOO_VM="blackdown-jdk-1.4.2" CLASSPATH="" \
        JAVA_HOME="/opt/blackdown-jdk-1.4.2.03" emerge openoffice

Hopefully, this will do the trick.

--- Vladimir

On Wed, 2006-10-18 at 20:08 -0700, Vladimir G. Ivanovic wrote:
> On Wed, 2006-10-18 at 20:14 +0200, Jean-Marc Hengen wrote:
> > Seems to be a problem, with sun-jdk-1.5, see 
> > http://bugs.gentoo.org/show_bug.cgi?id=151225
> > 
> > Use blackdown-jdk-1.4 and it should work (at least for me).
>         
> Using the blackdown compiler did not work for me.
> 
>         ...
>         cd ../../unxlngx6.pro/lib &&  regcomp -register -br
>         uno_types.rdb -r uno_services.rdb\
>                 -c acceptor.uno.so \
>                 -c bridgefac.uno.so \
>                 -c connector.uno.so \
>                 -c remotebridge.uno.so \
>                 -c uuresolver.uno.so \
>                 -c bridgetest.uno.so \
>                 -c cppobj.uno.so \
>                 -c uriproc.uno.so \
>                 -c constructors.uno.so
>         register component 'acceptor.uno.so' in registry
>         'uno_services.rdb' succesful!
>         register component 'bridgefac.uno.so' in registry
>         'uno_services.rdb' succesful!
>         register component 'connector.uno.so' in registry
>         'uno_services.rdb' succesful!
>         register component 'remotebridge.uno.so' in registry
>         'uno_services.rdb' succesful!
>         register component 'uuresolver.uno.so' in registry
>         'uno_services.rdb' succesful!
>         register component 'bridgetest.uno.so' in registry
>         'uno_services.rdb' succesful!
>         register component 'cppobj.uno.so' in registry
>         'uno_services.rdb' succesful!
>         register component 'uriproc.uno.so' in registry
>         'uno_services.rdb' succesful!
>         register component 'constructors.uno.so' in registry
>         'uno_services.rdb' succesful!
>         regcomp -register -br ../../unxlngx6.pro/lib/uno_types.rdb
>         -r ../../unxlngx6.pro/lib/uno_services.rdb \
>                 -c javaloader.uno.so -c javavm.uno.so
>         register component 'javaloader.uno.so' in registry
>         '../../unxlngx6.pro/lib/uno_services.rdb' succesful!
>         register component 'javavm.uno.so' in registry
>         '../../unxlngx6.pro/lib/uno_services.rdb' succesful!
>         regcomp -register
>         -br ../../unxlngx6.pro/misc/bridgetest/bootstrap.rdb
>         -r ../../unxlngx6.pro/lib/uno_services.rdb -c \
>         
>         file:///var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest/../../unxlngx6.pro/class/testComponent.jar \
>         
>         -env:URE_INTERNAL_JAVA_DIR=file:///var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/solver/680/unxlngx6.pro/bin
>         using loader com.sun.star.loader.Java2
>         register component
>         'file:///var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest/../../unxlngx6.pro/class/testComponent.jar' in registry '../../unxlngx6.pro/lib/uno_services.rdb' failed!
>         error (RuntimeException): JNI exception occurred
>         dmake:  Error code 1, while making
>         '../../unxlngx6.pro/lib/uno_services.rdb'
>         dmake:  '../../unxlngx6.pro/lib/uno_services.rdb' removed.
>         '---* tg_merge.mk *---'
>         
>         ERROR: Error 65280 occurred while
>         making /var/tmp/portage/app-office/openoffice-2.0.4/work/ooo/build/OOO_2_0_4/testtools/source/bridgetest
>         make: *** [stamp/build] Error 1
>         
>         !!! ERROR: app-office/openoffice-2.0.4 failed.
>         Call stack:
>           ebuild.sh, line 1568:   Called dyn_compile
>           ebuild.sh, line 937:   Called src_compile
>           openoffice-2.0.4.ebuild, line 271:   Called die
>         
>         !!! Build failed
>         !!! If you need support, post the topmost build error, and the
>         call stack if relevant.
>         
>         !!! When you file a bug report, please include the following
>         information:
>         GENTOO_VM=sun-jdk-1.5  CLASSPATH=""
>         JAVA_HOME="/opt/sun-jdk-1.5.0.08"
>         JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""
>         and of course, the output of emerge --info
>         
>         # eselect java-vm list
>         Available Java Virtual Machines:
>           [1]   blackdown-jdk-1.4.2  system-vm
>           [2]   emul-linux-x86-java-1.4.2 
>           [3]   emul-linux-x86-java-1.5 
>           [4]   sun-jdk-1.5 
> 
> --- Vladimir
> 
>         -- 
> Vladimir G. Ivanovic <vgivanovic@comcast.net>
> 
-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Vladimir G. Ivanovic]

Yo Gary, Dude! ;-)

You're right. I was still using the Sun compiler. See my reply to myself
that I just posted.

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Neil Cathey]

Vladimir G. Ivanovic wrote:
> Correction. 
> 
> I was still using the Sun compiler. It seem that setting 'eselect
> java-vm set system 1' does not change the Java compiler that is used
> during emerges. I ended up doing:
> 
>         # env GENTOO_VM="blackdown-jdk-1.4.2" CLASSPATH="" \
>         JAVA_HOME="/opt/blackdown-jdk-1.4.2.03" emerge openoffice
> 
> Hopefully, this will do the trick.
> 
> --- Vladimir
> 

Comment #43 from Bug #151255 lists a workaround:

JAVA_PKG_FORCE=blackdown-jdk-1.4.2 emerge openoffice

It seems that something (Portage?) will automatically select the newest JDK.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Neil Cathey]

Neil Cathey wrote:
> Vladimir G. Ivanovic wrote:
>> Correction.
>> I was still using the Sun compiler. It seem that setting 'eselect
>> java-vm set system 1' does not change the Java compiler that is used
>> during emerges. I ended up doing:
>>
>>         # env GENTOO_VM="blackdown-jdk-1.4.2" CLASSPATH="" \
>>         JAVA_HOME="/opt/blackdown-jdk-1.4.2.03" emerge openoffice
>>
>> Hopefully, this will do the trick.
>>
>> --- Vladimir
>>
> 
> Comment #43 from Bug #151255 lists a workaround:
> 
> JAVA_PKG_FORCE=blackdown-jdk-1.4.2 emerge openoffice
> 
> It seems that something (Portage?) will automatically select the newest 
> JDK.

Correction:

JAVA_PKG_FORCE_VM=blackdown-jdk-1.4.2 emerge openoffice

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Vladimir G. Ivanovic]

> JAVA_PKG_FORCE_VM=blackdown-jdk-1.4.2 emerge openoffice

Thanksn for this tidbit, but I unfortunately saw your email too late: I
had to remove the Sun packages (and emerge openoffice for the third
time!)

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Neil Cathey]

Vladimir G. Ivanovic wrote:
>> JAVA_PKG_FORCE_VM=blackdown-jdk-1.4.2 emerge openoffice
> 
> Thanksn for this tidbit, but I unfortunately saw your email too late: I
> had to remove the Sun packages (and emerge openoffice for the third
> time!)
> 
> --- Vladimir
> 
Don't thank me, Jon Severinsson gave the workaround in Bug #140728.  I 
used that command and got openoffice-2.0.4 to compile just last night - 
and I have sun-jdk-1.5 installed.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] OpenOffice.org natively available for AMD64

[Peter Humphrey]

On Monday 16 October 2006 11:30, Simon Stelling wrote:

> It finally happened: openoffice is expected to compile and work natively
> on amd64.

Is there any way to install it without dbus? I run vmware-server and 
vmware-server-console, which really dislike dbus at the moment.

-- 
Rgds
Peter
-- 
gentoo-amd64@gentoo.org mailing list