openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <dam...@apache.org>
Subject Re: University student looking for experience in contributing to the Open Office project
Date Tue, 27 Oct 2015 13:15:32 GMT
Hi Jatin

It looks like that unit test fails to compile on MacOS for some reason.
Without access to a Mac I can't tell why. You could try passing
--disable-unit-tests to ./configure to skip building unit tests, which will
also speed up your build a little, or skip only that test by editing
/Users/jatin1/repos/asf/openoffice/main/basebmp/test/makefile.mk and
changing "APP1TEST" to "disabled" (as per
https://wiki.openoffice.org/wiki/Googletest) in which case you don't have
to restart building from the beginning.

Mac currently seems to be the hardest platform to build AOO on :-(.

Good luck
Damjan


On Tue, Oct 27, 2015 at 2:57 PM, #PATHANGI JANARDHANAN JATINSHRAVAN# <
JATINSHR001@e.ntu.edu.sg> wrote:

> I have now run build --all and got an error with the module ‘basebmp’. I
> ran build —from basebmp to check the detailed error and see the following
> error:
>
> /Users/jatin1/repos/asf/openoffice/main/basebmp/test/basictest.cxx:95:5:
> error: no matching conversion for functional-style cast from
> 'PaletteMemorySharedVector' (aka 'shared_ptr<const std::vector<Color> >')
> to '::testing::AssertionResult'
>     ASSERT_TRUE( pDevice->getPalette() ) << "Palette existence";
>     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
> Can someone help me on this error?
>
> Clang version:
> Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn)
> Target: x86_64-apple-darwin14.3.0
> Thread model: posix
>
>
> Lldb version:
> lldb-330.0.48
>
>
> Thanks
>
>
>
> On 10/27/15, 6:55 AM, "Kay Schenk" <kay.schenk@gmail.com> wrote:
>
> >On Mon, Oct 26, 2015 at 7:37 AM, #PATHANGI JANARDHANAN JATINSHRAVAN# <
> >JATINSHR001@e.ntu.edu.sg> wrote:
> >
> >> As per the previous mail, I have downgraded to jdk 1.7.0_79. I ran the
> >> configure script again, after downloading the junit jar, and got the
> >> following output at the end
> >>
> >> * Apache OpenOffice 420 configuration.
> >> *
> >> *
> >> * Configuration part of Apache OpenOffice 420 build is finished.
> >> *
> >> * Note: Be aware that you might not be able to build Apache OpenOffice
> if
> >> * you ignore any warnings that were generated during this configuration
> >> * process.
> >> *
> >> * - Disabling gtk-quickstarter - not supported on Mac. Use
> >> --disable-systray
> >> * - JAVA_HOME was not explicitly informed with --with-jdk-home. the
> >> configure script
> >> * - attempted to find JAVA_HOME automatically, but apparently it failed
> >> * - in case JAVA_HOME is incorrectly set, some projects with not be
> built
> >> correctly
> >> *
> >> *
> >> * USAGE:
> >> * Source MacOSXX64Env.Set (in tcsh) or MacOSXX64Env.Set.sh (in sh)
> >> * in order to set up the build-environment variables.
> >> *
> >>
> >> I have set the JAVA_HOME environment variable correctly as per the
> >> following command:
> >>
> >>
> >> echo $JAVA_HOME
> >> /Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home
> >>
> >>
> >> This is pointing to the correct jdk home. This is output of java
> -version:
> >>
> >> java version "1.7.0_79"
> >> Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
> >> Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
> >>
> >> Why is the configure script not able to find my JAVA_HOME automatically
> >> and what can I do to make this warning go away?
> >>
> >> Thanks
> >> Jatin
> >>
> >
> >​Probably the quickest way to solve this problem is to do a configure
> again
> >(delete the existing ​
> > MacOSXX64Env.
> >​* files first), and add the the configuration option:
> >
>
> >--with-jdk-home=/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home
> >
> >I am not a Mac developer, but hopefully this will solve the problem for
> you.
> >​
> >
> >>
> >>
> >>
> >>
> >>
> >>
> >> On 10/25/15, 9:28 PM, "Andrea Pescetti" <pescetti@apache.org> wrote:
> >>
> >> >PATHANGI JANARDHANAN JATINSHRAVAN wrote:
> >> >> I downgraded to Ant 1.8.4 and still I get the same issue. It is
> greater
> >> than 1.7.0
> >> >> and 1.8.4 is sufficiently old enough at this point that I would
> expect
> >> it to work
> >> >
> >> >I confirm I can build with ant 1.9 (1.9.3, to be precise) with no
> issues.
> >> >
> >> >> so is there something else that is the problem here? My JDK is
> 1.8.0_45.
> >> >
> >> >It looks like this may be the problem. This has recently been discussed
> >> >on this list. Can you try building with Java 7?
> >> >
> >> >Note: in any case, when you have build issues the best thing to do is
> to
> >> >find your config.log file and upload it to http://pastebin.com/ (or
> any
> >> >other service) with expiration date set at one month and send the link
> >> >here. This will allow people to look at all diagnostic messages. And
> >> >this is helpful when, like in this case, the error given by configure
> is
> >> >actually not very precise.
> >> >
> >> >Regards,
> >> >   Andrea.
> >> >
> >> >---------------------------------------------------------------------
> >> >To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> >For additional commands, e-mail: dev-help@openoffice.apache.org
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>
> >
> >
> >
> >--
> >----------------------------------------------------------------------
> >MzK
> >
> >“The journey of a thousand miles begins with a single step.”
> >                                                          --Lao Tzu
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message