To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=51560
                  Issue #:|51560
                  Summary:|Build with cygwin 1.5.18 fails in instsetoo_native
                Component:|tools
                  Version:|680m113
                 Platform:|All
                      URL:|
               OS/Version:|Windows, all
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|code
              Assigned to:|vq
              Reported by:|vq





------- Additional comments from [EMAIL PROTECTED] Mon Jul  4 15:52:50 -0700 
2005 -------
The W32-tcsh build fails in instsetoo_native with:

... generating setup.ini ...
... copying files into installation set ...
... creating ddf files ...
... creating log file log_SRC680__en-US.log 
... packaging installation set ... 
... makecab.exe (1) ...
(-- nothing, build hangs --)

The following attachment is a standalone testcase, unfortunately it depends on
the absolute path it resides in. To reproduce unpack perlfreeze.zip to d: then
do:
$ cd /cygdrive/d/perlfreeze
$ ./perltest.pl

and see it hang. (In cygwin bash, without OOo build environment set.)

P.S.: Using cygwin 1.5.17 works around this problem.

P.P.S: If you cannot unpack to d: choose a diffrent location and change
openofficeorg_q4.ddf accordingly.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to