Benjamin wrote:
some files are generated automaticaly during the build process, i guess you have overwritten the ones that ship with the source-distribution
(in this case gmarshal.c and cmarshal.h). one soulution might be to uncomment the related lines in glib/gobject/makefile.xxx and copy the files
from the source-distribution again
the same happens with other files. HINT: search all makefiles for perl and comment out the lines that are intend to generate any code (again: the files
that are generated do allready exist).
You were partially correct. My gmarshal.h and gmarshal.c were overwritten, but they're not generated by perl scripts.
<snip>
I'm surprised no one has jumped in here and told me how wrong I was about how exactly gmarshal.h, etc. are generated :) I got some similar problems running 'make check' so I decided to take a closer look.
gobject/glib-genmarshal is a wrapper script that calls gobject/.libs/glib-genmarshal.exe, setting up the correct environment, etc. gobject/glib-genmarshal.exe is a wrapper executable that calls gobject/glib-genmarshal; the wrapper exe calls the wrapper script that calls the actual exe. This is all set up by libtool.
Cygwin calls the wrapper executable just fine, but something is wrong with the wrapper. In fact I don't think any of the wrapper exes are working correctly. Each wrapper throws this warning on compilation:
creating glib-genmarshal.exe
.libs/lt-glib-genmarshal.c: In function `main':
.libs/lt-glib-genmarshal.c:79: warning: passing arg 2 of `execv' from incompatible pointer type
When the wrapper exe is run, it emits no output and returns an exit
value of 0, silently failing. Running the wrapper script directly works fine, so the problem must be with the wrapper exe.
Since this appears to be a problem with libtool, I won't bother the folks here with more emails about this. This message is for completeness/historical purposes :)
Jeff _______________________________________________ gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
