Am 10.01.2014 09:23, schrieb Zhenqiang Chen: > Hi, > > MULTIARCH_DIRNAME was removed @r196649 since the dir info had been > combined in MULTILIB_OSDIRNAMES. > > But MULTIARCH_DIRNAME was re-added @r201164. With this change, the > final multiarch_dir is combined as > "aarch64-linux-gnu:aarch64-linux-gnu", which is incorrect and leads to > multiarch build fail if the sysroot is in correct multiarch layout. > > Any reason to add MULTIARCH_DIRNAME? If it is not necessary, can we > remove it as the patch?
see the thread "[patch] set MULTIARCH_DIRNAME for multilib architectures" from June 2013. I think it is necessary to have the default defined. Yesterday's build looks ok for me, looking at default and include paths, so maybe I don't yet understand the issue. I think aarch64 is the only architecture which introduces MULTILIB_* macros without actually building any multilib, just to set the default library name to lib64. So maybe this has some side effects. Matthias
