gcc-cross: Use MULTIMACH_TARGET_SYS instead of TARGET_SYS in staging path

Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
This commit is contained in:
Richard Purdie 2010-07-23 14:35:37 +01:00
parent 3f5d3d7b99
commit 989d2f794f
2 changed files with 2 additions and 2 deletions

View File

@ -33,7 +33,7 @@ do_compile () {
do_install () {
# Install libgcc from our gcc-cross saved data
install -d ${D}${base_libdir} ${D}${libdir}
cp -fpPR ${STAGING_INCDIR_NATIVE}/gcc-build-internal-${TARGET_SYS}/* ${D}
cp -fpPR ${STAGING_INCDIR_NATIVE}/gcc-build-internal-${MULTIMACH_TARGET_SYS}/* ${D}
for d in ${RUNTIMETARGET}; do
cd ${B}/$d/

View File

@ -18,7 +18,7 @@ do_install () {
# gcc-runtime installs libgcc into a special location in staging since it breaks doing a standalone build
if [ "${PN}" == "gcc-cross" -o "${PN}" == "gcc-crosssdk" ]; then
dest=${D}/${includedir}/gcc-build-internal-${TARGET_SYS}
dest=${D}/${includedir}/gcc-build-internal-${MULTIMACH_TARGET_SYS}
oe_runmake "DESTDIR=$dest" libdir=${target_libdir} base_libdir=${target_base_libdir} prefix=${target_prefix} exec_prefix=${target_exec_prefix} install-target-libgcc
# Ideally here we'd override the libgcc Makefile's idea of slibdir but