[lfs-dev] bc ready
martyj19 at comcast.net
Mon Jul 15 03:14:57 PDT 2019
On 07/14/2019 10:01 PM, Bruce Dubbs via lfs-dev wrote:
> I've added your version of bc to LFS. I have one minor issue. When the tests are run, there is no indication of the results. There is a long list of activities, but I assume that a lack of failure notices means success. A notice of how many tests passed and/or failed would be nice.
> -- Bruce
> On 7/8/19 12:56 PM, Gavin Howard via lfs-dev wrote:
>> I am the author of the bc that is going to be put in
>> (http://wiki.linuxfromscratch.org/lfs/ticket/4436), and it's time for
>> me to say that it is ready to be put in. The reason: I believe that it
>> is complete, so I have switched from active development to active
>> The instructions are still the same:
>> <<Begin instructions>>
>> Prepare Bc for compilation:
>> PREFIX=/usr CC=gcc CFLAGS="-std=c99" ./configure.sh -G -O3
>> The meaning of the configure options:
>> * PREFIX=/usr
>> Like --prefix in other packages.
>> * CC=gcc
>> Set the C compiler. This package defaults to c99, which doesn't exist.
>> * CFLAGS="-std=c99"
>> Sets the C standard that gcc uses to be C99.
>> * -G
>> Disables tests in the test suite that requires another bc to
>> generate results for.
>> * -O3
>> Enables optimization. This bc gets an order of magnitude more
>> performance from optimizations, and these optimizations have been
>> Compile the package:
>> If desired, test bc:
>> make test
>> Install the package:
>> make install
>> <<End instructions>>
>> The URL to download from is:
>> Checksums are below.
>> $ sha512sum bc-2.1.0.tar.xz
>> $ sha256sum bc-2.1.0.tar.xz
>> $ stat -c '%s %n' bc-2.1.0.tar.xz
>> 153912 bc-2.1.0.tar.xz
>> I would be happy to help integrate this into LFS.
>> Gavin Howard
I will be continuing to run the GNU version of bc. While the version you now have in the book may be a totally impressive piece of work, until it is picked up by one or more major distros, it is not suitable for my system.
Compare to the situation with libjpeg-turbo, which completely overtook libjpeg. Why you would make choices that make your build less mainstream is not clear. There's been no discussion of this that I am aware of.
More information about the lfs-dev