2005/12/31, Volker Quetschke <[EMAIL PROTECTED]>: > 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? > 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. > > > ===================== > > 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. > 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? > 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; 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? Once again: Thanks a lot! I get further and further. /$ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
