Hi,
On Jul 9, 2008, at 8:22 AM, Marian Aldenhövel wrote:
Hi,
I have a problem building the package commonc++ for my custom target.
The target package selection is based on the tlx example and is very
slim. It
is marked as a cross-build and targets x86 systems without any CPU-
specific
optimizations. The target builds fine without commonc++. Now I have
added
the package and the build fails at the make stage.
ERROR-LOG
(Complete file at: http://www.marian-aldenhoevel.de/tmp/ERROR-LOG)
i686-t2-linux-uclibc-g++ -DHAVE_CONFIG_H -I. -I.. -I../inc -I../src -
DCCXX_EXPORT_LIBRARY -D_GNU_SOURCE -I../inc -g -O2 -MT thread.lo -MD
-MP -MF .deps/thread.Tpo -c thread.cpp -fPIC -DPIC -o .libs/thread.o
In file included from /home/kbox/t2/build/default-8.0-trunk-kbox-x86-
cross/usr/include/sys/un.h:38,
from ../inc/cc++/config.h:806,
from mutex.cpp:38:
/home/kbox/t2/build/default-8.0-trunk-kbox-x86-cross/usr/include/
string.h:289: error: expected unqualified-id before 'char'
/home/kbox/t2/build/default-8.0-trunk-kbox-x86-cross/usr/include/
string.h:289: error: expected initializer before 'char'
In file included from /home/kbox/t2/build/default-8.0-trunk-kbox-x86-
cross/usr/include/sys/un.h:38,
from ../inc/cc++/config.h:806,
from thread.cpp:38:
/home/kbox/t2/build/default-8.0-trunk-kbox-x86-cross/usr/include/
string.h:289: error: expected unqualified-id before 'char'
/home/kbox/t2/build/default-8.0-trunk-kbox-x86-cross/usr/include/
string.h:289: error: expected initializer before 'char'
string.h? Feels pretty basic and I am sure the file in itself is OK.
It is
even checked for while configuring:
config.log
(Complete file at: http://www.marian-aldenhoevel.de/tmp/config.log):
checking for string.h: yes
checking sys/un.h usability: yes
checking sys/un.h presence: yes
checking for sys/un.h: yes
What can cause this problem?
Hard to tell from this distance :-) I guess you did not update gcc
togcc-4.3
and this is due to the fewer implicit includes of the new 4.3 version?
Maybe just something not yet defined due missing explicit inclusion of
some basic type header in the uclibc?
Is this problem still open or did you solve it in the meantime? If
it's still
a problem I could try to reproduce.
Yours
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2
