Hi Ulf,
looks like you were successful in getting further through the OOo on
Solaris build.
Just a few notes:
- I can confirm that GNU patch and GNU make should be used instead of
the Solaris equivalents. I've them in /usr/local/bin which is in front
of the search path, so I tend to forget to mention them. You might also
need GNU cp and GNU tar in some cases.
- we had a former version of OOo on Solaris Sparc which was buildable
with gcc but this port hasn't been maintained for a long time. Currently
you'll need SunStudio (8, 10-12 or Sun Studio Express) to build OOo on
Solaris. The configure script hasn't been updated in a while as you
found out ... sorry for that.
- support for building jdk-1.6 has been recently added and might not
work perfectly yet. They've changed the place where some libraries live
(for instance the libmawt.so over which you stumbled). Since we need to
access these libraries directly some changes to JDKLIB and JDKLIBS
environment variables might be necessary.
- it's a wonderful thing if people try to build the stuff on the latest
OS/compiler/jdk etc releases and we do fully encourage that. Especially
if the they aren't discouraged by the need to tweak this and that to get
through. Please do file a few bugs for the problems you found, I do plan
to update the Solaris build stuff in the hopefully not so long future.
Heiner
Ulf Wendel wrote:
Hi Tora!
tora - Takamichi Akiyama schrieb:
I am afraid, but I still cannot understand why you need to avoid
using gcc on Solaris.
I got some linker errors before not related to OOo. Don't ask me about
the specific errors, I've thrown away the virtual box. As far as Google
told me it could have been because of mixing GNU ld and Sun ld.
The last time I tried OOo with GCC on OpenSolaris the configure failed [1]:
checking the GNU gcc compiler version... checked (gcc 3.4.3)
checking gcc linker... configure: error: failed (not GNU ld). Use GNU ld
instead of Sun ld on Solaris
The OOo configure script checks wheter I'm using GCC with GNU ld by
running something like this:
gcc -Wl,--version 2>&1 |head -n 1
--> /usr/ccs/bin/ld: illegal option -- version
As the default GCC did not work for me, I compiled a GCC 4.2.something
myself. That one worked better. But the FSWxorg-headers package is known
to be broken and I lacked some header files for compiling OOO [2]. After
messing around on the system, I started from scratch. When starting from
scratch I started to use Sun Studio. The Sun compilers have worked just
fine so far. The only little hassle is that the OOo configure script
nneds to be changed to accept 5.10+ [2].
Sure, OpenSolaris engineers will have had good reasons to compile GCC
the way they did (--without-gnu-ld). However, I tried the next compiler
that was around - Sun Studio - and the Sun compiles have worked flawless
to far.
Last but not least, the wiki page shows the Sun compiler and not GCC for
Solaris. If Sun compiler are good for Solaris, hey, why not try them
either on OpenSolaris but switch to GCC.
Why do you use Java 1.6? The latest software sometimes does not
work with current source codes that were firstly prepared with
several software/tools developed several years ago. For Java, I
would like to propose use of Java 1.4 or 1.5, instead, in this
moment.
Because OpenSolaris comes with 1.6. In a certain way OOo and OpenSolaris
are Sun products. Why not check if they work nicely together using
out-of-the-box installations and OpenSolaris packages...
Is the could not find jni.h problem a problem that's likely related to
1.5 vs. 1.6? I can't imagine that.
My starting point was basically on ./configure
CPPFLAGS="-I/path/to/jdk/some/path" [...] --without-java resulting into
CC -INO_JAVA_HOME/some/path. Is that because I used --without-java? If I
could tell OOo where to search for jni.h my issue might be gone.
In general, please, please, do not doubt the efforts done by
professional engineers from Solaris, Java, gcc, Ant, Apache,
Mozilla, and so on.
> How did I get there? I think I copied
> /usr/jdk/instances/jdk1.6.0/jre/lib/i386/headless/libmawt.so to
> /usr/jdk/instances/jdk1.6.0/jre/lib/i386/ , though, not sure any more.
I think that kind of modification without any deep thoughts might
I'm aware of the fact that its a hack which might cause follow-up problems.
However, given that ldd fails on a newly installed out-of-the-box
system, it smells a bit like either a buggy package or some weird VMware
side-effect. For sure no OOo issue.
be wrong. I just use appropriate versions of software and tools
and have never faced the problem that you ran into and described
in this mailing list.
What's wrong with trying to build OOo on a platform that is not on the
list of platforms used by maintainers and release engineers? Sure, its
new grounds and likely to be bloody. But why should I not try to use
OpenSolaris as a development platform.
[1]
http://www.nabble.com/[EMAIL PROTECTED]
[2] http://opensolaris.org/jive/thread.jspa?threadID=69228&tstart=120
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jens-Heiner Rechtien
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
