It is easier to move the actual header file from  
/usr/armv7a-cros-linux-gnueabi/usr/include/libcxxabi/__cxxabi_config.h
/usr/armv7a-cros-linux-gnueabi/usr/include/libcxxabi/cxxabi.h

to 

/usr/armv7a-cros-linux-gnueabi/usr/include/libcxxabi/include/__cxxabi_config.h
/usr/armv7a-cros-linux-gnueabi/usr/include/libcxxabi/include/cxxabi.h


Would this do the job?

Which configuration is the intended one from upstream? We should probably follow that.

upstream copy the header file over instead of using symbolic link. We probably can do that too.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/e9be242257eb2fe693ce4306a8a7280c7ceac364

commit e9be242257eb2fe693ce4306a8a7280c7ceac364
Author: Yunlian Jiang <yunlian@google.com>
Date: Wed Jul 12 21:24:38 2017

libcxx: remove a symbolic link in the source code.

Android souce tree adds a symbolic link of __cxxabi_config.h
from libcxxabi to libcxx. This causes libcxx install a symbolic
link of __cxxabi_config.h which points to a wrong location.
We do not need that symbolic link and this CL removes that.

BUG= chromium:740232 
TEST=sudo emerge cross-x86_64-cros-linux-gnu/libcxx
     /usr/x86_64-cros-linux-gnu/usr/include/c++/v1/__cxxabi_config.h
     is a real file instead of a symbolic link.

Change-Id: I1b0a727c778463a1100f24a9ee19df63b5039190
Reviewed-on: https://chromium-review.googlesource.com/567521
Commit-Ready: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>
Reviewed-by: Bailey Forrest <bcf@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[rename] https://crrev.com/e9be242257eb2fe693ce4306a8a7280c7ceac364/sys-libs/libcxx/libcxx-4.0.0-r5.ebuild