Hi Tora!
tora - Takamichi Akiyama schrieb:
Hi Ulf,
Ulf Wendel wrote:
The last time I tried OOo with GCC on OpenSolaris the configure failed
[1]:
> [1]
http://www.nabble.com/[EMAIL PROTECTED]
> 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
Hmm, why don't you tweak a PATH environment variable for the ./configure?
Setting PATH with /opt/SUNWspro/bin followed by /usr/sfw/bin like this
export
PATH=/opt/SUNWspro/bin:/usr/sfw/bin:/usr/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/local/bin
would bring you a better result.
checking for gcc... /opt/SUNWspro/bin/cc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
^ ^ ^ ^ ^ ^ ^ ^ ^ ^
Is there a misunderstanding in our discussion? I am using the Sun
compilers, for example, Sun Ceres C 5.10 SunOS_i386 2008/04/04. Its
working fine!
Before I tried the Sun compilers, I have tried GCC. I was using the gcc
from the OpenSolaris SUNWgcc package. That did not work very well for
the reasons explained earlier.
Also, (Jens-)Heiner (Rectien) replied that some OOo code might expect
you to use SunStudio on OpenSolaris/Solaris and not GCC. My conclusion
is that I better keep my fingers away from GCC on OpenSolaris for the
beginning.
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.
You might have heard that changing version of Java is problematic.
Some Java applications might become not to work after updating Java.
I do not refer to jni.h, but that is a general story.
Sure, ... I'm close to giving up and consider to install 1.5. Did you
see the comments from Heiner regarding 1.6 - there's a small chance to
get it working with 1.6.
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.
Maybe no. You would also need to specify by means of something where
jni.h relevant .so files are. Otherwise, you would face another problem
at linking stage or running stage even though compilation would have
become succeeded. .h and .so files are a set of files.
Yes, that's exactly what I see happening now :-( . Why ":-("? Because
there is no OpenSolaris Java 1.5 package for the lazy guys. Ok, no big
deal I hope, but...
What i normally do is building a specific module, not building entire OOo.
For example,
1. Obtain source files of DEV300_mXX
2. Prepare build environment
3. cd sw; build.pl --all
4. cd sw; make some modifications in the existing source files
5. cd sw; build.pl debug=1
6. Install DEV300_mXX released by the release engineer of OOo.
7. Replace libswsi.so in the installation directory with the built one.
8. Start OOo.
9. Attach a debugger to the process of soffice.bin
So, I carefully try to avoid any compilation errors which are not related
to the module in which I am interested. Additionally I try to tweak my
build environment to meet the one used by the RE as much as i can.
That's definetly worth posting again and again on the ML for those who
want to start with OOo! I might be better off doing exactly the same.
But meanwhile I got a thick-headed and want to get everything to compile
on OpenSolaris.
Thanks!
Ulf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
