| 1 |
On 12/31/2016 06:59 AM, Håkon Alstadheim wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> Den 30. des. 2016 14:44, skrev lee: |
| 5 |
>> Nikos Chantziaras <realnc@×××××.com> writes: |
| 6 |
>> |
| 7 |
>>> A world update emerged gcc-5.4.0-r2 (update from 5.4.0). At the end of |
| 8 |
>>> the build, I got this: |
| 9 |
>>> |
| 10 |
>>> * Python seems to be broken, attempting to locate CHOST ourselves ... |
| 11 |
>>> * Switching native-compiler to x86_64-pc-linux-gnu-5.4.0 |
| 12 |
>>> ...PORTAGE_BZIP2_COMMAND setting is invalid: 'bzip2' |
| 13 |
>>> PORTAGE_BZIP2_COMMAND setting from make.globals is invalid: 'bzip2' |
| 14 |
>>> |
| 15 |
>>> I'm not seeing how python is broken here (works fine), and why |
| 16 |
>>> PORTAGE_BZIP2_COMMAND is invalid. Can someone explain what's going on |
| 17 |
>>> here? |
| 18 |
>> |
| 19 |
>> Since there is such a command, is it possible (and worthwhile) to use |
| 20 |
>> lbzip2 instead of bzip2 with portage? (lbzip2 is ridiculously fast when |
| 21 |
>> you have the cores and the RAM ...) |
| 22 |
>> |
| 23 |
>> |
| 24 |
> |
| 25 |
> What is the difference between theese two? : |
| 26 |
> ---- |
| 27 |
> * app-arch/lbzip2 |
| 28 |
> Available versions: 2.3-r1 ~2.5 {debug symlink} |
| 29 |
> Homepage: https://github.com/kjn/lbzip2/ |
| 30 |
> Description: Parallel bzip2 utility |
| 31 |
> |
| 32 |
> [I] app-arch/pbzip2 |
| 33 |
> Available versions: 1.1.12 ~1.1.12-r1 ~1.1.13 {static symlink} |
| 34 |
> Installed versions: 1.1.12(kl. 16.51 +0100 09. nov. 2016)(symlink |
| 35 |
> -static) |
| 36 |
> Homepage: http://compression.ca/pbzip2/ |
| 37 |
> https://launchpad.net/pbzip2 |
| 38 |
> Description: Parallel bzip2 (de)compressor using libbz2 |
| 39 |
> |
| 40 |
> ---- |
| 41 |
> I just picked one at random. |
| 42 |
> |
| 43 |
|
| 44 |
lbzip2 is generally faster when I looked into it, but it likes gobs of RAM. |
| 45 |
|
| 46 |
Dan |
Archives