[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Continuous problems --no-undefined
From:       Harri Porten <porten () froglogic ! com>
Date:       2005-02-23 13:41:47
Message-ID: Pine.LNX.4.44.0502231433490.28312-100000 () alster ! froglogic ! com
[Download RAW message or body]

Hi,

for several weeks I've been having problems with the use of the
--no-undefined and --allow-shlib-undefined flags. I contribute this to my
dated gcc/binutils (2.95/2.12.90) installation and therefore haven't
complained earlier, yet. After all there was some work going on to fix
similar issues but mine have remained.

The problem occurs with libraries referencing libstdc++ symbols:

/bin/sh ../libtool --silent --mode=link --tag=CXX g++  -Wnon-virtual-dtor
-Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE
-Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith
-Wwrite-strings -fno-builtin -g -O2 -fno-exceptions -fno-check-new
-fno-common -fno-exceptions -fno-check-new -fno-common
-DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT
-DQT_NO_TRANSLATION    -o libkdefx.la -rpath /home/porten/kde/lib -R
/home/porten/kde/lib -R /home/porten/kde/lib -R
/home/porten/qt-3.3-snapshot//lib -R /usr/X11R6/lib
-L/home/porten/kde/lib -L/home/porten/qt-3.3-snapshot//lib
-L/usr/X11R6/lib    -no-undefined -Wl,--no-undefined
-Wl,--allow-shlib-undefined -version-info 6:0:2 kpixmap.lo
kpixmapsplitter.lo kpixmapeffect.lo kimageeffect.lo kdrawutil.lo kstyle.lo
kcpuinfo.lo -lqt-mt  -lz -lpng -lz -lm -lXext -lX11  -lSM -lICE -lpthread
-lXrender
.libs/kimageeffect.o: In function
`QValueList<QString>::detachInternal(void)':
/home/porten/qt-3.3-snapshot/include/qvaluelist.h(.text+0x56): undefined
reference to `cerr'
/home/porten/qt-3.3-snapshot/include/qvaluelist.h(.text+0x5b): undefined
reference to `ostream::operator<<(char const *)'
/home/porten/qt-3.3-snapshot/include/qvaluelist.h(.text+0x63): undefined
reference to `endl(ostream &)'

So far I've resorted to remove the offending flags from the
KDE_NO_UNDEFINED entry in config.status. But I'm willing to look into
this in case someone could hint me at the possible location of the
problem. Is it the configure check that reports back a wrong result or is
above link line broken and misses e.g. a reference to -lstdc++?

Harri.

[prev in list] [next in list] [prev in thread] [next in thread]