Issue 71082 - W32:m191: parallel build fails in sw/util
Summary: W32:m191: parallel build fails in sw/util
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: solenv (show other issues)
Version: current
Hardware: PC Windows, all
: P2 Trivial (vote)
Target Milestone: OOo 2.2
Assignee: quetschke
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-01 18:08 UTC by quetschke
Modified: 2006-11-12 02:38 UTC (History)
1 user (show)

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

Attachments
Logfile (3.54 MB, patch)
2006-11-01 18:10 UTC, quetschke 		no flags Details | Diff
Testing this ... (3.02 KB, patch)
2006-11-04 15:35 UTC, quetschke 		no flags Details | Diff
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 quetschke 2006-11-01 18:08:53 UTC 
The build fails with the following attached log.
Comment 1 quetschke 2006-11-01 18:10:13 UTC 
Created attachment 40230 [details]
Logfile
Comment 2 hjs 2006-11-02 18:25:49 UTC 
i'm currently left to guessing.

according to the log, sw680mi.dll was already built, which in this case creates
the IMPLIB _sw.lib. also $(SHL1TARGETN) is specified as a dependency of the
failing dll. so it looks like a collision of the SHL1IMPLIB target, which in
this case simply is a dummy and the SHL3TARGET.
there may be two ways to get around this:
- either add $(LB)$/$(SHL1IMPLIB) to SHL3DEPN for windows only. should
workaround the problem with local changes only but doesn't solver the
underlaying issue
- remove the TOUCH command in [_]tg_shl.mk, SHLnIMPLIBTARGETN, USE_DEFFILE!=""
case. solves the race and might be obsolete in current builds.
Comment 3 quetschke 2006-11-04 15:35:08 UTC 
Created attachment 40321 [details]
Testing this ...
Comment 4 quetschke 2006-11-05 14:13:33 UTC 
Seems to work. I tested the patch on top of CWS vq39 (clean checkout) and the
build finished without problems.

I guess it's to late to get vq39 into m192, shall I resync vq39 to m192, commit
this and fix the new missing pch includes?
Comment 5 hjs 2006-11-06 12:21:07 UTC 
m192 is already done and i just approved vq39. how about ause071 (just preparing
for the final build)?
Comment 6 quetschke 2006-11-06 13:58:26 UTC 
Sure, just committ it.
Comment 7 hjs 2006-11-07 17:25:59 UTC 
committed
Comment 8 hjs 2006-11-07 17:27:28 UTC 
please verify
Comment 9 quetschke 2006-11-07 19:58:55 UTC 
ause071 build without problems using `build.pl -- -P2` on a machine that otherwise
(nearly) always triggered that problem. -> VERIFIED
Comment 10 quetschke 2006-11-12 02:38:05 UTC 
Seen on master