From: Phillip Liang <liangcw94086@yahoo.com>
To: buildroot@busybox.net
Subject: [Buildroot] llseek errors in e2fsprogs
Date: Fri, 17 Aug 2007 17:24:25 -0700 (PDT) [thread overview]
Message-ID: <649040.99213.qm@web54202.mail.re2.yahoo.com> (raw)
Hello,
I am compiling buildroot 2007-06-07 for at91sam9263
and stuck with this problem.
linux-kernel 2.6.20.4
gcc-4.1.2-uclibc
Your help is appreciated.
making all in lib/ext2fs
make[3]: Entering directory
`/scratch/buildroot-atmel/build_arm_small/e2fsprogs-1.39/lib/ext2fs'
CC llseek.c
llseek.c:65: error: expected declaration specifiers or
'...' before '_llseek'
llseek.c:65: error: expected declaration specifiers or
'...' before 'fd'
llseek.c:65: error: expected declaration specifiers or
'...' before 'offset_high'
llseek.c:66: error: expected declaration specifiers or
'...' before 'offset_low'
llseek.c:66: error: expected declaration specifiers or
'...' before 'result'
llseek.c:67: error: expected declaration specifiers or
'...' before 'origin'
llseek.c: In function '_syscall5':
llseek.c:71: error: expected '=', ',', ';', 'asm' or
'__attribute__' before '{' token
llseek.c:91: error: expected '=', ',', ';', 'asm' or
'__attribute__' before '{' token
llseek.c:65: error: parameter name omitted
llseek.c:65: error: parameter name omitted
llseek.c:65: error: parameter name omitted
llseek.c:66: error: parameter name omitted
llseek.c:66: error: parameter name omitted
llseek.c:67: error: parameter name omitted
llseek.c:114: error: expected '{' at end of input
make[3]: *** [llseek.o] Error 1
____________________________________________________________________________________
Luggage? GPS? Comic books?
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz
next reply other threads:[~2007-08-18 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 0:24 Phillip Liang [this message]
2007-08-20 14:38 ` [Buildroot] llseek errors in e2fsprogs Bernhard Fischer
2007-08-21 0:31 ` Phillip Liang
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=649040.99213.qm@web54202.mail.re2.yahoo.com \
--to=liangcw94086@yahoo.com \
--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