public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmarkman at mac dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/41180] can not build gcc 4.4.1 on Snow Leopard Mac OS X 10.6 Date: Fri, 28 Aug 2009 14:36:00 -0000 [thread overview] Message-ID: <20090828143617.12392.qmail@sourceware.org> (raw) In-Reply-To: <bug-41180-13994@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from dmarkman at mac dot com 2009-08-28 14:36 ------- thanks for the answer. Here is what I did in the fresh new gcc-4.4.1 folder I issued ./configure --prefix=/home/dmarkman/Development/GCC/macintel64/gcc-4.4.1/build --enable-languages=c,c++ --with-gmp=/home/dmarkman/Development/GCC/macintel64/gmp-4.3.1/build --with-mpfr=/home/dmarkman/Development/GCC/macintel64/mpfr-2.4.1/build -build=x86_64-apple-darwin10.0.0 --host=x86_64-apple-darwin10.0.0 --target=x86_64-apple-darwin10.0.0 and now I got another error: /Volumes/Macintosh_HD/Users/Shared/Development/GCC/gcc-4.4.1/host-x86_64-apple-darwin10.0.0/prev-gcc/xgcc -B/Volumes/Macintosh_HD/Users/Shared/Development/GCC/gcc-4.4.1/host-x86_64-apple-darwin10.0.0/prev-gcc/ -B/home/dmarkman/Development/GCC/macintel64/gcc-4.4.1/build/x86_64-apple-darwin10.0.0/bin/ -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -o cc1plus-dummy \ cp/cp-lang.o stub-objc.o cp/call.o cp/decl.o cp/expr.o cp/pt.o cp/typeck2.o cp/class.o cp/decl2.o cp/error.o cp/lex.o cp/parser.o cp/ptree.o cp/rtti.o cp/typeck.o cp/cvt.o cp/except.o cp/friend.o cp/init.o cp/method.o cp/search.o cp/semantics.o cp/tree.o cp/repo.o cp/dump.o cp/optimize.o cp/mangle.o cp/cp-objcp-common.o cp/name-lookup.o cp/cxx-pretty-print.o cp/cp-gimplify.o tree-mudflap.o attribs.o c-common.o c-format.o c-pragma.o c-semantics.o c-lex.o c-dump.o i386-c.o darwin-c.o c-pretty-print.o c-opts.o c-pch.o incpath.o cppdefault.o c-ppoutput.o c-cppbuiltin.o prefix.o c-gimplify.o c-omp.o tree-inline.o dummy-checksum.o main.o libbackend.a ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a ../libcpp/libcpp.a ./../intl/libintl.a -liconv ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -L/home/dmarkman/Development/GCC/macintel64/gmp-4.3.1/build/lib -L/home/dmarkman/Development/GCC/macintel64/mpfr-2.4.1/build/lib -lmpfr -lgmp ld: duplicate symbol _init_inline_once in libbackend.a(tree-inline.o) and tree-inline.o collect2: ld returned 1 exit status make[3]: *** [cc1plus-dummy] Error 1 make[2]: *** [all-stage2-gcc] Error 2 make[1]: *** [stage2-bubble] Error 2 make: *** [all] Error 2 and BTW, from the gcc-4.4.1 I called command: find . -name *.o | xargs file and I saw that majority of the .o files have x86_64 arch., but there are .o file with i386 (especially from prev-gcc/i386 and i386/libgcc folders) also I did try to build gcc with x86_64 kernel, unfortunately config.guess doesn't guess right, because uname -p still returns i386 only uname -m returns x86_64 I found that very confusing command arch also returns i386 and now I can say that building gcc on x86_64 kernel machine gave me the same duplication error thanks in advance -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41180
next prev parent reply other threads:[~2009-08-28 14:36 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-08-28 3:13 [Bug c++/41180] New: " dmarkman at mac dot com 2009-08-28 3:17 ` [Bug c++/41180] " dmarkman at mac dot com 2009-08-28 10:19 ` redi at gcc dot gnu dot org 2009-08-28 10:23 ` [Bug bootstrap/41180] " redi at gcc dot gnu dot org 2009-08-28 13:28 ` howarth at nitro dot med dot uc dot edu 2009-08-28 14:36 ` dmarkman at mac dot com [this message] 2009-08-28 14:37 ` dmarkman at mac dot com 2009-08-28 15:02 ` redi at gcc dot gnu dot org 2009-08-28 15:12 ` howarth at nitro dot med dot uc dot edu 2009-08-28 15:32 ` howarth at nitro dot med dot uc dot edu 2009-08-28 16:14 ` mrs at gcc dot gnu dot org 2009-08-28 17:28 ` dmarkman at mac dot com 2009-08-29 1:32 ` howarth at nitro dot med dot uc dot edu 2009-08-29 1:41 ` howarth at nitro dot med dot uc dot edu 2009-08-29 2:19 ` howarth at nitro dot med dot uc dot edu 2009-08-31 17:36 ` mrs at apple dot com 2009-08-31 17:38 ` mrs at apple dot com 2009-08-31 18:04 ` howarth at nitro dot med dot uc dot edu 2009-08-31 20:37 ` mrs at apple dot com 2009-09-01 4:00 ` howarth at nitro dot med dot uc dot edu 2009-09-01 4:23 ` howarth at nitro dot med dot uc dot edu 2009-09-02 20:37 ` mrs at apple dot com 2009-09-02 21:41 ` howarth at nitro dot med dot uc dot edu 2009-09-02 21:44 ` howarth at nitro dot med dot uc dot edu 2009-09-02 22:22 ` howarth at nitro dot med dot uc dot edu 2009-09-02 23:37 ` howarth at nitro dot med dot uc dot edu 2009-09-03 0:20 ` mrs at apple dot com 2009-09-03 0:56 ` howarth at nitro dot med dot uc dot edu 2009-09-03 11:04 ` joseph at codesourcery dot com 2009-09-03 13:00 ` howarth at nitro dot med dot uc dot edu 2009-09-04 1:50 ` mrs at apple dot com 2009-09-09 8:15 ` fxcoudert at gcc dot gnu dot org 2009-09-09 8:47 ` fxcoudert at gcc dot gnu dot org 2009-09-30 19:40 ` pinskia at gcc dot gnu dot org 2009-09-30 19:41 ` pinskia at gcc dot gnu dot org [not found] <bug-41180-4@http.gcc.gnu.org/bugzilla/> 2014-02-16 13:14 ` jackie.rosen at hushmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20090828143617.12392.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).