[Buildroot] ARM build error with llseek.c

[Arun Reddy]

CC'd buildroot list

On Thu, May 8, 2008 at 6:12 PM, Arun Reddy <reddyac at gmail.com> wrote:

> Thank you for your help. If anyone would like to chime in on how to define
> _syscall5 or just with dealing with this problem you would be helping a lot!
>
>
> On Thu, May 8, 2008 at 4:30 PM, hartleys <hartleys at visionengravers.com>
> wrote:
>
>>  Unfortunately no... Like I said I have not yet tried to build a
>> toolchain from source. Sorry
>>
>>  ------------------------------
>> *From:* Arun Reddy [mailto:reddyac at gmail.com]
>> *Sent:* Thursday, May 08, 2008 4:24 PM
>> *To:* hartleys
>> *Cc:* Buildroot List
>> *Subject:* Re: [Buildroot] ARM build error with llseek.c
>>
>> Thanks for the information hartleys. Do you know how I can go about
>> defining _syscall5? Will I need to go into uClibc's menuconfig and select it
>> first?
>>
>> On Thu, May 8, 2008 at 4:11 PM, hartleys <hartleys at visionengravers.com>
>> wrote:
>>
>>>  This is just a guess but...
>>>
>>> I'm still using a prebuilt external toolchain and haven't tried building
>>> one from source yet so I'm not sure how to fix it. But, maybe this
>>> information to help.
>>>
>>> It appears you have a problem with your toolchain. That line in llseek.c
>>> should be invoving a uClibc macro (_syscall5) but it's not defined so the
>>> compiler is dying on the syntax of the "function" _syscall.
>>>
>>> Just my two cents...
>>>
>>>
>>>  ------------------------------
>>> *From:* buildroot-bounces at uclibc.org [mailto:
>>> buildroot-bounces at uclibc.org] *On Behalf Of *Arun Reddy
>>> *Sent:* Thursday, May 08, 2008 3:49 PM
>>> *To:* Buildroot List
>>> *Subject:* [Buildroot] ARM build error with llseek.c
>>>
>>>   Hi everyone,
>>>
>>> I am continuing with my ARM build and I ran into a problem with llseek.c:
>>>
>>> http://img211.imageshack.us/img211/6387/e2fsprogsph4.jpg
>>>
>>> I found that this problem was reported before:
>>> http://bugs.busybox.net/view.php?id=1548
>>>
>>> and the solution seemed to involve enabling large file support in
>>> buildroot's configuration. I did this, but still get the same error. Does
>>> anyone know why LFS needs to be activated and in my case, why it doesn't
>>> resolve this issue? Any help on this problem would be appreciated. Thank
>>> you.
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080508/755cf45e/attachment.htm