Difference between revisions of "User:Drobbins/CLFS"

From Funtoo
Jump to navigation Jump to search
Line 18: Line 18:
unset CFLAGS CXXFLAGS
unset CFLAGS CXXFLAGS
echo Hello.
echo Hello.
export CLFS_HOST=$(echo ${MACHTYPE} | sed -e 's/-[^-]*/-cross/')
export CLFS_HOST=$(echo ${MACHTYPE} {{!}} sed -e 's/-[^-]*/-cross/')
export CLFS_TARGET="powerpc64-unknown-linux-gnu"
export CLFS_TARGET="powerpc64-unknown-linux-gnu"
export BUILD64="-m64"
export BUILD64="-m64"

Revision as of 04:11, February 9, 2022

Self-Contained CLFS

Getting CLFS building entirely in your existing user's home directory should be possible.

I'm working on cleaning up some things in CLFS, and want to see if we can build everything inside someone's home directory -- creating the /tools and /cross-tools symlinks on the root filesystem is a bit messy. I also want to see if there is a simpler way to create a clean environment than creating a separate clfs user. In theory, this should not be necessary. We can create a clean-room shell environment like this:

    (bash source code)
#!/bin/bash
exec /usr/bin/env -i /bin/bash --noprofile --norc << "EOF"
set +h
umask 022
export HOME=/home/drobbins
export CLFS=$HOME/sexybeast
export CLFS_CROSS_TOOLS=${CLFS}/cross-tools
export D=${CLFS_CROSS_TOOLS}
export LC_ALL=POSIX
export PATH=$CLFS/cross-tools/bin:/bin:/usr/bin
unset CFLAGS CXXFLAGS
echo Hello.
export CLFS_HOST=$(echo ${MACHTYPE} | sed -e 's/-[^-]*/-cross/')
export CLFS_TARGET="powerpc64-unknown-linux-gnu"
export BUILD64="-m64"
cd file-5.19 && ./configure --prefix=/ --disable-static && \
make -j && \
make DESTDIR=${D} install
EOF