I'm thinking about changing the way we build packages in separate
directories. What we do now for tool chain packages is:
mkdir -v ../binutils-build
cd ../binutils-build
../binutils-2.25.1/configure ...
I'm thinking about changing that to:
mkdir -v build
cd build
../configure ...
========
The rationale is that it moves the build directory to inside the extracted
package tree and avoids the necessary removal of the separate
package-build directory. It's a little less confusing when removing the
directory after a package is complete.
The change is also more consistent with the packages in BLFS (virtually
all the cmake based packages) that build in separate directories.
The packages affected are:
chapter05/binutils-pass{1,2}
chapter05/gcc-pass{1,2}
chapter05/glibc
chapter05/libstdc++
chapter06/binutils
chapter06/gcc
chapter06/glibc
I've tested this for the Chapter 5 packages so far and there is no
indication of a problem. I'm going to test the Chapter 6 packages in the
next couple of hours.
What do you think?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
