That's too bad... if gc gets dropped, won't this cause trouble for packages depending on gc, like inkscape? I guess one could keep a legacy version of gc that is known to work.
Jens On Jul 21, 2007, at 9:53 AM, David R. Morrison wrote: > In addition to this XCode issue, I've received a few private bug > reports about the new gc package. If I can't resolve them soon, I > may remove the package from fink. > > -- Dave > > > On Jul 19, 2007, at 3:05 PM, Jens Noeckel wrote: > >> Hi, >> >> gc (7.0-1001) compiles fine with XCode 2.4 on an Intel Core Duo >> machine, but fails to compile on the same architecture with Xcode >> 2.3, where I have gcc version: i686-apple-darwin8-gcc-4.0.1 (GCC) >> 4.0.1 (Apple Computer, Inc. build 5341). >> >> I guess this is again related to the question of having an xcode >> virtual package to keep track of the required XCode Tools version >> (discussed recently on this list). >> Right now the build on XCode 2.3 fails with an error that won't >> tell people how to fix the problem (see below). >> It would perhaps be good to have a warning, "compiler out of >> date", to remind people to update their XCode. I think some >> packages do this, but can't recall where I've seen this before. >> Maybe this is just hand-coded as a test in the .info file somehow? >> >> Jens >> >> >> Here is the error message I get building gc on Mac Intel Core Duo >> (10.4.10) and XCode 2.3: >> >> gcc -DPACKAGE_NAME=\"gc\" -DPACKAGE_TARNAME=\"gc\" - >> DPACKAGE_VERSION=\"7.0\" "-DPACKAGE_STRING=\"gc 7.0\"" - >> DPACKAGE_BUGREPORT=\"[EMAIL PROTECTED]" -DGC_VERSION_MAJOR=7 - >> DGC_VERSION_MINOR=0 -DPACKAGE=\"gc\" -DVERSION=\"7.0\" - >> DGC_DARWIN_THREADS=1 -DTHREAD_LOCAL_ALLOC=1 -DSTDC_HEADERS=1 - >> DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 - >> DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 - >> DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 - >> DHAVE_DLFCN_H=1 -DNO_EXECUTE_PERMISSION=1 - >> DALL_INTERIOR_POINTERS=1 -DGC_GCJ_SUPPORT=1 -DJAVA_FINALIZATION=1 - >> DATOMIC_UNCOLLECTABLE=1 -I./include -fexceptions -I ./ >> libatomic_ops/src -fno-common -DGC_DARWIN_THREADS -DLARGE_CONFIG - >> g -UNO_DEBUGGING -I/sw/include -MT os_dep.lo -MD -MP -MF .deps/ >> os_dep.Tpo -c os_dep.c -fno-common -DPIC -o .libs/os_dep.o >> os_dep.c: In function 'GC_dirty_init': >> os_dep.c:3749: error: 'x86_THREAD_STATE32' undeclared (first use >> in this function) >> os_dep.c:3749: error: (Each undeclared identifier is reported only >> once >> os_dep.c:3749: error: for each function it appears in.) >> os_dep.c: In function 'catch_exception_raise': >> os_dep.c:3869: error: 'x86_EXCEPTION_STATE32' undeclared (first >> use in this function) >> os_dep.c:3870: error: 'x86_EXCEPTION_STATE32_COUNT' undeclared >> (first use in this function) >> os_dep.c:3871: error: 'x86_exception_state32_t' undeclared (first >> use in this function) >> os_dep.c:3871: error: parse error before 'exc_state' >> os_dep.c:3891: error: 'exc_state' undeclared (first use in this >> function) >> make[1]: *** [os_dep.lo] Error 1 >> make: *** [all-recursive] Error 1 >> ### execution of make failed, exit code 2 >> Removing runtime build-lock... >> Removing build-lock package... >> /sw/bin/dpkg-lockwait -r fink-buildlock-gc-7.0-1001 >> (Reading database ... 168161 files and directories currently >> installed.) >> Removing fink-buildlock-gc-7.0-1001 ... >> Failed: phase compiling: gc-7.0-1001 failed >> > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fink-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
