I find following dpatch files in the Yocto tree. Dpatch files have a small shell script at the beginning of the patch.
Out of all these, all gcc patches are for all gcc-4.3.3 only, which is kind of outdated stuff now. And will be going out of the tree soon. Binutils & tslib patches are in current use. Adding metadata vars likes upstream_status may break the dpatch format/script. Do we care for the shell script inside the dpatch file? Is it ok to break it inside Yocto tree? meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-012_check_ldrunpath_length.patch meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-001_ld_makefile_patch.patch meta/recipes-devtools/binutils/binutils-2.21/binutils-x86_64_i386_biarch.patch meta/recipes-devtools/binutils/binutils-2.21/binutils-uclibc-300-006_better_file_error.patch meta/recipes-devtools/gcc/gcc-4.5.1/libstdc++-pic.dpatch meta/recipes-devtools/gcc/gcc-4.5.1/arm-unbreak-eabi-armv4t.dpatch meta/recipes-devtools/gcc/gcc-4.5.1/gcc-ice-hack.dpatch meta/recipes-devtools/gcc/gcc-4.5.1/pr30961.dpatch meta/recipes-devtools/gcc/gcc-4.6.0/libstdc++-pic.dpatch meta/recipes-devtools/gcc/gcc-4.6.0/arm-unbreak-eabi-armv4t.dpatch meta/recipes-devtools/gcc/gcc-4.6.0/gcc-ice-hack.dpatch meta/recipes-devtools/gcc/gcc-4.6.0/pr30961.dpatch meta/recipes-devtools/gcc/gcc-4.3.3/300-libstdc++-pic.patch meta/recipes-devtools/gcc/gcc-4.3.3/debian/libstdc++-pic.dpatch meta/recipes-devtools/gcc/gcc-4.3.3/debian/arm-unbreak-eabi-armv4t.dpatch meta/recipes-devtools/gcc/gcc-4.3.3/debian/gcc-ice-hack.dpatch meta/recipes-devtools/gcc/gcc-4.3.3/debian/pr30961.dpatch meta/recipes-graphics/tslib/tslib/32bitBE-support.patch Thanks, Nitin
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
