| 1 |
>>> On 21-02-2008 22:25:02 +1100, Matt Michalowski wrote: |
| 2 |
>>>> rabbe@×××××××.se wrote: |
| 3 |
>>>>> [ text clipped ] |
| 4 |
>>>>> However, the ebuild pulls in 15 dependencies and texinfo, which is |
| 5 |
>>>>> number |
| 6 |
>>>>> 11 of the 15, fails to build. The final lines of console output are: |
| 7 |
>>>>> |
| 8 |
>>>>> [ text clipped ] |
| 9 |
>>>>> help2man: can't get `--help' info from ../util/texi2dvi |
| 10 |
>>>> |
| 11 |
>>>> I actually hit the same error when trying to bootstrap on FreeBSD 6.3 |
| 12 |
>>>> for the first time the other day, but I thought it was probably just |
| 13 |
>>>> me and I was going to try again from scratch. |
| 14 |
>>> |
| 15 |
>>> Fabian wrote: |
| 16 |
>>> You should emerge "<bash-3.2_p33" to get around this. |
| 17 |
>>> |
| 18 |
>> I put an entry into etc/portage/package.mask denying 3.2_p33 and |
| 19 |
>> higher. It helped! |
| 20 |
>> |
| 21 |
>> I then ran into a problem with coreutils, where the ebuild wants |
| 22 |
>> to unpack coreutils-6.10.tar.lzma. So I thought, better emerge the |
| 23 |
>> "lzma" utility first. Inserting "emerge --oneshot lzma" just before |
| 24 |
>> emerging coreutils did not solve it though; lzma itself is emerged |
| 25 |
>> nicely (no depenencies pulled in). But it does not make the tar.lzma |
| 26 |
>> file possible to unpack, here is what goes in the console log: |
| 27 |
>> |
| 28 |
>> * checking ebuild checksums ;-) ... [ ok ] |
| 29 |
>> * checking auxfile checksums ;-) ... [ ok ] |
| 30 |
>> * checking miscfile checksums ;-) ... [ ok ] |
| 31 |
>> * checking coreutils-6.10.tar.lzma ;-) ... [ ok ] |
| 32 |
>> * checking coreutils-6.10-patches-1.1.tar.bz2 ;-) ... [ ok ] |
| 33 |
>>>>> Unpacking source... |
| 34 |
>>>>> Unpacking coreutils-6.10.tar.lzma to |
| 35 |
>> /local/scratch/portage/sys-apps/coreutils-6.10-r1/work |
| 36 |
>> |
| 37 |
>> LZMA 4.57 Copyright (c) 1999-2007 Igor Pavlov 2007-12-06 |
| 38 |
>> |
| 39 |
>> Error: Incorrect command |
| 40 |
>> |
| 41 |
>> |
| 42 |
>> Usage: LZMA <e|d> inputFile outputFile [<switches>...] |
| 43 |
>> e: encode file |
| 44 |
>> d: decode file |
| 45 |
>> b: Benchmark |
| 46 |
>> <Switches> |
| 47 |
>> -a{N}: set compression mode - [0, 1], default: 1 (max) |
| 48 |
>> -d{N}: set dictionary - [0,30], default: 23 (8MB) |
| 49 |
>> -fb{N}: set number of fast bytes - [5, 273], default: 128 |
| 50 |
>> -mc{N}: set number of cycles for match finder |
| 51 |
>> -lc{N}: set number of literal context bits - [0, 8], default: 3 |
| 52 |
>> -lp{N}: set number of literal pos bits - [0, 4], default: 0 |
| 53 |
>> -pb{N}: set number of pos bits - [0, 4], default: 2 |
| 54 |
>> -mf{MF_ID}: set Match Finder: [bt2, bt3, bt4, hc4], default: bt4 |
| 55 |
>> -mt{N}: set number of CPU threads |
| 56 |
>> -eos: write End Of Stream marker |
| 57 |
>> -si: read data from stdin |
| 58 |
>> -so: write data to stdout |
| 59 |
>> |
| 60 |
>> Error |
| 61 |
>> * ERROR: sys-apps/coreutils-6.10-r1 failed: |
| 62 |
>> * failure unpacking coreutils-6.10.tar.lzma |
| 63 |
>> |
| 64 |
> |
| 65 |
> Hmm .. maybe Gentoo tar is needed to deal with .tar.lzma files. I have |
| 66 |
> thrown in an early emerge of tar as well to see if it makes any |
| 67 |
> difference. |
| 68 |
|
| 69 |
... not, it did not help. I also notice that automake-1.10.1 has been |
| 70 |
emerged previously, which should be good according to this link |
| 71 |
|
| 72 |
http://blog.hartwork.org/?p=118 |
| 73 |
|
| 74 |
which claims that automake-1.10.1 has lzma support. Oh well, seems I'm |
| 75 |
stuck for now. |
| 76 |
|
| 77 |
|
| 78 |
-- |
| 79 |
gentoo-alt@l.g.o mailing list |
Archives