public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mexas at bristol dot ac.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/53964] regression: sparc64 FreeBSD: /usr/ports/lang/gcc46/work/build/./prev-gcc/include/stddef.h:150:26: error: two or more data types n declaration specifiers Date: Wed, 23 Jan 2013 10:15:00 -0000 [thread overview] Message-ID: <bug-53964-4-MxgR9L7daC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53964-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53964 --- Comment #7 from Anton Shterenlikht <mexas at bristol dot ac.uk> 2013-01-23 10:14:52 UTC --- a great miracle happened here: # pkg info -xo gcc-4.6 gcc-4.6.4.20121123: lang/gcc46 # I didn't have to do anything extra to get it build. However, I'm getting this error using the new 4.6 compiler to build lapack: gfortran46 -O -Wl,-rpath=/usr/local/lib/gcc46 -fPIC -c LAPACK_version.f -o LAPACK_version.o gfortran46 -Wl,-rpath=/usr/local/lib/gcc46 -fPIC -o testlsame lsame.o lsametst.o /usr/local/lib/gcc46/gcc/sparc64-portbld-freebsd10.0/4.6.4/../../../libgfortran.so: undefined reference to `__emutls_v._ThreadRuneLocale' collect2: ld returned 1 exit status *** [testlsame] Error code 1
next prev parent reply other threads:[~2013-01-23 10:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-14 16:18 [Bug regression/53964] New: " mexas at bristol dot ac.uk 2012-07-15 10:50 ` [Bug regression/53964] " mexas at bristol dot ac.uk 2012-07-15 11:00 ` mexas at bristol dot ac.uk 2012-07-15 13:23 ` gerald at pfeifer dot com 2012-07-15 13:58 ` mexas at bristol dot ac.uk 2012-09-04 16:09 ` mexas at bristol dot ac.uk 2012-09-05 8:44 ` mexas at bristol dot ac.uk 2013-01-23 10:15 ` mexas at bristol dot ac.uk [this message] 2013-06-06 8:52 ` mexas at bristol dot ac.uk 2013-06-10 7:59 ` mexas at bristol dot ac.uk
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=bug-53964-4-MxgR9L7daC@http.gcc.gnu.org/bugzilla/ \ --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).