Issue 65276 - W32 build fails in instsetoo_native
Summary: W32 build fails in instsetoo_native
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All Windows, all
: P1 (highest) Trivial (vote)
Target Milestone: OOo 2.0.3
Assignee: rt
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-11 01:37 UTC by quetschke
Modified: 2006-05-15 10:10 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description quetschke 2006-05-11 01:37:14 UTC
m168 fails with:

ERROR: Saved logfile:
d:/w1/tin_tcsh/instsetoo_native/wntmsci10.pro/OpenOffice/msi/logging/en-US/log_SRC680__en-US.log
**************************************************
... analyzing files ...
ERROR: The following files could not be found: 
ERROR: File not found: gdiplus.dll
... cleaning the output tree ...
... removing directory /cygdrive/d/tmp/i_34161147298013 ...
Wed May 10 17:53:46 2006 (00:13 min.)

because d.lst from CWS vq31 was not integrated. vq31 was integrated in m168, but
the SRC680_m168 tag from external was not set correctly.
Comment 1 rt 2006-05-11 08:34:09 UTC
Fixed, the correct revision is tagged now.
Comment 2 quetschke 2006-05-11 15:19:23 UTC
Verified, this problem is solved.
Comment 3 rt 2006-05-11 16:38:42 UTC
closing
Comment 4 quetschke 2006-05-12 20:24:47 UTC
Please fix again. The fix didn't make it into SRC680_m169.

Somesthing is broken with the automatic tagging of external/ .
Comment 5 rt 2006-05-15 08:32:56 UTC
Fixed again.
Comment 6 pavel 2006-05-15 09:39:45 UTC
rt: d.lst is tagges, but not gdiplus directory contents.

See
http://util.openoffice.org/source/browse/util/external/gdiplus/README_gdiplus.dll

for the tags it has now - only m168 -> m169 and also m0 is missing.
Comment 7 rt 2006-05-15 10:05:34 UTC
pjanik: you're right :-(
I'd like to know what I forgot last friday so that we've got into this. No idea.
Anyway, it should be fixed now. Really. Hopefully.
Comment 8 pavel 2006-05-15 10:10:01 UTC
OK, we will see :-)