/usr/lib all over the place, plus the eclass does export LIBDIRPATH="/usr/lib/" among others. Some of these packages are keyworded ~amd64 or even amd64... rox-base/oroborox rox-base/rox-clib rox-base/rox-lib rox-base/rox rox-base/rox-session rox-extra/edit rox-extra/reticker rox.eclass (lots of places) The list above is probably not complete.
*** Bug 155983 has been marked as a duplicate of this bug. ***
As per IRC, the temporary workaround was to include rox in MULTILIB_STRICT_EXEMPT. Since there's nothing more that the amd64 team could do for now, I remove us. Feel free to re-add us if there's a need.
After some careful consideration, I have decided to just change everything over to user /usr/$(get_libdir)/ and let the bugs fly. Committed just moments ago. I honestly don't expect any huge repercussions... I think the only users affected would be those few ~amd64 users whose /usr/lib is not symlinked to the /usr/libxx where rox-lib and/or rox-clib was installed previously. For them, the workaround is to rebuild any affected rox apps. I hope that will do it!
