I didn't investigate other formats of patch, e.g. I don't known if it would be feasible since gcc has patches. To libsoil (either use diff 3.2 or manually remove the quotes from the 'Format and licensing of the package patches' the workaround needed whenĪ file changed by a patch has spaces in its name, apply the workaround V2.5.9 is from 2004 ), address on the manual Solution 2: Add patch >= 2.5.9 as prerequisite to the manual (patch Solution 1: Add patch >= 2.7 as prerequisite to the manual (patch v2.7 Patch >= 2.7 can handle both quoted and unquoted filenames
Patch >= 2.5.9 can handle unquoted filenames The tool 'patch' can handle patches with spaces in the name of aĬhanged file depending on the tool version: The output of "diff -purN" when there are spaces in the name of aĬhanged file depends on the tool version:ĭiff = v3.3 adds double quotes to filenames |diff -uNr "/projects/makefile/alternate Makefile.txt" "soil/projects/makefile/alternate Makefile.txt" |Various makefile fixes to allow cross compilation Perhaps you used the wrong -p or -strip option? Patch failed! Please fix 0001-fix-makefile.patch!Ĭan't find file to patch at input line 11 Libsoil is the only package today that patches a file with space in theĢ out of 2 hunks FAILED - saving rejects to file 'projects/makefile/alternate Makefile.txt".rej' The tool patch needs to be version 2.7 or any later to ensure any patch
When applying a patch generated by diff v3.3 (the newest version ), This error occurs when applying a patch that changes a file with spaces > place on my build server, but it does apply when I test things locally
The patch doesn't apply when the build takes 12:55 ` Thomas Petazzoni 0 siblings, 1 reply 415+ messages in threadįrom: Ricardo Martincoski 12:33 UTC ( / raw) Analysis of build failures All of help / color / mirror / Atom feed * Analysis of build failures 12:33 Ricardo Martincoski
0 kommentar(er)
