Re: [dev] Compile error: external/common/apache-ant[...] not found @ OpenSolaris snv 95
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]
Re: [dev] Compile error: external/common/apache-ant[...] not found @ OpenSolaris snv 95
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 checking whether /opt/SUNWspro/bin/cc accepts -g... yes checking for /opt/SUNWspro/bin/cc option to accept ISO C89... none needed 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. 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. The simplest way to instantly specify both at once is to use --with-jdk-home=, i think. For instance, --with-jdk-home=/usr/j2se brings the following settings: $ grep j2se SolarisX86Env.Set.sh JAVA_HOME="/usr/j2se" JAVAINTERPRETER="/usr/j2se/bin/java" JAVACOMPILER="/usr/j2se/bin/javac" JAVADOC="/usr/j2se/bin/javadoc" $ grep JAVA_HOME solenv/inc/*.mk solenv/inc/ant.mk:JAVA_HOME=$(JDK14PATH) solenv/inc/ant.mk:CLASSPATH!:=$(CLASSPATH)$(PATH_SEPERATOR)$(ANT_CLASSPATH)$(PATH_SEPERATOR)$(JAVA_HOME)$/lib$/tools.jar solenv/inc/antsettings.mk:JAVA_HOME= solenv/inc/antsettings.mk:.EXPORT : JAVA_HOME solenv/inc/libs.mk:AWTLIB*=$(JAVA_HOME)$/lib$/jawt.lib solenv/inc/target.mk:.IF "$(JAVALOCATION)"!="$(JAVA_HOME)" solenv/inc/target.mk:.ELSE # "$(JAVALOCATION)"!="$(JAVA_HOME)" solenv/inc/target.mk:.ENDIF # "$(JAVALOCATION)"!="$(JAVA_HOME)" solenv/inc/target.mk: @echo JAVALOCATION:=$(JAVA_HOME) >> $@ solenv/inc/tg_javav.mk:.IF "$(JAVAVER)"=="" || "$(JAVALOCATION)"!="$(JAVA_HOME)" solenv/inc/tg_javav.mk:JAVAVER:=$(shell @-$(JAVA_HOME)$/bin$/java $(JFLAGSVERSION_CMD)) solenv/inc/tg_javav.mk:JAVANUMVER:=$(shell @-$(JAVA_HOME)$/bin$/java $(JFLAGSNUMVERSION_CMD)) solenv/inc/tg_javav.mk:.ENDIF # "$(JAVAVER)"=="" || "$(JAVALOCATION)"!="$(JAVA_HOME)" 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. Now I understand what you want to do. Thank you for the comments. I admire your challenges. My interest is different from yours. It is to find a cause of bug, to try to fix a bug, to confirm a fix done by developers or myself, to make a mock-up for proposing enhancement, to provide my customers with a binary patch .so files, and so on. 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. Best, Tora - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Starting more than one OO instance parallel
Hi Bastian, On Wed, Aug 20, 2008 at 12:02 PM, Bastian Preindl <[EMAIL PROTECTED]> wrote: > > Is there a possibility to start more than one soffice.bin process at a time > on both MacOS and Linux? At the moment a second soffice.bin process > immediately quits after startup if an instance is already running. Start OOo with a dedicated user-configuration directory: soffice -env:UserInstallation=file://home/user/ooouserdirectory ciao Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] missing menu and toolbars on Opensuse 11 x86_64
Hi, I have build OOO300_m2 on Opensuse 11 64 bit and after the installation of all the rpm packages I can start OOo but for some reasons the menu and the toolbars are not shown. Very strange is, that on the first screen, where I can select the type of document I want, the menu is shown. But once I selected Text Document the menu is gone! Same if I start swriter directly, no menu and toolbars. The same source build on Opensuse 11 with 32 bits works fine. Has someone seen this before? Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Compile error: external/common/apache-ant[...] not found @ OpenSolaris snv 95
Hi Ulf, Ulf Wendel wrote: Moin Heiner! Jens-Heiner Rechtien schrieb: - 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. Its likely that GCC works fine on OpenSolaris and x86. Its just that you might not want to use the OpenSolaris SUNWgcc package but compile GCC yourself. I'll try GCC once I get OOo to build with the Sun compilers. Building OOo on Solaris with gcc is a bit more involved than it might seem on the first glance. GCC itself is a fine compiler and works great on Solaris but there are a few assumptions in the OOo code that assume that on Solaris SunStudio is used for building. Especially the bridge needs to be adapted for each compiler/platform combination, because it requires intimate knowledge about object layout, calling conventions and the throwing and catching of exceptions. The bridge glues the generic UNO API to the (mostly) C++ based OOo implementation. Parts of it are implemented in assembler. - 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. Maybe not perfect but, for example, hsql compiles just fine with the defaultOpenSolaris Java 1.6 packages. That's pretty cool. JDKLIB, JDKLIBS ... aha... I'll try to find a human Java-FAQ to navigate me through the 1.6 waters... These are environment variables which are set in the SolarisEnv.sh script generated by the configure process, so they are specific to OOo. 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. Will do once I've fiddled out some instructions for building on OpenSolaris x86. I'm doing a lot of try & error at the moment. Ulf PS: SuSE 11 - all fine on x86, x86_64 as long as you stay away from non-Sun Java. Heiner -- Jens-Heiner Rechtien [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] break iteration
Hi Jens, On Wednesday, 2008-08-20 08:42:07 +0200, Thomas Lange wrote: > > we want to implement break iteration for Khmer in OpenOffice. We created a > > patch for ICU to implement a dictionary base breakiterator and so far this > > seems to work for line breaking. Are you sure ICU will need modifications for that? For Japanese and Chinese we already have dictionary based breakiterators, see source in i18npool/source/breakiterator/, especially breakiterator_cjk.cxx; probably similar can be added to breakiterator_ctl.cxx or be built upon. > > Unfortunately it is not working for word breaking. :-( > > > > From the code in OOo we got the impression that for word breaking always > > rule > > based iterators are used. > > > > Has anyone experience in this field and can tell us what we need to do in > > order to use an iterator from ICU for word breaking? > > Please contact Karl Hong (Karl Hong <[EMAIL PROTECTED]>) he implemented > the breakiterator in i18npool and is probably the most familiar with the > ICU. Instead of descending into private communication I'd like to invite Jens to the [EMAIL PROTECTED] mailing list instead, where Karl also is present. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Use [EMAIL PROTECTED] Thanks. pgp2sRdTLz3n5.pgp Description: PGP signature
Re: [dev] tabs
Hi Rigo I think you thought about this: http://wiki.services.openoffice.org/wiki/Framework/WorkInProgress/Tabbed_Windows_Extension kind regards Michael Cziebalski Rigo Santana wrote: have you guys ever thought about adding tabs? so you can have multiple documents open in the same window? kinda like firefox Rigoberto Santana [EMAIL PROTECTED] EMAILING FOR THE GREATER GOOD Join me - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] tabs
have you guys ever thought about adding tabs? so you can have multiple documents open in the same window? kinda like firefox Rigoberto Santana [EMAIL PROTECTED] EMAILING FOR THE GREATER GOOD Join me
Re: [dev] Compile error: external/common/apache-ant[...] not found @ OpenSolaris snv 95
Hi Ulf, On Tuesday, 2008-08-19 13:29:32 +0200, Ulf Wendel wrote: > David Tardon schrieb: >> If through CVS, it's possible you haven't got everything needed. Look >> into external/common if there is apache-ant-1.7.0 subdirectory there. If >> not, checkout it and repeat the build. > > I have used CVS. There seems to be no directory external/common in my > CWS. Which is correct, a 'common' subdirectory would be a build output directory for multi-platform builds, there should not be any code checked in. Also Ant should not be part of the OOo source tree. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Use [EMAIL PROTECTED] Thanks. pgp0wtmv2sV4a.pgp Description: PGP signature
Re: [dev] Compile error: external/common/apache-ant[...] not found @ OpenSolaris snv 95
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/[EMA
Re: [dev] Compile error: external/common/apache-ant[...] not found @ OpenSolaris snv 95
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]
Re: [dev] Compile error: external/common/apache-ant[...] not found @ OpenSolaris snv 95
Hi Ulf, I am afraid, but I still cannot understand why you need to avoid using gcc on Solaris. 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. 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 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. I would like to recommend to respect the information at [1] and thoroughly read information written by professionals, hackers, and experienced engineers, available at tools.openoffice.org, wiki of OpenOffice.org, and other sources before stating the battle. [1] http://wiki.services.openoffice.org/wiki/Compiler_versions_used_by_port_maintainers_and_release_engineers Best, Tora - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Starting more than one OO instance parallel
Hi, I've been forwarded from the community fora with my question to ask it in this mailing list, so I'm hopefully not OT: Is there a possibility to start more than one soffice.bin process at a time on both MacOS and Linux? At the moment a second soffice.bin process immediately quits after startup if an instance is already running. Reason is that I currently implement a native Java OO process pool for operating in headless mode and I need the ability to start several OO processes in parallel. Thank you very much in advance Bastian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Compile error: external/common/apache-ant[...] not found @ OpenSolaris snv 95
tora - Takamichi Akiyama schrieb: export CC=/usr/sfw/bin/gcc Please tell me about this one! I am still trying to compile it with the Sun compilers. I don't trust the GCC that comes with OpenSolaris. Its build against Sun ld and Sun ar. That caused some pain. It's just for compilation of Perl modules. I see. Compiling Perl modules worked fine with Sun's compiler in my case. I don't even have GCC installed on my current snv 95 (vmware) OOo build machine. The gcc bundled in OpenSolaris seems to use /usr/sbin/pkgchk -v SUNWgcc 2>&1 | grep /usr/sfw/bin/ /usr/sfw/bin/gcc /usr/sbin/pkgchk -l -p /usr/sfw/bin/gld ... SUNWbinutils ... /usr/sbin/pkgchk -v SUNWbinutils 2>&1 | grep /usr/sfw/bin/ /usr/sfw/bin/gar ... for GNU ar ... /usr/sfw/bin/gld ... for GNU ld ... man -M /usr/sfw/man gld NAME ld - Using LD, the GNU linker Look at the PATH above again, /usr/sfw/bin is prior to /usr/ccs/bin /usr/ccs/bin/ld /usr/ccs/bin/ar I have set up a new Vmware box. I used the OpenSolaris snv 95 iso image to install the virtual machine. After the installation of the image on the disk I did not have a GCC installed. I installed GCC using pfexec pkg install SUNWgcc: -bash-3.2$ pfexec pkg list SUNWgcc NAME (AUTHORITY) VERSION STATE UFIX SUNWgcc 3.4.3-0.95 installed You can check the configure settings of GCC using gcc -V. It will show that GCC has been compiled with --with-ld=/usr/ccs/bin/ld and --without-gnu-ld: -bash-3.2$ gcc -v Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.11/3.4.3/specs Configured with: /builds2/sfwnv-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++,f77,objc --enable-shared Thread model: posix gcc version 3.4.3 (csl-sol210-3_4-20050802) /usr/ccs/bin/ld -V gives me Solaris Link Editors: 5.11-1.1614 . Note the mixture of GNU as and SUN ld. I had some fun with that before on another virtual machine. (Yes, I love creating VMs, messing them up and throwing them away.) The fun got solved by compiling GCC 4.2.1 . My current issue is on jni.h. I'm trying to pass additional CPPFLAGS but maybe its just about this --without-java vs. --with-jdk-home. Why don't you simply use Java? Any problem with Java? That's from the above mentioned newly created virtual machine: -bash-3.2$ ldd /usr/jdk/instances/jdk1.6.0/jre/lib/i386/libjawt.so libmawt.so =>(file not found) libjava.so => /usr/jdk/instances/jdk1.6.0/jre/lib/i386/libjava.so [...] I've posted it earlier on opensolaris-help@ [1] - no hints to far. How did I get OOo to compile on the other virtual machine? This is how it reads on my OOo OpenSolaris snv 95 build box created from the same OpenSolaris ISO image: [EMAIL PROTECTED]:~/oo.org-m28$ ldd /usr/jdk/instances/jdk1.6.0/jre/lib/i386/libjawt.so libmawt.so => /usr/jdk/instances/jdk1.6.0/jre/lib/i386/libmawt.so libjava.so => [...] 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. Ulf [1] http://opensolaris.org/jive/thread.jspa?threadID=69545&tstart=30 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Could not open include file "jni.h". @ OOo 3.0 M28 @ OpenSolaris svn 95
tora - Takamichi Akiyama schrieb: Ulf Wendel wrote: > after solving my little ant issue I ran into "could not open jni.h". How about use of --with-jdk-home=/usr/j2se or like that? find /usr/j* -name jni.h /usr/j2se/include/jni.h /usr/jdk/instances/jdk1.5.0/include/jni.h /usr/jdk/instances/jdk1.6.0/include/jni.h I do use --with-jdk-home = ... CC=cc CXX=CC ./configure CPPFLAGS="-I/usr/jdk/latest/include/ -I/usr/jdk/latest/include/solaris" --disable-build-mozilla --disable-mediawiki --with-use-shell=bash --with-jdk-home=/usr/jdk/latest/ --with-system-curl --without-java --with-epm=internal --with-system-libxml --with-system-python --with-ant-home=/usr/bin ... and both jni.h and jni_md.h (a follow-up requirement) are available in /usr/jdk/latest/. /usr/jdk/latest is a softlink pointing to the latest installed version of the JDK: -bash-3.2$ ls -la /usr/jdk/latest/include/jni.h -rw-r--r-- 1 root bin67831 Aug 15 20:31 /usr/jdk/latest/include/jni.h -bash-3.2$ ls -la /usr/jdk/latest/include/solaris/jni_md.h -rw-r--r-- 1 root bin 453 Aug 15 20:31 /usr/jdk/latest/include/solaris/jni_md.h Its OK that I might have to set additional CPPFLAGS. I'd be fine if it would work. Using the OpenSolaris Java packages, which is my intention, I'll find jni.h in: -bash-3.2$ pfexec pkg search -r jni.h INDEX ACTIONVALUE PACKAGE [...] basename file usr/jdk/instances/jdk1.6.0/include/jni.h pkg:/[EMAIL PROTECTED] -bash-3.2$ locate jni.h /export/home/nixnutz/oo.org-m28/moz/unxsoli4.pro/inc/java/jni.h /export/home/nixnutz/oo.org-m28/solver/300/unxsoli4.pro/inc/mozilla/java/jni.h /usr/include/firefox/java/jni.h /usr/jdk/instances/jdk1.6.0/include/jni.h Christian asked me earier why I am using --with-jdk-home together with --without-java. Several modules look out for jni.h. I was hoping that --without-java means no need for a JDK but that seems to be a false assumption. Only way out of the issue which I found so far is copying the required JDK include header into the module directories, but of course that's no solution. Ulf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
