Willy Sudiarto Raharjo wrote:
expected. Currently i'm using 6.00.0366 (perhaps this is because i
installed VS 2003 SP 1). Can anybody send the 6.00.0361 version that
comes with VS 2003 to get this works?
I fixed this by copying Midl.exe from SDK/bin and it works but now it
If i were you, i would try to investigate the reason why 6.00.0366 is
rejected by what and then modify the cause. I would never overwrite
version 6.00.0366 of Midl.exe with different version of Midl.exe.
Midl.exe, Microsoft (R) 32b/64b MIDL Compiler Version 6.00.0361, must
be accompanied with other relevant set of files. Replacing only .exe
instead of replacing a set of entire files might break its function
and make the command unstable. Consequently, the final fruits of build
process could not be reliable.
stucked on mozilla compilation. Here's the error log
/mozilla/directory/c-sdk/ldap/build'
cd include; /usr/bin/make export
make[4]: Entering directory `/home/har2d2/OOH680_m17/moz/wntmsci10.pro/misc/bui
d/mozilla/directory/c-sdk/ldap/include'
Makefile:74: *** target pattern contains no `%'. Stop.
How about earching keywords "cygwin make target pattern contains no `%'"
in the Internet?
Downgrading version of 'make' embedded in Cygwin might be a easiest
solution.
Many people instantly believe that the latest version of tools are the
best choice. In reality, the latest ones often bring us difficulties.
Christian Lohmaier wrote:
> The only times when the build did just hang without any progress was
> when I was using tcsh (on Mac, not Windows) - I never had that problem
> with bash. Not sure whether it helps in your case...
I also have the similar experience with another software.
'tcsh' has to invoke '/bin/sh' for shell scripts written in sh shell script.
'sh' seems to have a problem around file redirection and it occasionally
freezes. But i am not sure if this is the case.
From that experience, i had to migrate from tcsh to bash. And now,
I have become to prefer bash to tcsh. I have never used tcsh for years.
For your build environment
I would like to recommend to use 'bash' instead of 'tcsh.'
configure --with-use-shell=bash ...
cd ..
source winenv.set.sh or . winenv.set.sh
For logging error messages
>> $ (date; time build.pl -- PRODUCT=full ; date ) 2>&1 | tee build_`date
+%Y%m%d_%H%M`.log
That, '2>&1,' works on bash, not tcsh.
That logs both standard output and standard error output
Willy Sudiarto Raharjo wrote:
> I modified the above command into (date; time build.pl -- PRODUCT=full; date)
> build-error
I am afraid, but that does not work expectedly. That solely logs
standard output. We want to log both standard output and standard
error output at the same time.
I mean you seemed to expect '> build-error.'
That, however, works as '> build-log-of-normal-output-except-error'
If you want to keep using 'tcsh,' use '>&' instead of '>', which
will log both standard output and standard error output.
Willy Sudiarto Raharjo wrote:
> Finally i CTRL+C the process and restart again and it just works
> it happens on several dmake --PRODUCT=full
> so everytime i see no CPU utilization and it's on dmake, i stopped and
> restart the process again
That is not good.
Nobody can assure your build has no problem.
e.g. possible scenario:
1. dmake invokes a command.
2. the command create a file.
3. the command freezes for some reasons.
4. you kill the command with CTRL+C.
the file exists, but its content is partially broken.
5. dmake, again.
dmake recognizes the file exists and judges there is no
need to repeatedly run the command.
6. In fact, the file has been created, but its content is broken.
7. the file will be packed into the installer of OpenOffice.org.
8. a user will be surprised to find strange behavior of OpenOffice.org.
Please fix the problem first and throw the folder wntmsci10.pro of
the the problematic project to the garbage can and re-build the project.
I hope that help.
Tora
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
