fpc-2.4.4 fails to compile when there is no default config file. That is, if there are no /usr/lib/fpc/${FPCVER}/samplecfg and "${PPC_CONFIG_PATH}"/fpc.cfg in the directory, then the compilation fails. The offending commands in the ebuild are: if ! test ${PPC_CONFIG_PATH+set}; then local FPCVER="${PV}" export PPC_CONFIG_PATH="${WORKDIR}" sed -e 's/^FPBIN=/#&/' /usr/lib/fpc/${FPCVER}/samplecfg | sh -s /usr/lib/fpc/${FPCVER} "${PPC_CONFIG_PATH}" || die sed -i -e '/^-Xs/d' "${PPC_CONFIG_PATH}"/fpc.cfg || die fi Reproducible: Always Once I commented the offending comments, the compilation succeeded AND the config files are created in the expected places. Subsequent compilation with the offending commands uncommented will succeed. This suggests that the if check is faulty.
Same here. Re-assigning to who did the bump to 2.4.4. Feel free to revert if you dislike that choice. A more end-user view of things: ===================================================== [..] >>> Preparing source in /var/tmp/portage/dev-lang/fpc-2.4.4/work/fpcbuild-2.4.4/fpcsrc ... sed: can't read /usr/lib/fpc/2.4.4/samplecfg: No such file or directory sed: can't read /var/tmp/portage/dev-lang/fpc-2.4.4/work/fpc.cfg: No such file or directory * ERROR: dev-lang/fpc-2.4.4 failed (prepare phase): * (no error message) * * Call stack: * ebuild.sh, line 84: Called src_prepare * environment, line 245: Called die * The specific snippet of code: * sed -i -e '/^-Xs/d' "${PPC_CONFIG_PATH}"/fpc.cfg || die; [..] ===================================================== Is src_prepare even supposed to fix files outside of ${WORKDIR} ? Looks like a conceptual problem (not a missing file) to me.
Ah, the nasty ide stuff broke. No surprise there.
(In reply to comment #1) > Is src_prepare even supposed to fix files outside of ${WORKDIR} ? > Looks like a conceptual problem (not a missing file) to me. It's not altering files outside of ${WORKDIR} if you take a closer look and anyway that should be stopped by sandbox.
Fixed in CVS.
(In reply to comment #3) > It's not altering files outside of ${WORKDIR} if you take a closer look The error on /usr/lib/fpc/2.4.4/samplecfg puzzles me. What's your explanation for it? > and > anyway that should be stopped by sandbox. True. (In reply to comment #4) > Fixed in CVS. Thanks.
(In reply to comment #5) > (In reply to comment #3) > > It's not altering files outside of ${WORKDIR} if you take a closer look > > The error on /usr/lib/fpc/2.4.4/samplecfg puzzles me. > What's your explanation for it? It looks like the previous code was modifying the output of the samplecfg command installed on the local filesystem with sed not the actual file itself.
