icecream-create-env, when creating a tarball for a different target architecture, uses the environment variable ${CHOST}, which is blank instead of set to the correct CHOST. This causes icecream-create-env to fail. Setting the CHOST on the command line before running icecream-create-env works fine. Reproducible: Always Steps to Reproduce: 1. crossdev -t sparc-unknown-linux-gnu 2. icecream-create-env sparc-unknown-linux-gnu 3. CHOST="i686-pc-linux-gnu" icecream-create-env sparc-unknown-linux-gnu Actual Results: Step 2 fails, step 3 works. Expected Results: Step 2 works, with the addition in step 3 unnecessary.
Not sure if this is a bug or a feature. The documentation at http://dev.gentoo.org/~bluebird/icecream.xml?style=printable includes instructions to prepend CHOST=<host's chost> to the command line. However, the documentation here: http://dev.gentoo.org/~bluebird/icecream.xml?style=printable makes no mention of it. Either way, the proposed patch here from bug 275756 fixes this issue.
This seems to be what I ran into here: http://forums.gentoo.org/viewtopic-t-789604-highlight-icecream.html Just ran into this issue again today. So looks like I'm in the same boat here and would appreciate a permanent fix.
(In reply to comment #1) > Not sure if this is a bug or a feature. Yeah, it seems to be a feature, since CHOST is only used to construct the correct path. I also would prefer to have this fixed in the script.
Created attachment 234875 [details, diff] Proposed patch that suppress the need to define CHOST
Thanks for bugreport and patch guys, applied.
