| 1 |
Look if you have star in your spec file. If it's so change it to tar. |
| 2 |
I had the same problem. |
| 3 |
|
| 4 |
Carl Flippin wrote: |
| 5 |
|
| 6 |
>I never touched genkernel.conf. I will try putting in a debug |
| 7 |
>statement to dump out the command in question to see what is going on. |
| 8 |
>Thanks for the pointer. |
| 9 |
> |
| 10 |
>Thanks, |
| 11 |
>Carl Flippin |
| 12 |
> |
| 13 |
>On 6/14/05, Zac Medico <zmedico@×××××.com> wrote: |
| 14 |
> |
| 15 |
> |
| 16 |
>>Carl Flippin wrote: |
| 17 |
>> |
| 18 |
>> |
| 19 |
>>>After the kernel compile, however, genkernel craps out saying: |
| 20 |
>>> |
| 21 |
>>>"Could not extract busybox source tarball" |
| 22 |
>>> |
| 23 |
>>> |
| 24 |
>>> |
| 25 |
>>That means tar had a nonzero exit status inside /usr/share/genkernel/gen_compile.sh |
| 26 |
>> |
| 27 |
>> tar -jxpf ${BUSYBOX_SRCTAR} || |
| 28 |
>> gen_die 'Could not extract busybox source tarball!' |
| 29 |
>> |
| 30 |
>>You probably changed the busybox settings in genkernel.conf. You need to make sure genkernel can find a good busybox source tarball. The default tarball is /usr/share/genkernel/pkg/busybox-1.00-pre7-losetup-crypto-alpha.tar.bz2 |
| 31 |
>> |
| 32 |
>>Zac |
| 33 |
>>-- |
| 34 |
>>gentoo-catalyst@g.o mailing list |
| 35 |
>> |
| 36 |
>> |
| 37 |
>> |
| 38 |
>> |
| 39 |
> |
| 40 |
> |
| 41 |
> |
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-catalyst@g.o mailing list |
Archives