On Mon, Nov 8, 2010 at 2:09 PM, Thiago Macieira
<email address hidden> wrote:
> Em Segunda-feira 08 Novembro 2010, às 16:50:52, você escreveu:
>> testing the packages from ricardos PPA on a non NEON architecture
>> results in a SIGILL again :(
>
> Can you post a backtrace? It would be useful if the build used -fno-inline, or
> this will get a bit tricky to track down.
>
> Please also verify that Qt did detect that Neon is absent. Run libQtCore.so.4
> and paste the last line of the output. E.g.:
>
> # /usr/lib/libQtCore.so.4
> This is the QtCore library version 4.7.1
> Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).
> Contact: Nokia Corporation (<email address hidden>)
>
> Build key: armv6 linux g++-4 full-config
> Compat build key: |
> Build date: 2010-11-04
> Installation prefix: /usr
> Library path: /usr/lib
> Include path: /usr/include/qt4
> Processor features: neon
>
> If it says "neon" is present (like above), then it looks like there was a
> detection mistake. Can you try turning the feature off by setting
> QT_NO_CPU_FEATURE=neon and running the app again?
4.7, the one used by Maverick doesn't export the processor features line.
Best thing would be to get the proper trace from the sigill.
> Finally, it would be nice also to have the command-line of the compiler used
> when compiling the actual .cpp file.
On Mon, Nov 8, 2010 at 2:09 PM, Thiago Macieira libQtCore. so.4 FEATURE= neon and running the app again?
<email address hidden> wrote:
> Em Segunda-feira 08 Novembro 2010, às 16:50:52, você escreveu:
>> testing the packages from ricardos PPA on a non NEON architecture
>> results in a SIGILL again :(
>
> Can you post a backtrace? It would be useful if the build used -fno-inline, or
> this will get a bit tricky to track down.
>
> Please also verify that Qt did detect that Neon is absent. Run libQtCore.so.4
> and paste the last line of the output. E.g.:
>
> # /usr/lib/
> This is the QtCore library version 4.7.1
> Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).
> Contact: Nokia Corporation (<email address hidden>)
>
> Build key: armv6 linux g++-4 full-config
> Compat build key: |
> Build date: 2010-11-04
> Installation prefix: /usr
> Library path: /usr/lib
> Include path: /usr/include/qt4
> Processor features: neon
>
> If it says "neon" is present (like above), then it looks like there was a
> detection mistake. Can you try turning the feature off by setting
> QT_NO_CPU_
4.7, the one used by Maverick doesn't export the processor features line.
Best thing would be to get the proper trace from the sigill.
> Finally, it would be nice also to have the command-line of the compiler used
> when compiling the actual .cpp file.
One example: shared/ QtCore -g -O2 include/ freetype2 -pthread -I/usr/ include/ glib-2. 0 lib/glib- 2.0/include -mfpu=neon -O2 -fvisibility=hidden inlines- hidden -Wall -W -D_REENTRANT -fPIC -DQT_SHARED USING_NAMESPACE -DQT_NO_ CAST_TO_ ASCII CAST_WARNINGS -DQT3_SUPPORT -DQT_MOC_COMPAT FAST_OPERATOR_ PLUS -DQT_USE_ FAST_CONCATENAT ION ER=\"/lib/ ld-linux. so.3\" -DHB_EXPORT= Q_CORE_ EXPORT SOURCE -D_LARGEFILE_SOURCE /mkspecs/ linux-g+ + -I. -I../../include -I../.. /include/ QtCore release- shared -Iglobal -I../3rdparty/ harfbuzz/ src release- shared -o shared/ qsimd.o tools/qsimd.cpp
g++ -c -include .pch/release-
-I/usr/
-I/usr/
-fvisibility-
-DQT_BUILD_CORE_LIB -DQT_NO_
-DQT_ASCII_
-DQT_USE_
-DELF_INTERPRET
-DQT_HAVE_NEON -DQT_NO_DEBUG -D_LARGEFILE64_
-I../..
-I.rcc/
-I../3rdparty/md5 -I../3rdparty/md4 -I.moc/
.obj/release-