Possible change to the "Native Build" page?

Phil Hart <philhart -AT- iinet.net.au>
Tue, 19 Jun 2012 06:06:29 +0800

Hello.

I have found (and solved) an annoyance when it comes to native build onopenSUSE 12.1 . It is this: openSUSE 12.1 ships with Java 1.5, but thecurrent version of LibreOffice needs Java 1.6.

This can be resolved by installing Java-1_6_0-openjdk-devel before the./autogen.sh step.

Should this be documented inhttp://wiki.documentfoundation.org/Development/Native_Build ? Should italso be put into http://www.libreoffice.org/developers-2/ ?

If so, is it something that I should do? (As a newbie to this forum, Iwondered if I should leave it to more experienced people.)


Regards,
philhart

Context

Possible change to the "Native Build" page? · Phil Hart
- Re: Possible change to the "Native Build" page? · Caolán McNamara
  - Re: Possible change to the "Native Build" page? · Phil Hart
    - Re: Possible change to the "Native Build" page? · Caolán McNamara
      - Re: Possible change to the "Native Build" page? · Phil Hart
        
        Re: Possible change to the "Native Build" page? · Noel Grandin
        
        Re: Possible change to the "Native Build" page? · Phil Hart
        
        Re: Possible change to the "Native Build" page? · Miklos Vajna
        Re: Possible change to the "Native Build" page? · Phil Hart
        
        Re: Possible change to the "Native Build" page? · Phil Hart
        Re: Possible change to the "Native Build" page? · Jan Holesovsky

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.