On Mon, 2007-04-30 at 07:07 -0600, Pueblo Native wrote:

Are you downloading it, or installing it as a RPM? The latter should eliminate any of those problems.

I put it in as part of my clean install of the system, from the OpenSUSE install DVD.. I did try installing it as an RPM from OpenOffice directly, but I'm not sure if it installed correctly; certainly it gave the same error afterwards. (I can try again!) Gavin -- Dr Gavin Tabor Lecturer, School of Engineering, Computer Science and Mathematics, University of Exeter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Mandag 30 april 2007 15:35 skrev Gavin Chester:

On Mon, 2007-04-30 at 07:07 -0600, Pueblo Native wrote:

...

Are you downloading it, or installing it as a RPM? The latter should eliminate any of those problems.

Can't go wrong with that advice, but the only thing I would add is to switch to 'smart' for package management. Once you add the useful set of repositories it leaves yast for dead and will 'smartly' resolve and dependency issue like you saw with OO.o If unsure, google for 'smart' on suse.

Gavin

Wait a sec., the binary programname for OO is NOT oofice, rather it's soffice! - what have you been installing? -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 2007-04-30 at 20:54 +0200, Verner Kjærsgaard wrote:

Mandag 30 april 2007 15:35 skrev Gavin Chester:

...

On Mon, 2007-04-30 at 07:07 -0600, Pueblo Native wrote:

...

Are you downloading it, or installing it as a RPM? The latter should eliminate any of those problems.

Can't go wrong with that advice, but the only thing I would add is to switch to 'smart' for package management. Once you add the useful set of repositories it leaves yast for dead and will 'smartly' resolve and dependency issue like you saw with OO.o If unsure, google for 'smart' on suse.

Gavin

Wait a sec., the binary programname for OO is NOT oofice, rather it's soffice! - what have you been installing?

-- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard

No ; ooffice seems to start OpenOffice. Soffice generates the same error (but does not even get as far as the introductory banner). I wondered if one was an alias for the other, but they seem to be different executables. I'm confused.... although this might account for the fact that when I reinstalled OpenOffice from RPM's, nothing seemed to change. Gavin -- Dr Gavin Tabor Lecturer, School of Engineering, Computer Science and Mathematics, University of Exeter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, 2007-05-01 at 11:59 +0200, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Tuesday 2007-05-01 at 10:42 +0100, Dr Gavin Tabor wrote:

...

No ; ooffice seems to start OpenOffice. Soffice generates the same error (but does not even get as far as the introductory banner).

Have you investigated yet about that OpenFOAM I told you?

Sorry - I must have missed your original message.

The problem is not OOo, but "OpenFOAM". What is that? It doesn't come from openSuSE 10.2. Investigate that program, it is requesting the gcc compiler to build something, and that's not the business of OOo.

OpenFOAM is an open source CFD (computational fluid dynamics) code I use. I really can't see that it should be involved in this anywhere. However it does occur to me that its installation involves installing a version of gcc, and it may be that ooffice is getting confused about libraries somewhere along the line. Does that sound reasonable? Gavin

- -- Cheers, Carlos E. R.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76

iD8DBQFGNw+YtTMYHG2NR9URAjQtAJoDik+YKT1qsPBm9eN/CKtWpPwPHwCghQm9 vNseyV5TO9XUz+Ga8TKyeW8= =VIrt -----END PGP SIGNATURE-----

-- Dr Gavin Tabor Lecturer, School of Engineering, Computer Science and Mathematics, University of Exeter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2007-05-01 at 11:58 +0100, Dr Gavin Tabor wrote:

...

Have you investigated yet about that OpenFOAM I told you?

| Sorry - I must have missed your original message. Notice the error message?

ooffice /usr/lib/ooo-2.0/program/javaldx: /opt/foam/OpenFOAM/linux/gcc-3.4.3/lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libstdc++.so.6)

javaldx was complaining about a gcc component in OpenFOAM.

Problem sorted. OpenFOAM includes initialisation of a variable LD_LIBRARY_PATH which was pointing to the wrong gcc libraries (for OpenOffice, that is). I have edited the ooffice script to unset this variable temporarily so as to be able to run ooffice without it getting confused.

I knew there was something wrong with it, but not what it was exactly. You should instead set that variable only for those programs related to that OpenFOAM thing, and leave the rest of the system intact - or you will hit more problems related to it. It is bad for a program to set that variable globally and f*k the system. I would report that as a bug to OpenFOAM folks. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGNyYytTMYHG2NR9URAuYaAJ9rYwWBtFP0n5HxXRshzrfs43oXBQCgjxJm MgHWyNmxQbi6HS5DxDTUCjI= =jYAQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org