Hi John, thanks for the hint. The problem already happens during the built, when the make rule wants to copy a generated file into the read-only source tree. I fixed this by only copying if the the source and destination files differ, which shouldn't happen. The fix is in my Github repo. However, I immediately ran into a similar problem within the documentation's make files. I'll first need a deeper look into gtk-doc before I can fix that. Best Regards Thomas Am Montag, den 26.03.2012, 17:57 +0000 schrieb John Darrington: > On Mon, Mar 26, 2012 at 07:08:13PM +0200, Thomas Zimmermann wrote: > Hi Victor, > > first of all, thanks for your efforts. I managed to reproduce your bug, > which turns out to actually be a feature of automake. > > Running 'make distcheck' first generates source packages and afterwards > tries to build and install the sources. This runs on files and directory > with only read permissions set to see if the sources are self-contained > and to simulate builds in non-writable locations. That why you can't > write to the 'gdkglenumtypes.c.' > > I'm looking for how to best fix this. Meanwhile using 'make dist' > instead of 'make distcheck' should be a suitable workaround. > > This sounds like somebody somewhere is misusing Automake. See > http://www.gnu.org/software/automake/manual/automake.html#Hard_002dCoded-Install-Paths > for possible causes. > > > J' > _______________________________________________ > gtkglext-list mailing list > gtkglext-list gnome org > http://mail.gnome.org/mailman/listinfo/gtkglext-list -- GnuPG: http://tdz.users.sourceforge.net/tdz.asc Fingerprint: 16FF F599 82F8 E5AA 18C6 5220 D9DA D7D4 4EF1 DF08 jsapigen - A free glue-code generator for Mozilla SpiderMonkey. See http://jsapigen.sourceforge.net for more information.
Description: This is a digitally signed message part