Hi Bjarne,

For RedSleeve 7 it is like this:
CentOS 7.2 ships version 3.6.2 this builds fine, but it does not produce 
working mesa* items later on. At that time I opted to upgrade to version 3.7.1.
CentOS 7.3 ships with version 3.8.0 This version seems to not support armv5 
CPUs. I am thus stuck at version 3.7.1
There is quite a big difference between SPEC files and build methods for 3.7.1 
and 3.8 that I thought it not useful to produce patches. Best is to look at the 
3.7.1 SRPM.

That said, on RedSleeve 6 the situation is different IIRC. I remember that it 
had some gcc trouble when building, but that it worked afterwards.

let me see, I used this patch to get it working:
http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el6-staging/6.8/Redsleeve6.8/new/patches/gcc48-4.8.2-15.el6.src.rpm-mesa-private-llvm.patch
This gcc patch is different from the others that I fixed something about the 
hidden symbols.

out of curiosity, why are you building this again? This is all already online 
here:
http://www.mirrorservice.org/sites/ftp.redsleeve.org/pub/el6-staging/6.8/Redsleeve6.8/new/

Jacco



On Monday, 26 December, 2016 23:05 CET, Bjarne Saltbæk 
<[email protected]> wrote: 
 
> >* mesa-private-llvm was not able to update to the new version. I have
> >found one version that does build.
> 
> 
> Please do share your progress. I am also working on patching it on RSEL 6.8
> 
> 
> Failing at
> 
> 
> --- cut ---
> 
> g++ -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> --param=ssp-buffer-size=4 -march=armv5te -O2 -g -pipe -Wall 
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> --param=ssp-buffer-size=4 -march=armv5te -O2 -g -pipe -Wall 
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> --param=ssp-buffer-size=4 -march=armv5te -O2 -g -pipe -Wall 
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> --param=ssp-buffer-size=4 -march=armv5te -O2 -g -pipe -Wall 
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> --param=ssp-buffer-size=4 -march=armv5te -Wl,-R -Wl,'$ORIGIN' 
> -Wl,--gc-sections -rdynamic -Wl,-Bsymbolic,--default-symver 
> -L/builddir/build/BUILD/llvm-3.6.2.src/Release/lib 
> -L/builddir/build/BUILD/llvm-3.6.2.src/Release/lib     -shared -o 
> /builddir/build/BUILD/llvm-3.6.2.src/Release/lib/libLLVM-3.6-mesa.so 
> /builddir/build/BUILD/llvm-3.6.2.src/tools/llvm-shlib/Release/libllvm.o \
>            -Wl,--whole-archive -lLLVMARMAsmParser -lLLVMARMAsmPrinter 
> -lLLVMARMCodeGen -lLLVMARMDesc -lLLVMARMDisassembler -lLLVMARMInfo 
> -lLLVMAnalysis -lLLVMAsmParser -lLLVMAsmPrinter -lLLVMBitReader 
> -lLLVMBitWriter -lLLVMCodeGen -lLLVMCore -lLLVMDebugInfo 
> -lLLVMExecutionEngine -lLLVMIRReader -lLLVMInstCombine -lLLVMInstrumentation 
> -lLLVMInterpreter -lLLVMLTO -lLLVMLineEditor -lLLVMLinker -lLLVMMC 
> -lLLVMMCDisassembler -lLLVMMCJIT -lLLVMMCParser -lLLVMObjCARCOpts 
> -lLLVMObject -lLLVMOption -lLLVMProfileData -lLLVMR600AsmParser 
> -lLLVMR600AsmPrinter -lLLVMR600CodeGen -lLLVMR600Desc -lLLVMR600Info 
> -lLLVMRuntimeDyld -lLLVMScalarOpts -lLLVMSelectionDAG -lLLVMSupport 
> -lLLVMTarget -lLLVMTransformUtils -lLLVMVectorize -lLLVMipa -lLLVMipo 
> -Wl,--no-whole-archive -Wl,--soname,libLLVM-3.6-mesa.so -Wl,--no-undefined 
> -lz -lpthread -lrt -ldl -lm
> /usr/bin/ld: 
> /builddir/build/BUILD/llvm-3.6.2.src/Release/lib/libLLVM-3.6-mesa.so: hidden 
> symbol `_ZNSt13__future_base11_State_base15_M_run_deferredEv' isn't defined
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> make[1]: Leaving directory 
> `/builddir/build/BUILD/llvm-3.6.2.src/tools/llvm-shlib'
> collect2: error: ld returned 1 exit status
> make[1]: *** 
> [/builddir/build/BUILD/llvm-3.6.2.src/Release/lib/libLLVM-3.6-mesa.so] Error 1
> 
> --- cut ---
> 
> 
> I remember that I have patched a similar issue with some other 
> _ZNSt_something_something.
> 
> Something about defining them as hidden.
> 
> 
> I will find the solution in the next days where I have some spare vacation 
> time [��]
> 
> 
> Happy Holidays too.
> 
> 
> BR,
> 
> Bjarne
> 
 
 
 
 


_______________________________________________
users mailing list
[email protected]
https://lists.redsleeve.org/mailman/listinfo/users

Reply via email to