| Summary: | sys-devel/gcc-4.5.4-r2 fails to apply patch 101_all_libjava-ucontext.patch | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Cyp <cyp561> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | /var/tmp/portage/sys-devel/gcc-4.5.4-r2/temp/101_all_libjava-ucontext.patch.out | ||
Created attachment 582014 [details]
/var/tmp/portage/sys-devel/gcc-4.5.4-r2/temp/101_all_libjava-ucontext.patch.out
Attaching with content type auto-detect says:
“The content type chemical/x-gulp is invalid. Valid types must be of the form foo/bar where foo is one of application, audio, image, message, model, multipart, text, video and bar must not contain any special characters (such as "=", "?", ...).”
* Failed Patch: 101_all_libjava-ucontext.patch ! * ( /etc/portage/patches/sys-devel/gcc:4.5.4/101_all_libjava-ucontext.patch ) That's your local patch. Oh, sorry. Removing it worked, thanks. |
* Failed Patch: 101_all_libjava-ucontext.patch ! * ( /etc/portage/patches/sys-devel/gcc:4.5.4/101_all_libjava-ucontext.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-devel/gcc-4.5.4-r2/temp/101_all_libjava-ucontext.patch.out * ERROR: sys-devel/gcc-4.5.4-r2::gentoo failed (prepare phase): * Failed Patch: 101_all_libjava-ucontext.patch! * * Call stack: * ebuild.sh, line 124: Called src_prepare * environment, line 3437: Called toolchain_src_prepare * environment, line 4843: Called epatch_user * environment, line 1239: Called epatch * environment, line 1211: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * * If you need support, post the output of `emerge --info '=sys-devel/gcc-4.5.4-r2::gentoo'`, * the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.5.4-r2::gentoo'`. * The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.5.4-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.5.4-r2/temp/environment'. * Working directory: '/var/tmp/portage/sys-devel/gcc-4.5.4-r2/work/gcc-4.5.4' * S: '/var/tmp/portage/sys-devel/gcc-4.5.4-r2/work/gcc-4.5.4'