Issue 117350 - DEV300_m102: MINGWSTRIP hackery broke configure
Summary: DEV300_m102: MINGWSTRIP hackery broke configure
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: configure (show other issues)
Version: DEV300m101
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: pavel
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-12 10:43 UTC by pavel
Modified: 2017-05-20 10:34 UTC (History)
2 users (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 pavel 2011-03-12 10:43:09 UTC 
Hi,

DEV300_m102 configure fails with:

checking whether to build the ODK... ./configure: line 20453: syntax error near unexpected token `('
./configure: line 20453: `    case `(uname -sr) 2>/dev/null` in'

Reverting this change helped:

http://hg.services.openoffice.org/DEV300/raw-diff/2af012206726/configure.in

I see several issues there:

1. intermixed MINGSTRIP and MINGWSTRIP (which doesn;t cause an error here, but well, sounds strange)

2. the second hunk is line broken which causes an error.

Please master fix this.
Comment 1 pavel 2011-03-12 10:45:15 UTC 
ups. Vladimir, not Volker.
Comment 2 mst.ooo 2011-03-31 16:50:35 UTC 

*** This issue has been marked as a duplicate of issue 117269 ***
Comment 3 mst.ooo 2011-03-31 16:55:03 UTC 
oops, too fast :(
bogus line break is fixed but:
the MINGWSTRIP vs MINGSTRIP problem still exists in m104;
should not cause much problems, so can be fixed on a CWS...
Comment 4 mst.ooo 2011-04-04 10:33:17 UTC 
fixed in CWS gnumake4
http://hg.services.openoffice.org/hg/cws/gnumake4/rev/82fc045a63a6
Comment 5 mst.ooo 2011-04-04 10:33:54 UTC 
please verify
Comment 6 pavel 2011-04-04 10:42:24 UTC 
Seen one added letter in http://hg.services.openoffice.org/hg/cws/gnumake4/rev/82fc045a63a6
Comment 7 Oliver-Rainer Wittmann 2012-06-13 12:29:00 UTC 
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.