The current way links is built is wrong because it has "gcc" hardcoded in the Makefiles (or somewhere else?). It just doesn't take CBUILD and CHOST into account which results in broken binaries (cannot be run on target system).
Created attachment 59804 [details, diff] links-2.1_pre17-r2.ebuild.diff I took a look at the configure script and found this: if test -n "$CC"; then ac_cv_prog_CC="$CC" # Let the user override the test. Thus perhaps setting CC before the configure script is run fixes it? Please tell me if this patch works for you.
AFAIK setting CC worked for me but this is not an acceptable solution. Portage itself should take care of build/target architecture so one can emerge world for another arch without dealing with this... P.S.: Sorry, can't test it now as my system is not prepared... :-(
(In reply to comment #2) > Portage itself should take care... Yep, that's why I'm adding export CC="$(tc-getCC)" to the ebuild, it should define CC so that you don't have to. > P.S.: Sorry, can't test it now as my system is not prepared... :-( No problem. Let me know when you can so that we can sort this out :-).
OK, thanks. Will try ASAP...
This patch seem to work as expected, please include. Don't have a machine to try it on but in case it won't work, I'll reopen this one.
Alright, adding it to -r2. Thanks for reporting.
