Summary: | fcron dies when trying to detect vim on a hardened-gcc compiled system | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Davis (zhen) (RETIRED) <zhen> |
Component: | [OLD] Core system | Assignee: | John Davis (zhen) (RETIRED) <zhen> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | base-system |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | fcron-2.0.0-r4.ebuild fixup |
Description
John Davis (zhen) (RETIRED)
![]() Created attachment 22979 [details, diff]
fcron-2.0.0-r4.ebuild fixup
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}) + zhen, show me some love here does the fix work or not? i think that this was more of a catalyst bug. 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. |