Busybox awk errors

Busybox awk errors

[stephen Turner]

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

Quick question for those using a busybox based musl system,

I can cross compile musl programs fine on my host debian system (using a
dynamically linked gcc/binutils/musl toolchain (thanks for all the help
getting that working!)) but the build environment i'm making (which could
very well be broke as hell) Partially compiles gcc then errors out
complaining about

"awk -f /blah/blah/i386-builtin-types.awk /blah/blah/i386-builtin-types.def
> tmp-bt.inc"
"awk /blah/blah/i386-builtin-types.awk:164 call to undefined function"
"t-i386: recipe for target s-i386-bt failed"

The biggest difference obviously is the use of gnu programs on debian vs
the busybox system that's failing.

Has anyone working with similar setups seen this issue before? I guess I
could just install gawk and try again to prove if its the busybox awk or
not.....

[-- Attachment #2: Type: text/html, Size: 1037 bytes --]

Re: Busybox awk errors

[Rich Felker]

On Wed, Nov 05, 2014 at 04:10:28PM -0500, stephen Turner wrote:
> Quick question for those using a busybox based musl system,
> 
> I can cross compile musl programs fine on my host debian system (using a
> dynamically linked gcc/binutils/musl toolchain (thanks for all the help
> getting that working!)) but the build environment i'm making (which could
> very well be broke as hell) Partially compiles gcc then errors out
> complaining about
> 
> "awk -f /blah/blah/i386-builtin-types.awk /blah/blah/i386-builtin-types.def
> > tmp-bt.inc"
> "awk /blah/blah/i386-builtin-types.awk:164 call to undefined function"
> "t-i386: recipe for target s-i386-bt failed"
> 
> The biggest difference obviously is the use of gnu programs on debian vs
> the busybox system that's failing.
> 
> Has anyone working with similar setups seen this issue before? I guess I
> could just install gawk and try again to prove if its the busybox awk or
> not.....

I think this particular failure was a bug in busybox that was fixed
more than a year ago. But if you have further problems and it's
practical for you to use gawk, that should be a solution too.

Rich

Re: Busybox awk errors

[stephen Turner]

[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]

That's interesting. I have a script that downloads every time i install
busybox from the "latest" folder on their server and sets up the links
automagically. Thanks for the quick response, i'm going to try gawk and
check in with the busybox maintainers to make sure that's a current
version.


On Wed, Nov 5, 2014 at 4:31 PM, Rich Felker <dalias@libc.org> wrote:

> On Wed, Nov 05, 2014 at 04:10:28PM -0500, stephen Turner wrote:
> > Quick question for those using a busybox based musl system,
> >
> > I can cross compile musl programs fine on my host debian system (using a
> > dynamically linked gcc/binutils/musl toolchain (thanks for all the help
> > getting that working!)) but the build environment i'm making (which could
> > very well be broke as hell) Partially compiles gcc then errors out
> > complaining about
> >
> > "awk -f /blah/blah/i386-builtin-types.awk
> /blah/blah/i386-builtin-types.def
> > > tmp-bt.inc"
> > "awk /blah/blah/i386-builtin-types.awk:164 call to undefined function"
> > "t-i386: recipe for target s-i386-bt failed"
> >
> > The biggest difference obviously is the use of gnu programs on debian vs
> > the busybox system that's failing.
> >
> > Has anyone working with similar setups seen this issue before? I guess I
> > could just install gawk and try again to prove if its the busybox awk or
> > not.....
>
> I think this particular failure was a bug in busybox that was fixed
> more than a year ago. But if you have further problems and it's
> practical for you to use gawk, that should be a solution too.
>
> Rich
>

[-- Attachment #2: Type: text/html, Size: 2165 bytes --]

Re: Busybox awk errors

[John Spencer]

Rich Felker wrote:
> On Wed, Nov 05, 2014 at 04:10:28PM -0500, stephen Turner wrote:
>> Quick question for those using a busybox based musl system,
>>
>> I can cross compile musl programs fine on my host debian system (using a
>> dynamically linked gcc/binutils/musl toolchain (thanks for all the help
>> getting that working!)) but the build environment i'm making (which could
>> very well be broke as hell) Partially compiles gcc then errors out
>> complaining about
>>
>> "awk -f /blah/blah/i386-builtin-types.awk /blah/blah/i386-builtin-types.def
>>> tmp-bt.inc"
>> "awk /blah/blah/i386-builtin-types.awk:164 call to undefined function"
>> "t-i386: recipe for target s-i386-bt failed"
>>
>> The biggest difference obviously is the use of gnu programs on debian vs
>> the busybox system that's failing.
>>
>> Has anyone working with similar setups seen this issue before? I guess I
>> could just install gawk and try again to prove if its the busybox awk or
>> not.....
> 
> I think this particular failure was a bug in busybox that was fixed
> more than a year ago. But if you have further problems and it's

yep. sabotage has a patch for it in KEEP/ (i believe it was 
busybox-awk-emptyfun.patch), and in the latest busybox version it's 
fixed as well.

--JS

Re: Busybox awk errors

[stephen Turner]

[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]

Nice! Thanks for the tips. It looks like I need to see what else sabotage
has been up to before proceeding.
On Nov 5, 2014 8:28 PM, "John Spencer" <maillist-musl@barfooze.de> wrote:

> Rich Felker wrote:
>
>> On Wed, Nov 05, 2014 at 04:10:28PM -0500, stephen Turner wrote:
>>
>>> Quick question for those using a busybox based musl system,
>>>
>>> I can cross compile musl programs fine on my host debian system (using a
>>> dynamically linked gcc/binutils/musl toolchain (thanks for all the help
>>> getting that working!)) but the build environment i'm making (which could
>>> very well be broke as hell) Partially compiles gcc then errors out
>>> complaining about
>>>
>>> "awk -f /blah/blah/i386-builtin-types.awk /blah/blah/i386-builtin-types.
>>> def
>>>
>>>> tmp-bt.inc"
>>>>
>>> "awk /blah/blah/i386-builtin-types.awk:164 call to undefined function"
>>> "t-i386: recipe for target s-i386-bt failed"
>>>
>>> The biggest difference obviously is the use of gnu programs on debian vs
>>> the busybox system that's failing.
>>>
>>> Has anyone working with similar setups seen this issue before? I guess I
>>> could just install gawk and try again to prove if its the busybox awk or
>>> not.....
>>>
>>
>> I think this particular failure was a bug in busybox that was fixed
>> more than a year ago. But if you have further problems and it's
>>
>
> yep. sabotage has a patch for it in KEEP/ (i believe it was
> busybox-awk-emptyfun.patch), and in the latest busybox version it's fixed
> as well.
>
> --JS
>
>

[-- Attachment #2: Type: text/html, Size: 2205 bytes --]