It appears that make may also be touching the output files during parallel builds, probably as some kind of locking or synchronization mechanism. So the actual compilation phase was finding existing files of size zero, which eet was treating as an invalid file.
On Nov 30, 2007 2:25 PM, Sebastian Dransfeld <[EMAIL PROTECTED]> wrote: > Nathan Ingersoll wrote: > > You're probably right that a dep could fix the build failure, but it > > would be better if we could determine why edje_cc is failing and fix > > that. These really are independent directories with no shared files, > > especially on the output. > > Doesn't make just check whether the outfile exists? So if edje_cc > creates the out file at the beginning of the compile, make will only try > to make the file once? > > Sebastian > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
