Re: [Mesa-dev] OSMesa Driver Changed With OS Update

2013-07-18 Thread Kevin H. Hobbs
On 07/17/2013 06:12 PM, Brian Paul wrote:
 On 07/17/2013 03:10 PM, Kevin H. Hobbs wrote:
 
 Can anybody give me a clue as to what's going on?
 
 My guess is your Fedora 18 system is missing some dependency that was 
 previously found on your Fedora 17 system.
 
 I'd try to compare Mesa config.log files from 17 vs. 18 to see what 
 might be different.  Or, just the output from running ./configure on each.
 

The only differences that stand out to me are:

 F17 used llvm-3.0 and F18 uses llvm-3.3.

 the LLVM_LIBS variables differed.

I don't have the make output from F17 but the F18 output has :

gmake[3]: Entering directory `/home/kevin/mesa/src/gallium/targets/osmesa'
  CC   target.lo
  GEN  libOSMesa.la
/usr/bin/ld: cannot find -lLLVMMCJIT
/usr/bin/ld: cannot find -lLLVMBitWriter
/usr/bin/ld: cannot find -lLLVMX86Disassembler
/usr/bin/ld: cannot find -lLLVMX86AsmParser
/usr/bin/ld: cannot find -lLLVMX86CodeGen
/usr/bin/ld: cannot find -lLLVMSelectionDAG
/usr/bin/ld: cannot find -lLLVMAsmPrinter
/usr/bin/ld: cannot find -lLLVMMCParser
/usr/bin/ld: cannot find -lLLVMX86Desc
/usr/bin/ld: cannot find -lLLVMX86Info
/usr/bin/ld: cannot find -lLLVMX86AsmPrinter
/usr/bin/ld: cannot find -lLLVMX86Utils
/usr/bin/ld: cannot find -lLLVMJIT
/usr/bin/ld: cannot find -lLLVMRuntimeDyld
/usr/bin/ld: cannot find -lLLVMExecutionEngine
/usr/bin/ld: cannot find -lLLVMCodeGen
/usr/bin/ld: cannot find -lLLVMObjCARCOpts
/usr/bin/ld: cannot find -lLLVMScalarOpts
/usr/bin/ld: cannot find -lLLVMInstCombine
/usr/bin/ld: cannot find -lLLVMTransformUtils
/usr/bin/ld: cannot find -lLLVMipa
/usr/bin/ld: cannot find -lLLVMAnalysis
/usr/bin/ld: cannot find -lLLVMTarget
/usr/bin/ld: cannot find -lLLVMMC
/usr/bin/ld: cannot find -lLLVMObject
/usr/bin/ld: cannot find -lLLVMCore
/usr/bin/ld: cannot find -lLLVMSupport
collect2: error: ld returned 1 exit status
gmake[3]: [libOSMesa.la] Error 1 (ignored)
/usr/bin/mkdir -p ../../../../lib;
/usr/bin/mkdir -p ../../../../lib/gallium;
ln -f .libs/libOSMesa.so ../../../../lib/gallium/libOSMesa.so;
ln: accessing ‘.libs/libOSMesa.so’: No such file or directory
gmake[3]: [all-local] Error 1 (ignored)
ln -f .libs/libOSMesa.so.8 ../../../../lib/gallium/libOSMesa.so.8;
ln: accessing ‘.libs/libOSMesa.so.8’: No such file or directory
gmake[3]: [all-local] Error 1 (ignored)
cp .libs/libOSMesa.so.8.0.0 ../../../../lib/gallium/
cp: cannot stat ‘.libs/libOSMesa.so.8.0.0’: No such file or directory
gmake[3]: [all-local] Error 1 (ignored)
gmake[3]: Leaving directory `/home/kevin/mesa/src/gallium/targets/osmesa'

I should have noticed this earlier but libOSMesa.so* exist in the
install directory so I didn't think to check until now.

In fact this output repeats for nouveau and others.

In the mesa build tree for F17 lib/gallium/ has lots of stuff but is
empty in the mesa build tree for F18.

I cannot find these libs anywhere on my system.

Everything builds if I add --with-llvm-shared-libs.

There also exists the F18 package llvm-static.x86_64 which I don't have
installed...

When I install the static libraries everything builds.




signature.asc
Description: OpenPGP digital signature
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


Re: [Mesa-dev] OSMesa Driver Changed With OS Update

2013-07-17 Thread Brian Paul

On 07/17/2013 03:10 PM, Kevin H. Hobbs wrote:

I build Mesa with OSMesa from git source for testing VTK on two hosts with:

./autogen.sh \
   --prefix=/home/kevin/mesa_nightly \
   --enable-glx \
   --enable-dri \
   --enable-shared-glapi \
   --enable-gallium-llvm \
   --with-gallium-drivers=nouveau,swrast \
   --enable-osmesa

When I used Fedora 17 OSMesa used :

GL_RENDERER: Gallium 0.4 on llvmpipe (LLVM 3.0, 128 bits)

I updated the OS on each host to Fedora 18 on different days.

After the update each host reverted to using the old OSMesa driver:

GL_RENDERER: Mesa OffScreen

I used to be able to change the driver by setting GALLIUM_DRIVER and I
can't do that anymore.

Can anybody give me a clue as to what's going on?


My guess is your Fedora 18 system is missing some dependency that was 
previously found on your Fedora 17 system.


I'd try to compare Mesa config.log files from 17 vs. 18 to see what 
might be different.  Or, just the output from running ./configure on each.


-Brian

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


Re: [Mesa-dev] OSMesa Driver Changed With OS Update

2013-07-17 Thread Kevin H. Hobbs
On 07/17/2013 06:12 PM, Brian Paul wrote:
 On 07/17/2013 03:10 PM, Kevin H. Hobbs wrote:
 
 Can anybody give me a clue as to what's going on?
 
 I'd try to compare Mesa config.log files from 17 vs. 18 to see what 
 might be different.  Or, just the output from running ./configure on each.
 

Thank you for your _very_ rapid reply!

I don't have any F17 boxes left but I pulled
/home/kevin/mesa/config.log from the backup server with only a
work day to spare before it got recycled.

I'll analyze the difference in the morning.

Thank you!





signature.asc
Description: OpenPGP digital signature
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev