| Summary: | Explicitly call gpatch | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | C. <cbergstrom> |
| Component: | Eclasses | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Solaris | ||
| URL: | http://archives.gentoo.org/gentoo-dev/msg_01c84a2bb36ed6f8561ad97d9aec9270.xml | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
As seen on [URL]. have your profile/system hijack `patch` to go to GNU patch just like is done with sed -> gsed |
We depend on gnu patch.. Calling explicitly gpatch instead of patch avoids problems on arches where both are installed. There's a few instances of this in eclass/eutils.eclass if (cat ${PATCH_TARGET} | patch -p${count} ${popts} --dry-run -f ; _epatch_assert) >> ${ST DERR_TARGET%/*}/${patchname}-${STDERR_TARGET##*/} 2>&1 if (cat ${PATCH_TARGET} | gpatch -p${count} ${popts} --dry-run -f ; _epatch_assert) >> ${ST DERR_TARGET%/*}/${patchname}-${STDERR_TARGET##*/} 2>&1 Reproducible: Always