>>Just to make sure. It were not the missing instmsia.exe and instmsiw.exe >>that let the build fail, there are important libraries missing. configure >>is not checking if these libraries are present and therefore it will not >>complain. But you are welcome to find workarounds. > > configure reported this until i found some instmsia.exe and > instmsiw.exe to use (and exitied): > checking for instmsia.exe/instmsiw.exe... configure: error: > instmsia.exe and/or instmsiw.exe are/is missing in the default > location. > These programs are part of the .NET installation and should be found in a > directory similar to: > "c:\Program Files\Microsoft Visual Studio .NET > 2003\Common7\Tools\Deployment\MsiRedist\" > As the automatic detection fails please copy the files to external/msi/. > > Are there more libraries that I need from a full studio installation? > That are not checked by configure? Yes, see: <http://www.openoffice.org/issues/show_bug.cgi?id=32040> and dependent issues.
>>You can always look at: >><http://go-ooo.org/tinderbox/all_trees.express.html> >>for successfull builds and compare the buildlogs. > > I would really like to look there, I just don't understand where to > click to see the logs. It is very good to know what is considered > normal. Click on the m147 link <http://go-oo.org/tinderbox/SRC680_m147/status.html>, scroll down to "12/29 05:21" and click the "L" (you need javascript), then choose "View Summary Log". Or just click here: <http://go-oo.org/tinderbox/gunzip.cgi?tree=SRC680_m147&brief-log=1135851779.23614> >>>===================== >>>Problem 3: dmake hangs >>>===================== >>>How can I get further? >> >>Debug the problem. It doesn't help much to say that it works for me, it does >>;) . >>I currently use >> >>$ uname -a > > I was trying to locate such command. Standard unix command ;) >>Can you find out what is hanging? (ps and task manager might be your friend.) > > I believe it is sed. > >>Does >> >>$ ls /proc/*/fd >> >>help to "cure" the hang? If yes, you are member of an elite club. ;) > > Yes! And ps shows sed every time dmake hangs (and not otherwise), is > there a possibility to use another implementation of sed? Which? > Is the problem inside cygwin1.dll, not in sed? Most propably it's cygwin. Please try the 24.12. snapshot. (Reboot even if it's not needed.) I just started a build with the 29.12. snapshot. >>Is the hang reproducable? You don't have to build everything, just: >>$ cd extras ; rm -rf wntmsci10.pro ; build > > I don't think it stops on exactly the same place every time. But dmake > does not run many seconds between the stops now (cured by ls > /proc/*/fd every time). > > I don't know much about bash/tcsh, can you tell me how to write and > run a loop like (ada-style): > loop > "ls /proc/*/fd"; > delay 5.0; > end loop; I don't speak tcsh very well, but in bash it's: $ while true; do ls /proc/*/fd; sleep 5; done > Is ctrl-c placing commands in the background, or killing them? > If just placing them in the background - how do I kill a running command? ctrl-c should stop. Read about ctrl-z and bg about putting something in the background. ps gives you a list of running processes and kill <PID> should kill it. On cygwin you might want to try ps -W to get also a list of windows processes. And kill -9 <PID> might help you if kill doesn't work. Errm, and kill is a bash/tcsh command. There is also a program. Look at /bin/kill --help to learn about some more drastic methods ;) Volker -- 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
