From: Maxime Ripard <maxime.ripard@anandra.org>
To: buildroot@busybox.net
Subject: [Buildroot] tcl build error
Date: Wed, 6 Jan 2010 19:03:43 +0100 [thread overview]
Message-ID: <20100106180343.GX15153@anandra.org> (raw)
Hi all,
I'm having trouble getting tcl building correctly for generic_arm
architecture, and using the buildroot-generated toolchain. With
both of the latest release and the git tree, it cannot build. Here is
the output :
In file included from ./../generic/tclPort.h:27,
from ./../generic/tclAlloc.c:29:
./../generic/../unix/tclUnixPort.h:71: error: expected ?=?, ?,?, ?;?,
?asm? or ?__attribute__? before ?Tcl_SeekOffset?
make[1]: *** [tclAlloc.o] Error 1
I've searched the code to find the error, but couldn't find what causes
it.
Looking forward to your help,
--
Maxime Ripard
?tudiant ? l'Universit? de Technologie de Belfort - Montb?liard (UTBM)
G?nie Informatique (GI 04)
6bis rue Paul Giroud
90000 Belfort
France
06 85 40 57 32
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100106/c89d6ff9/attachment.pgp>
reply other threads:[~2010-01-06 18:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100106180343.GX15153@anandra.org \
--to=maxime.ripard@anandra.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox