Yeah, I had a deeper look into the build-log:
/bin/bash ../../bin/mklib -o glapi -static main/dispatch.o
glapi/glapi.o glapi/glapi_getproc.o glapi/glthread.o x86/glapi_x86.o
mklib: Making Linux static library: libglapi.a
ar: creating libglapi.a
mklib: Making Linux static library: libmesa.a
ar: creating libmesa.a
mklib: Making Linux static library: libmesagallium.a
ar: creating libmesagallium.a
ar: sl_pp_context.o: No such file or directory
ranlib: 'libmesagallium.a': No such file
NOTE: ar: sl_pp_context.o: No such file or directory
$ grep sl_pp_context.o -r mesa/ | egrep 'libmesa|libglsl'
Binary file mesa/src/glsl/pp/libglslpp.a matches
Binary file mesa/src/mesa/libmesa.a matches
Binary file mesa/src/mesa/libmesagallium.a matches
Seems to me something wrong with GLSL_LIBS.
In comparison the "normal" build.log (here we see the "order/sequence"
libmesa.a libmesagallium.a libglapi.a):
$ grep ^mklib build.log
mklib: Making Linux shared library: libGL.so.1.2
mklib: Installing libGL.so.1.2 libGL.so.1 libGL.so in ../../../lib
mklib: Making Linux static library: libglslpp.a
mklib: Making Linux static library: libglslcl.a
mklib: Making Linux static library: libmesa.a
mklib: Making Linux static library: libmesagallium.a
mklib: Making Linux static library: libglapi.a
mklib: Making Linux static library: libr300compiler.a
mklib: Making Linux shared library: r300_dri.so
mklib: Making Linux shared library: swrast_dri.so
...
Hmm, should we try to change here build-deps sequence?
[src/mesa/Makefile]
...
# Default: build dependencies, then asm_subdirs, GLSL built-in lib,
# then convenience libs (.a) and finally the device drivers:
default: depend asm_subdirs glsl_builtin libmesa.a libmesagallium.a \
libglapi.a driver_subdirs
...
Any ideas?
- 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
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
