I built 5 times with -j3, but damn builds were all OK. Sorry, I have no broken build-log for you.
- Sedat - On Fri, Jan 8, 2010 at 1:16 AM, Dan Nicholson <dbn.li...@gmail.com> wrote: > On Thu, Jan 7, 2010 at 3:26 PM, Sedat Dilek <sedat.di...@googlemail.com> > wrote: >> Indeed, I discovered a failure in both cases. >> But, I always do a clean checkout (build-from-scratch) and clean/clear >> the cache of ccache. >> >> $ grep libmesagallium.a mesa/src/mesa/Makefile >> default: depend asm_subdirs glsl_builtin libmesa.a libmesagallium.a \ >> libmesagallium.a: $(MESA_GALLIUM_OBJECTS) $(GLSL_LIBS) >> driver_subdirs: libmesa.a libmesagallium.a libglapi.a >> >> In case of failure I have... >> >> $ grep libmesa build.log >> removed `mesa/src/mesa/libmesa.a' >> + PATCH=0001-Build-libmesagallium.a-before-descending-into-driver.patch >> + patch -Np1 -i >> ../patches/0001-Build-libmesagallium.a-before-descending-into-driver.patch >> mklib: Making Linux static library: libmesa.a >> ar: creating libmesa.a >> mklib: Making Linux static library: libmesagallium.a >> ar: creating libmesagallium.a >> ranlib: 'libmesagallium.a': No such file > > This seems to be the real issue. I have no idea why the file's not > actually being created. It would be nice if mklib actually stopped on > critical errors like these. Can you attach the full build log? It > might not be that illuminating, but maybe there's something else going > on. > > -- > Dan > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
