ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2025-03-22 12:05:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

scripts/internals: do not remove lib{32,64}/ symlinks after build

Browse Source 
During the build, we create lib{32,64}/ symlinks out of the sysroot.
In some cases (eg. mingw32 target), these symlinks are still required
when running the toolchain. For other combinations, the symlinks are
without incidence, so they can be safely kept after the build.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
This commit is contained in:
Yann E. MORIN" 2011-04-15 00:22:42 +02:00
parent 5de61c8032
commit 21247bddbf
1 changed files with 2 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
scripts/build/internals.sh
View File

@ -114,18 +114,8 @@ do_finish() {
# The symlinks are needed only during the build process.
# The final gcc will still search those dirs, but will also search
# the standard lib/ dirs, so we can get rid of the symlinks
for d in \
"${CT_PREFIX_DIR}" \
"${CT_PREFIX_DIR}/${CT_TARGET}" \
; do
CT_DoExecLog ALL rm -f "${d}/lib32"
CT_DoExecLog ALL rm -f "${d}/lib64"
done
# Also remove the lib/ symlink out-side of sysroot
if [ "${CT_USE_SYSROOT}" = "y" ]; then
CT_DoExecLog ALL rm -f "${CT_PREFIX_DIR}/${CT_TARGET}/lib"
fi
CT_DoExecLog ALL rm -f "${CT_PREFIX_DIR}/lib32"
CT_DoExecLog ALL rm -f "${CT_PREFIX_DIR}/lib64"
CT_EndStep
}