* [Buildroot] ARM build error with llseek.c @ 2008-05-08 22:49 Arun Reddy 2008-05-08 23:11 ` hartleys 0 siblings, 1 reply; 9+ messages in thread From: Arun Reddy @ 2008-05-08 22:49 UTC (permalink / raw) To: buildroot 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/d0bc2df3/attachment.htm ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] ARM build error with llseek.c 2008-05-08 22:49 [Buildroot] ARM build error with llseek.c Arun Reddy @ 2008-05-08 23:11 ` hartleys 2008-05-08 23:24 ` Arun Reddy 0 siblings, 1 reply; 9+ messages in thread From: hartleys @ 2008-05-08 23:11 UTC (permalink / raw) To: buildroot 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@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/91dde945/attachment.htm ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] ARM build error with llseek.c 2008-05-08 23:11 ` hartleys @ 2008-05-08 23:24 ` Arun Reddy [not found] ` <1CF6EDDF0820924DA43C9A52FE7325950B4DAA2E@MI8NYCMAIL17.Mi8.com> 0 siblings, 1 reply; 9+ messages in thread From: Arun Reddy @ 2008-05-08 23:24 UTC (permalink / raw) To: buildroot 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@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/8b65557a/attachment-0001.htm ^ permalink raw reply [flat|nested] 9+ messages in thread
[parent not found: <1CF6EDDF0820924DA43C9A52FE7325950B4DAA2E@MI8NYCMAIL17.Mi8.com>]
[parent not found: <326f33790805081812sc3b8d29v948f331f7fe84653@mail.gmail.com>]
* [Buildroot] ARM build error with llseek.c [not found] ` <326f33790805081812sc3b8d29v948f331f7fe84653@mail.gmail.com> @ 2008-05-09 1:13 ` Arun Reddy 2008-05-12 3:24 ` Arun Reddy 0 siblings, 1 reply; 9+ messages in thread From: Arun Reddy @ 2008-05-09 1:13 UTC (permalink / raw) To: buildroot CC'd buildroot list On Thu, May 8, 2008 at 6:12 PM, Arun Reddy <reddyac@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@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@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 ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] ARM build error with llseek.c 2008-05-09 1:13 ` Arun Reddy @ 2008-05-12 3:24 ` Arun Reddy 2008-05-15 23:20 ` Christopher Taylor 0 siblings, 1 reply; 9+ messages in thread From: Arun Reddy @ 2008-05-12 3:24 UTC (permalink / raw) To: buildroot Hey everyone, I was just curious if anyone had any more suggestions on this problem? I am still finding myself stuck with it. Thank you. On Thu, May 8, 2008 at 6:13 PM, Arun Reddy <reddyac@gmail.com> wrote: > CC'd buildroot list > > > On Thu, May 8, 2008 at 6:12 PM, Arun Reddy <reddyac@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@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@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/20080511/4f43bd29/attachment.htm ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] ARM build error with llseek.c 2008-05-12 3:24 ` Arun Reddy @ 2008-05-15 23:20 ` Christopher Taylor 2008-05-15 23:41 ` Arun Reddy 0 siblings, 1 reply; 9+ messages in thread From: Christopher Taylor @ 2008-05-15 23:20 UTC (permalink / raw) To: buildroot Whops, replied to poster not to list ... sorry everyone .... I've had bad luck figuring out what parts of the tool chain I need to make clean when I make a change to uclibc. Look for LFS, large file support and other things like that in menuconfig uclibc-menuconifg busybox-menuconfig linux26-menuconifg by suggestion is then to go to the build dir for each of the major components (buildroot, uclibc, busybox, and the kernel) and do a make clean. You should have better luck from there. if that doesn't work, try d/l buildroot again, copy over your config files and rebuild HTH Chris - Show quoted text - On Sun, May 11, 2008 at 11:24 PM, Arun Reddy <reddyac@gmail.com> wrote: > Hey everyone, > > I was just curious if anyone had any more suggestions on this problem? I am > still finding myself stuck with it. Thank you. > > On Thu, May 8, 2008 at 6:13 PM, Arun Reddy <reddyac@gmail.com> wrote: >> >> CC'd buildroot list >> >> On Thu, May 8, 2008 at 6:12 PM, Arun Reddy <reddyac@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@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@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. >>>>> >>>> >>> >> > > > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot > On Sun, May 11, 2008 at 11:24 PM, Arun Reddy <reddyac@gmail.com> wrote: > Hey everyone, > > I was just curious if anyone had any more suggestions on this problem? I am > still finding myself stuck with it. Thank you. > > On Thu, May 8, 2008 at 6:13 PM, Arun Reddy <reddyac@gmail.com> wrote: >> >> CC'd buildroot list >> >> On Thu, May 8, 2008 at 6:12 PM, Arun Reddy <reddyac@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@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@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. >>>>> >>>> >>> >> > > > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot > ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] ARM build error with llseek.c 2008-05-15 23:20 ` Christopher Taylor @ 2008-05-15 23:41 ` Arun Reddy 2008-05-16 7:53 ` Bernhard Fischer 0 siblings, 1 reply; 9+ messages in thread From: Arun Reddy @ 2008-05-15 23:41 UTC (permalink / raw) To: buildroot Thanks Chris, Looks like the issue was with LFS not being enabled in uclibc (CONFIG_UCLIBC_HAS_LFS) and also BusyBox not having BR2_PACKAGE_BUSYBOX_HIDE_OTHERS selected. I did a make clean for everything and rebuilt, and got past that error. I am fairly certain I understand why LFS needed to be enabled, because I was reading up on a couple threads online about llseek.c being used for large file support in general, while lseek.c is used for small files. I want LFS for my purposes, and it is possible that by not selecting LFS in the uclibc menuconfig, that a specific function or variable wasn't defined correctly in a header file used by llseek.c, and therefore it couldn't compile correctly. This is of course my best assumption. As for selecting BusyBox's hide others option, I am unsure as to why that works, but found it here as a suggestion. http://buildroot.uclibc.org/lists/buildroot/2007-June/003077.html I hope this helps anyone in the future. On Thu, May 15, 2008 at 4:20 PM, Christopher Taylor <chtaylo3@gmail.com> wrote: > Whops, replied to poster not to list ... sorry everyone .... > > > I've had bad luck figuring out what parts of the tool chain I need to > make clean when I make a change to uclibc. Look for LFS, large file > support and other things like that in > menuconfig > uclibc-menuconifg > busybox-menuconfig > linux26-menuconifg > > by suggestion is then to go to the build dir for each of the major > components (buildroot, uclibc, busybox, and the kernel) and do a make > clean. > > You should have better luck from there. > > > if that doesn't work, try d/l buildroot again, copy over your config > files and rebuild > > HTH > Chris > - Show quoted text - > > > On Sun, May 11, 2008 at 11:24 PM, Arun Reddy <reddyac@gmail.com> wrote: > > Hey everyone, > > > > I was just curious if anyone had any more suggestions on this problem? I > am > > still finding myself stuck with it. Thank you. > > > > On Thu, May 8, 2008 at 6:13 PM, Arun Reddy <reddyac@gmail.com> wrote: > >> > >> CC'd buildroot list > >> > >> On Thu, May 8, 2008 at 6:12 PM, Arun Reddy <reddyac@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@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. > >>>>> > >>>> > >>> > >> > > > > > > _______________________________________________ > > buildroot mailing list > > buildroot at uclibc.org > > http://busybox.net/mailman/listinfo/buildroot > > > > On Sun, May 11, 2008 at 11:24 PM, Arun Reddy <reddyac@gmail.com> wrote: > > Hey everyone, > > > > I was just curious if anyone had any more suggestions on this problem? I > am > > still finding myself stuck with it. Thank you. > > > > On Thu, May 8, 2008 at 6:13 PM, Arun Reddy <reddyac@gmail.com> wrote: > >> > >> CC'd buildroot list > >> > >> On Thu, May 8, 2008 at 6:12 PM, Arun Reddy <reddyac@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@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. > >>>>> > >>>> > >>> > >> > > > > > > _______________________________________________ > > buildroot mailing list > > buildroot at uclibc.org > > http://busybox.net/mailman/listinfo/buildroot > > > _______________________________________________ > buildroot mailing list > buildroot at uclibc.org > http://busybox.net/mailman/listinfo/buildroot > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/buildroot/attachments/20080515/f6310a99/attachment-0001.htm ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] ARM build error with llseek.c 2008-05-15 23:41 ` Arun Reddy @ 2008-05-16 7:53 ` Bernhard Fischer 2008-05-16 15:31 ` Arun Reddy 0 siblings, 1 reply; 9+ messages in thread From: Bernhard Fischer @ 2008-05-16 7:53 UTC (permalink / raw) To: buildroot On Thu, May 15, 2008 at 04:41:48PM -0700, Arun Reddy wrote: >Thanks Chris, > >Looks like the issue was with LFS not being enabled in uclibc >(CONFIG_UCLIBC_HAS_LFS) and also BusyBox not having >BR2_PACKAGE_BUSYBOX_HIDE_OTHERS selected. I did a make clean for everything >and rebuilt, and got past that error. > >I am fairly certain I understand why LFS needed to be enabled, because I was >reading up on a couple threads online about llseek.c being used for large >file support in general, while lseek.c is used for small files. I want LFS >for my purposes, and it is possible that by not selecting LFS in the uclibc >menuconfig, that a specific function or variable wasn't defined correctly in >a header file used by llseek.c, and therefore it couldn't compile correctly. >This is of course my best assumption. > >As for selecting BusyBox's hide others option, I am unsure as to why that >works, but found it here as a suggestion. It works because if you enable it then you use busybox and not the big util-linux. As for your trouble with toggling LFS and other settings. This is believed to be fixed in my tree, i.e. the user doesn't have to take care of doing make uclibc-clean gcc-clean et al when she toggles LARGEFILE, SJLJ or chooses to add or remove support for a language in her cross-compiler or stuff like that. PS: It would be helpful if you could send your errors to the list (as text, of course) and not send a link to some picture of the error message. TIA ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] ARM build error with llseek.c 2008-05-16 7:53 ` Bernhard Fischer @ 2008-05-16 15:31 ` Arun Reddy 0 siblings, 0 replies; 9+ messages in thread From: Arun Reddy @ 2008-05-16 15:31 UTC (permalink / raw) To: buildroot Bernhard, Thank you for this information. I would like to point out that I would like to give an actual .log whenever I post a problem to the mailing list, but VirtualBox seems to prevent me from doing so. I have my development environment (Debian Etch) w/o a desktop environment installed on a VirtualBox instance with Windows as the host. I set up a shared folder (to bring over the error log to Windows so I can include the text in my email) but when copying a file to my shared folder, the resulting file is more than 3GB, while the original file is of course only a couple k. I checked with VB's ticket history and it looks like this is a common problem with version 1.5.6, and for now the only way to solve it seems to involve reverting back to 1.5.4 which I haven't done yet. Thanks for bringing that up and I will certainly try and fix the issue so I can include proper text of Buildroot errors, because I certainly understand that the links I put up in earlier emails may not last too long for future Buildroot users to see. On Fri, May 16, 2008 at 12:53 AM, Bernhard Fischer <rep.dot.nop@gmail.com> wrote: > On Thu, May 15, 2008 at 04:41:48PM -0700, Arun Reddy wrote: > >Thanks Chris, > > > >Looks like the issue was with LFS not being enabled in uclibc > >(CONFIG_UCLIBC_HAS_LFS) and also BusyBox not having > >BR2_PACKAGE_BUSYBOX_HIDE_OTHERS selected. I did a make clean for > everything > >and rebuilt, and got past that error. > > > >I am fairly certain I understand why LFS needed to be enabled, because I > was > >reading up on a couple threads online about llseek.c being used for large > >file support in general, while lseek.c is used for small files. I want LFS > >for my purposes, and it is possible that by not selecting LFS in the > uclibc > >menuconfig, that a specific function or variable wasn't defined correctly > in > >a header file used by llseek.c, and therefore it couldn't compile > correctly. > >This is of course my best assumption. > > > >As for selecting BusyBox's hide others option, I am unsure as to why that > >works, but found it here as a suggestion. > > It works because if you enable it then you use busybox and not the big > util-linux. > > As for your trouble with toggling LFS and other settings. This is > believed to be fixed in my tree, i.e. the user doesn't have to take care > of doing make uclibc-clean gcc-clean et al when she toggles LARGEFILE, > SJLJ or chooses to add or remove support for a language in her > cross-compiler or stuff like that. > > PS: It would be helpful if you could send your errors to the list (as > text, of course) and not send a link to some picture of the error > message. TIA > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://busybox.net/lists/buildroot/attachments/20080516/2d4451e0/attachment-0001.htm ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2008-05-16 15:31 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-08 22:49 [Buildroot] ARM build error with llseek.c Arun Reddy
2008-05-08 23:11 ` hartleys
2008-05-08 23:24 ` Arun Reddy
[not found] ` <1CF6EDDF0820924DA43C9A52FE7325950B4DAA2E@MI8NYCMAIL17.Mi8.com>
[not found] ` <326f33790805081812sc3b8d29v948f331f7fe84653@mail.gmail.com>
2008-05-09 1:13 ` Arun Reddy
2008-05-12 3:24 ` Arun Reddy
2008-05-15 23:20 ` Christopher Taylor
2008-05-15 23:41 ` Arun Reddy
2008-05-16 7:53 ` Bernhard Fischer
2008-05-16 15:31 ` Arun Reddy
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox