Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 36919 - fcron dies when trying to detect vim on a hardened-gcc compiled system
Summary: fcron dies when trying to detect vim on a hardened-gcc compiled system
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High blocker
Assignee: John Davis (zhen) (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-31 14:34 UTC by John Davis (zhen) (RETIRED)
Modified: 2004-04-19 01:33 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
fcron-2.0.0-r4.ebuild fixup (fcron-2.0.0-r4.ebuild.diff,505 bytes, patch)
2004-01-01 14:46 UTC, solar (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description John Davis (zhen) (RETIRED) gentoo-dev 2003-12-31 14:34:42 UTC
on ./configure, fcron fails to detect that /usr/bin/vim is an executable because it is a shared object thanks to hardened-gcc (and -pie).

Reproducible: Always
Steps to Reproduce:
1. hardened-gcc -A
2. emerge fcron
3.
Comment 1 solar (RETIRED) gentoo-dev 2004-01-01 14:46:04 UTC
Created attachment 22979 [details, diff]
fcron-2.0.0-r4.ebuild fixup
Comment 2 solar (RETIRED) gentoo-dev 2004-01-01 14:49:52 UTC
I don't think hgcc has anything to do with this from my tests.

What I think is happening here is the full path to your editor is probably not 
being passed at build time. I've attached a patch which I think would resolve 
this problem for everybody affected. If working then please test and then 
reassign bug to base if needed and or get us permission to add the fix.


 src_compile() {
+	EDITOR=$(type -path ${EDITOR})
+
Comment 3 solar (RETIRED) gentoo-dev 2004-01-08 02:21:06 UTC
zhen, 
show me some love here does the fix work or not?
Comment 4 John Davis (zhen) (RETIRED) gentoo-dev 2004-02-23 22:25:17 UTC
i think that this was more of a catalyst bug.
Comment 5 Fabrice Aneche 2004-04-19 01:33:53 UTC
This error is not related to hardened-gcc at all, I've got the same error on basic install, I've just changed the /etc/rc.conf to EDITOR="/usr/bin/vim".
So this is related to the way how fcron configure look for vi/vim.