Issue 3003 - Comment error in soffice script.
Summary: Comment error in soffice script.
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 641
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Martin Hollmichel
QA Contact: issues@framework
URL:
Keywords:
: 3039 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-02-04 23:03 UTC by siglercm
Modified: 2004-02-17 09:03 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description siglercm 2002-02-04 23:03:58 UTC 
Hi,

I searched IssueZilla but couldn't find this reported already.  I'm surprised. 
I just got around to installing 641C today and this problem cropped up.  This
happens with the Linux .tar.gz installation binary for 641C.

The Bourne shell script "soffice" that runs OpenOffice has a comment error. 
There's a C++-style comment in there, namely line 250:

   //HACK !!! MH cd into program dir

Commenting out that line with a '#' character fixes the problem.

                                    Clemmitt Sigler
Comment 1 thorsten.martens 2002-02-07 09:55:29 UTC 
TM->OBR: please have a look at this one, thanks !
Comment 2 nospam4obr 2002-02-07 11:20:25 UTC 
OBR->MH: This one is not in CVS. Did you patch it ?
Comment 3 Martin Hollmichel 2002-02-07 11:30:26 UTC 
Hi, yes this was hack to get the 641 C working before christmas ( see 
issue 2605 ). In the meantime it got fixed, so I didn't checked in 
the Hack and this will not be a problem in the next version.
Comment 4 siglercm 2002-02-07 18:05:54 UTC 
Hi Martin (and Thorsten and Oliver),

If this comment error wasn't checked in then please close this bug,
and thanks for checking on it :^)

                                   Clemmitt Sigler
Comment 5 Olaf Felka 2002-02-14 13:25:55 UTC 
*** Issue 3039 has been marked as a duplicate of this issue. ***
Comment 6 Martin Hollmichel 2002-04-19 16:09:13 UTC 
fixed in recent build.
Comment 7 Martin Hollmichel 2004-02-17 09:00:53 UTC 
verified.
Comment 8 Martin Hollmichel 2004-02-17 09:03:15 UTC 
close issue.