[yocto] Adding gcc-4.5.4 release back into oe-core

Elvis Dowson elvis.dowson at gmail.com
Sat Aug 4 12:25:31 PDT 2012


On Aug 4, 2012, at 11:19 PM, Elvis Dowson wrote:

> Do you think it makes sense to add gcc-4.5.4 back into oe-core, if it turns out that gcc-4.7.2 is causing a lot of issues for some targets?

I'm creating a gcc-4.5 recipe locally, modeling it after the current gcc-4.7 recipe folder. I've taken the patches from the gcc-4.5.1 recipe folder from a previous yocto release, and was wondering for the recent gcc-4.5.4 release, which of these patches can I drop?

SRC_URI = "git://gcc.gnu.org/git/gcc.git;branch=${BRANCH};protocol=git \
	   file://gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch \
	   file://100-uclibc-conf.patch \
           file://gcc-uclibc-locale-ctype_touplow_t.patch \
	   file://cache-amnesia.patch \
	   file://gcc-flags-for-build.patch \
	   file://libstdc++-emit-__cxa_end_cleanup-in-text.patch \
	   file://arm-bswapsi2.patch \
           file://fedora/gcc43-c++-builtin-redecl.patch;striplevel=0 \
           file://fedora/gcc43-ia64-libunwind.patch;striplevel=0 \
           file://fedora/gcc43-java-nomulti.patch;striplevel=0 \
           file://fedora/gcc43-ppc32-retaddr.patch;striplevel=0 \
           file://fedora/gcc43-pr32139.patch;striplevel=0 \
           file://fedora/gcc43-pr33763.patch;striplevel=0 \
           file://fedora/gcc43-rh330771.patch;striplevel=0 \
           file://fedora/gcc43-rh341221.patch;striplevel=0 \
           file://fedora/gcc43-java-debug-iface-type.patch;striplevel=0 \
           file://fedora/gcc43-i386-libgomp.patch;striplevel=0 \
           file://fedora/gcc45-no-add-needed.patch;striplevel=0 \
           file://103-uclibc-conf-noupstream.patch  \
           file://200-uclibc-locale.patch  \
           file://203-uclibc-locale-no__x.patch; \
           file://204-uclibc-locale-wchar_fix.patch; \
           file://205-uclibc-locale-update.patch; \
           file://301-missing-execinfo_h.patch  \
           file://302-c99-snprintf.patch  \
           file://303-c99-complex-ugly-hack.patch  \
           file://304-index_macro.patch  \
           file://305-libmudflap-susv3-legacy.patch  \
           file://306-libstdc++-namespace.patch  \
           file://740-sh-pr24836.patch  \
           file://800-arm-bigendian.patch  \
           file://904-flatten-switch-stmt-00.patch  \
           file://arm-nolibfloat.patch  \
           file://arm-softfloat.patch \
           file://zecke-xgcc-cpp.patch \
           file://gcc-poison-system-directories.patch \
           file://gcc-poison-dir-extend.patch \
           file://gcc-4.3.3-SYSROOT_CFLAGS_FOR_TARGET.patch \
	   file://64bithack.patch \
	   file://optional_libstdc.patch \
	   file://disable_relax_pic_calls_flag.patch \
	   file://GPLUSPLUS_INCLUDE_DIR_with_sysroot.patch \
	   file://COLLECT_GCC_OPTIONS.patch \
	   file://use-defaults.h-and-t-oe-in-B.patch \
	   file://pr43810.patch \
	   file://pr44290.patch \
	   file://pr44606.patch \
	   file://pr45094.patch \
	   file://pr45052.patch \
	   file://pr45886.patch \
	   file://pr44618.patch \
	  "

SRC_URI_append_sh3  = " file://sh3-installfix-fixheaders.patch "

I notice that around 60 to 70% of the above patches are still applied to the gcc-4.7 recipe, so I was wondering how one maintains this recipe.

Best regards,

Elvis Dowson



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20120804/ec89fd3b/attachment.html>


More information about the yocto mailing list