Here is the output: >>> emerge (2 of 4) dev-util/xmingw-gcc-3.3.1 to / >>> md5 src_uri ;-) gcc-3.3.1.tar.bz2 >>> md5 src_uri ;-) gcc-3.3.1-20030804-1-src.diff.gz >>> md5 src_uri ;-) mingw-runtime-3.2-src.tar.gz >>> md5 src_uri ;-) w32api-2.4-src.tar.gz >>> Unpacking source... >>> Unpacking gcc-3.3.1.tar.bz2 to /var/tmp/portage/xmingw-gcc-3.3.1/work >>> Unpacking mingw-runtime-3.2-src.tar.gz to /var/tmp/portage/xmingw-gcc-3.3.1/work >>> Unpacking w32api-2.4-src.tar.gz to /var/tmp/portage/xmingw-gcc-3.3.1/work patching file boehm-gc/win32_threads.c Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file boehm-gc/win32_threads.c.rej patching file boehm-gc/include/gc.h Hunk #1 FAILED at 895. 1 out of 1 hunk FAILED -- saving rejects to file boehm-gc/include/gc.h.rej patching file config/mh-mingw32 patching file gcc/Makefile.in The compilation runs well. But i think there's no harm to file a bug about this ;)
Ok, here is the info: ./gcc-3.3.1/boehm-gc/include/gc.h.rej is a white space change ( a single space was added ). ./gcc-3.3.1/boehm-gc/win32_threads.c.rej is a already applied. This came about because the patch at mingw.org was not form the 3.3.1 release, but a couple of chages off! A info message will be added to the ebuild to inform the user that the warning / errors are expected. Thanks, Stefan