История изменений
Исправление NK, (текущая версия) :
Разрулил ситуацию с ошибкой, на irc #libreoffice-dev действительно подсказали в чем, а именно в ключах
you have CFLAGS/CXXFLAGS containing -fomit-frame-pointer, and it looks like LO's precautions to override that in places where that's not OK like in bridges/Library_gcc3_linux_intel.mk don't work, as our -fno-omit-frame-pointer ends up in front of your -fomit-frame-pointer on the compiler's command line, so likely has no effect
don't assume that LO is such a trivial program that you can outsmart it with compiler settings
happens to negatively impact the bridges/source/cpp_uno code only on x86, not x86_64
у меня просто в ключах компилятора вот такая штука была
-O2 -march=i686 -mtune=i686 -fomit-frame-pointer -fPIC
Задал, как alien задает
http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/libreoffice/build/...
i486) SLKCFLAGS="-march=i486 -mtune=i686"
SLKLDFLAGS=""; LIBDIRSUFFIX=""
;;
x86_64) SLKCFLAGS="-fPIC"
SLKLDFLAGS="-L/usr/lib64"; LIBDIRSUFFIX="64"
;;
- все собралось
Исходная версия NK, :
Разрулил ситуацию с ошибкой, на irc #libreoffice-dev действительно подсказали в чем, а именно в ключах
you have CFLAGS/CXXFLAGS containing -fomit-frame-pointer, and it looks like LO's precautions to override that in places where that's not OK like in bridges/Library_gcc3_linux_intel.mk don't work, as our -fno-omit-frame-pointer ends up in front of your -fomit-frame-pointer on the compiler's command line, so likely has no effect
don't assume that LO is such a trivial program that you can outsmart it with compiler settings
happens to negatively impact the bridges/source/cpp_uno code only on x86, not x86_64
у меня просто в ключах компилятора вот такая штука была -fomit-frame-pointer
Задал, как alien задает
http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/libreoffice/build/...
i486) SLKCFLAGS="-march=i486 -mtune=i686"
SLKLDFLAGS=""; LIBDIRSUFFIX=""
;;
x86_64) SLKCFLAGS="-fPIC"
SLKLDFLAGS="-L/usr/lib64"; LIBDIRSUFFIX="64"
;;
- все собралось