From: "copiousfreetime (Jeremy Hinegardner)" Date: 2013-10-30T02:46:50+09:00 Subject: [ruby-core:58069] [ruby-trunk - Bug #9058][Open] compilation fails with -DGC_PROFILE_MORE_DETAIL Issue #9058 has been reported by copiousfreetime (Jeremy Hinegardner). ---------------------------------------- Bug #9058: compilation fails with -DGC_PROFILE_MORE_DETAIL https://bugs.ruby-lang.org/issues/9058 Author: copiousfreetime (Jeremy Hinegardner) Status: Open Priority: Normal Assignee: nobu (Nobuyoshi Nakada) Category: build Target version: ruby -v: 2.0.0-p247 Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN =begin Building ruby-2.0.0-p247 from source Configure % CFLAGS=-DGC_PROFILE_MORE_DETAIL ./configure --disable-install-doc --disable-install-rdoc --prefix=/opt/rubies/ruby-2.0.0-p247-gc # omitted Make % make CC = clang LD = ld LDSHARED = clang -dynamic -bundle CFLAGS = -DGC_PROFILE_MORE_DETAIL -pipe XCFLAGS = -include ruby/config.h -include ruby/missing.h -D_FORTIFY_SOURCE=2 -fstack-protector -fno-strict-overflow -fvisibility=hidden -DRUBY_EXPORT -fPIE CPPFLAGS = -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT -I. -I.ext/include/x86_64-darwin12.5.0 -I./include -I. DLDFLAGS = -Wl,-undefined,dynamic_lookup -Wl,-multiply_defined,suppress -fstack-protector -Wl,-u,_objc_msgSend -Wl,-pie SOLIBS = compiling main.c compiling dmydln.c compiling dmyencoding.c compiling version.c compiling dmyversion.c compiling miniprelude.c translating probes probes.d . ./vm_opts.h compiling array.c compiling bignum.c compiling class.c compiling compar.c compiling complex.c compiling dir.c compiling dln_find.c compiling enum.c compiling enumerator.c generating known_errors.inc known_errors.inc updated compiling error.c compiling eval.c compiling load.c compiling proc.c compiling file.c compiling gc.c gc.c:4089:34: error: no member named 'live_num' in 'struct rb_objspace::' size_t live = objspace->heap.live_num; ~~~~~~~~~~~~~~ ^ 1 error generated. make: *** [gc.o] Error 1 This appears to be possibly fixed in head, I want to make sure that this is fixed in the next release of 2.0. -- http://bugs.ruby-lang.org/