Bugzilla Bug 213902

+++ This bug was initially created as a clone of Bug #194233 +++

During the compile phase for app-office/plan (version 1.9), gcc is invoked
instead of a CHOST-specific command (like i686-pc-linux-gnu-gcc). This could
cause troubles if trying to do, say, a cross-compile and the system gcc gets
called (since normally it would use the CHOST for the cross compiler).

Reproducible: Always

Steps to Reproduce:
1. Install app-office/plan
2. Look at output during either the configure or compile phases
3.

Actual Results:  
gcc is invoked

Expected Results:  
A CHOST-specific compiler name to be invoked

NOTE: A simple ebuild fix and Makefile patch to follow
2nd note: Ebuild also includes minor fix to elog message (ebuild in tree
displays message about version number 1.8 instead of the current version)

Created an attachment (id=146554) [details]
diff between fixed ebuild and one in tree

Created an attachment (id=146555) [details]
patch to fix Makefile to respect ${CC} instead of hardcoded reference to gcc

fixed in cvs (along other things), thanks for the patch.

The patch uses the full path for the file to be patched:
/var/tmp/portage/app-office/plan-1.9/work/plan-1.9/src/Makefile

Please change it to src/Makefile - otherwise, for those of us overriding
PORTAGE_TMPDIR the ebuild fails.

Also, please consider adding the patch to plan-1.9-gentoo.tar.bz2 instead.

Reopening due to comment #4

Created an attachment (id=163917) [details]
Fixed patch

Created an attachment (id=163918) [details]
New diff between current ebuild and one that uses new patch correctly

I fixed the ${P}-makefile.patch in CVS. I did not add it to the patch tarball
as that would involve setting up a versioned tarball system (as is not
presently available, so I would have to push it under a new naming scheme).
Even without the ebuild patch it unpacks and patches fine - it doesn't need the
`cd "${S}"' as long as the path is `plan-1.9/src/Makefile'.