Hi!
I am trying to build OOo_2.0beta2 (& src680_127) on Windows with the
latest version of cygwin (1.5.18-1), but still have no luck. I wonder
if you guys have any idea on following issues.
Yes, this is issue 51560. Solution: use a newer cygwin snapshot.
<http://cygwin.com/snapshots/>
I know that the 08/28/2005 snapshot works.

1. When hyperthreading was enabled, dmake did not start (just hung).
Without hyperthreading, it started OK but seemed to be hanging at
random module.

2. For experiment, I tried to build after having changed 'SHELL'
variable from '/usr/bin/tcsh' to '/usr/bin/sh'. It was going fine
without regarding to hyperthreading but stopped at stlport.

cp ./wntmsci10.pro/misc/build/STLport-4.5-0119/lib/*.lib ./wntmsci10.pro/lib
cp: cannot stat `./wntmsci10.pro/misc/build/STLport-4.5-0119/lib/*.lib': No such
 file or directory

It seems that 'cp' command could not expand current directory with
bash. The command was successfully ran once SHELL was changed to tcsh.

3. I searched IZ and found that issue 51560 (
http://www.openoffice.org/issues/show_bug.cgi?id=51560 ) might be
related. By upgrading cygwin1.dll with snapshot version, the minimal
test case (perlfreeze) was passed but it did not help to solve my
issue.
This should have given you the idea to try a cygwin snapshot.
If you are really interested, there was a second problem inside cygwin
1.5.18, see <http://cygwin.com/ml/cygwin/2005-08/msg01287.html>


4. I understand it is the best to solve issues with the latest version
of cygwin, if any. However, what about providing 'proven to work'
version of cygwin through tools project?

I will try to trace the problem if you let me know how to do it.
Unfortunately, I am not cygwin expert. :-)

Too late, already solved.

Volker


Regards,
Jeongkyu



--
If you like my work consider:  http://www.scytek.de/donations.html
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to