Apache OpenOffice (AOO) Bugzilla – Issue 8181
config_office/set_soenv.1 ignores the current path when configuring
Last modified: 2013-08-07 15:35:14 UTC
When running configure, the set_soenv.1 script ignores the current path when creating LinuxIntelEnv.Set. This creates a problem when the required binaries are in non-standard locations. The following patch fixes that by appending the current path to the path variable that is written to LinuxIntelEnv.Set. diff -Nur oo_1.0_src.orig/config_office/set_soenv.1 oo_1.0_src/config_office/set_soenv.1 --- oo_1.0_src.orig/config_office/set_soenv.1 2002-04-17 15:41:31.000000000 -0500 +++ oo_1.0_src/config_office/set_soenv.1 2002-07-14 13:43:30.000000000 -0500 @@ -1057,6 +1059,7 @@ $ps.$USR.$BIN.$ds."X11". $ps.$USR.$ds."X11".$BIN. $ps.$USR.$LIB; + $PATH .= $oldPATH; } elsif ($platform eq "$Winnt") {
Created attachment 3100 [details] append current path to path set in LinuxIntelEnv.Set
Hi Sander, please have a look.
Any comments on this one? There has been no feedback (positive or negative) on this one ever since it was filed.
I have attached a new (and better) patch that utilizes the path set by the user properly. The patch is against OpenOffice 1.0.2 released source. The patch moves the values of the current PATH to the begining of the PATH variable thereby ensuring that the binaries in the user's path are picked up before the standard locations such as /usr/bin. I came across the problem because OpenOffice fails to compile with bison-1.875 and even though I installed bison-1.75 in /opt/bison-1.75 and added /opt/bison-1.75/bin to the front of my PATH variable, the build kept using /usr/bin/bison instead of /opt/bison-1.75/bin/bison.
Created attachment 4956 [details] Honor the user's path before using the standard system wide locations.
Ken, please have a look.
I have tested the patch and it causes no problem in LInux. Will commit with next development tree.
*** Issue 11307 has been marked as a duplicate of this issue. ***
*** Issue 12246 has been marked as a duplicate of this issue. ***
Applied to cws_srx644_ooo20030412
Please verify and close this issue.
Closing