From: Alex Song <songqf9@yahoo.ca>
To: buildroot@busybox.net
Subject: [Buildroot] support for SuperH
Date: Wed, 13 Dec 2006 11:16:52 -0500 (EST) [thread overview]
Message-ID: <98746.66357.qm@web50012.mail.yahoo.com> (raw)
Hi,
Looks like buildroot supports SuperH, but I got
several errors when trying to use it.
1. When I select sh3, it tries to install the kernel
headers by "make ARCH=sh3 ...". But kernel only has
arch sh. I changed top level Config.in and made this
pass.
2. Then duing building, it complains
make[1]: Entering directory
`/root/lab/buildroot-sh/buildroot/toolchain_build_sh/uClibc'
CC libc/sysdeps/linux/sh/syscall.os
libc/sysdeps/linux/sh/syscall.c:11: error: conflicting
types for 'syscall'
./include/unistd.h:1014: error: previous declaration
of 'syscall' was here
make[2]: *** [libc/sysdeps/linux/sh/syscall.os] Error
1
The syscall.c has
long syscall(long sysnum,
long arg1, long arg2, long arg3,
long arg4, long arg5, long arg6)
while unistd.h has
extern long int syscall (long int __sysno, ...)
__THROW;
Is there a fix? What is the correct way to build a
toolchain for sh?
Thanks a lot,
Alex
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
reply other threads:[~2006-12-13 16:16 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=98746.66357.qm@web50012.mail.yahoo.com \
--to=songqf9@yahoo.ca \
--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