[Bug 747] uicmoc4-native_4.3.1.bb

[bugzilla-daemon at bugzilla.openmoko.org]

http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=747

technil at riseup.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |technil at riseup.net



------- Additional Comments From technil at riseup.net  2007-08-27 00:55 -------
Same package failing here while building openmoko-devel-image.

NOTE: Tasks Summary: Attempted 1036 tasks of which 72 didn't need to be rerun
and 1 failed.
ERROR:
'/media/usbdisk/moko/openembedded/packages/uicmoc/uicmoc4-native_4.3.1.bb' failed
make: *** [openmoko-devel-image] Error 1

Processor: x86 Intel Core Duo

GCC:

technil at automata:/media/usbdisk/moko/build/tmp/work/i686-linux/uicmoc4-native-4.3.1-r0/temp$
gcc -v
Reading specs from /usr/lib/gcc/i486-linux-gnu/3.4.6/specs
Configured with: ../src/configure -v --enable-languages=c,c++,f77,pascal
--prefix=/usr --libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4
--enable-shared --with-system-zlib --enable-nls --without-included-gettext
--program-suffix=-3.4 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --with-tune=pentium4 i486-linux-gnu
Thread model: posix
gcc version 3.4.6 (Ubuntu 3.4.6-3ubuntu1)


when looking in:

moko/build/tmp/work/i686-linux/uicmoc4-native-4.3.1-r0/temp/log.do_compile.2139

problem seems to start here in the log:

ccache gcc  -c -isystem/media/usbdisk/moko/build/tmp/staging/i686-linux/include
-Os -fno-exceptions -O2 -fvisibility=hidden -Wall -W -D_REENTRANT
-DQT_BUILD_GUI_LIB -DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT3_SUPPORT
-DQT_MOC_COMPAT -DQT_NO_IMAGEFORMAT_PNG -DQT_RASTER_IMAGEENGINE
-DQT_RASTER_PAINTENGINE -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT_HAVE_SSE
-DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_NO_FONTCONFIG -DQT_NO_STYLE_MAC
-DQT_NO_STYLE_WINDOWSVISTA -DQT_NO_STYLE_WINDOWSXP -DQ_INTERNAL_QAPP_SRC
-DQT_NO_DEBUG -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE
-I../../mkspecs/qws/linux-x86-g++ -I. -I../../include/QtCore
-I../../include/QtCore -I../../include -I../../include/QtGui
-I/usr/include/freetype2 -I../3rdparty/harfbuzz/src -Idialogs
-I../../include/QtNetwork -I.moc/release-static-emb-x86
-I.uic/release-static-emb-x86 -o .obj/release-static-emb-x86/qblackraster.o
painting/qblackraster.c
cc1: error: unrecognized command line option "-fvisibility=hidden"
make[1]: *** [.obj/release-static-emb-x86/qblackraster.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory
`/media/usbdisk/moko/build/tmp/work/i686-linux/uicmoc4-native-4.3.1-r0/qtopia-core-opensource-src-4.3.1/src/gui'
FATAL: oe_runmake failed

for me the offending option was: -fvisibility=hidden

It appears in the GCC 4.2.1 manual http://gcc.gnu.org/onlinedocs/gcc-4.2.1/gcc.pdf
But not in the GCC 3.4.6 manual
http://gcc.gnu.org/onlinedocs/gcc-3.4.6/gcc.pdf

>From the GCC 4.2.1 Manual:
"
-fvisibility=default|internal|hidden|protected
   Set the default ELF image symbol visibility to the specified option—all
symbols will be marked with this unless overridden within the code. Using this
feature can very substantially improve linking and load times of shared object
libraries, produce more optimized code, provide near-perfect API export and
prevent symbol clashes. It is strongly recommended that you use this in any
shared objects you distribute. Despite the nomenclature, default always means
public ie; available to be linked against from outside the shared object.
protected and internal are pretty useless in real-world usage so the only other
commonly used option will be hidden. The default if ‘-fvisibility’ isn’t
specified is default, i.e., make every symbol public—this causes the same
behavior as previous versions of GCC."

they suggest looking at:
          
http://gcc.gnu.org/wiki/Visibility.

I am reading it, but it is still over my head. maybe GCC 3.4.6 chokes on the
-fvisibility=hidden flag (not defined) and we just need to install a newer GCC?




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.