public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38268] gfortran doesn't link any 64 bits binaries on Solaris
Date: Wed, 03 Dec 2008 09:14:00 -0000 [thread overview]
Message-ID: <20081203091241.27870.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38268-12750@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from ebotcazou at gcc dot gnu dot org 2008-12-03 09:12 -------
> gcc -g -fkeep-inline-functions -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 -fno-common -DHAVE_CONFIG_H -o
> cc1-dummy c-lang.o stub-objc.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o
> c-typeck.o c-convert.o c-aux-info.o c-common.o c-opts.o c-format.o
> c-semantics.o c-ppoutput.o c-cppbuiltin.o c-objc-common.o c-dump.o c-pch.o
> c-parser.o i386-c.o sol2-c.o c-gimplify.o tree-mudflap.o c-pretty-print.o
> c-omp.o dummy-checksum.o \
> main.o tree-browser.o libbackend.a ../libcpp/libcpp.a
> ../libdecnumber/libdecnumber.a ../libcpp/libcpp.a -lintl -liconv
> ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -L/usr/lib -L/usr/lib
> -lmpfr -lgmp -L/usr/lib -L/usr/lib -lmpfr -lgmp
> Undefined first referenced
> symbol in file
> libintl_gettext c-decl.o
> libintl_textdomain libbackend.a(intl.o)
> libintl_bindtextdomain libbackend.a(intl.o)
> libintl_dgettext ../libcpp/libcpp.a(errors.o)
> ld: fatal: Symbol referencing errors. No output written to cc1-dummy
> collect2: ld returned 1 exit status
> gnu-make[3]: *** [cc1-dummy] Error 1
> gnu-make[3]: Leaving directory `/home/delisle/gcc/obj44/gcc'
> gnu-make[2]: *** [all-stage1-gcc] Error 2
> gnu-make[2]: Leaving directory `/home/delisle/gcc/obj44'
> gnu-make[1]: *** [stage1-bubble] Error 2
> gnu-make[1]: Leaving directory `/home/delisle/gcc/obj44'
> gnu-make: *** [all] Error 2
Ah, yes, this is a classical one, see PR bootstrap/12482. You can work around
it by passing --disable-nls to the configure script.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38268
next prev parent reply other threads:[~2008-12-03 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 21:47 [Bug fortran/38268] New: " mt1 at systella dot fr
2008-11-26 3:54 ` [Bug fortran/38268] " jvdelisle at gcc dot gnu dot org
2008-11-26 7:19 ` mt1 at systella dot fr
2008-11-26 7:50 ` ebotcazou at gcc dot gnu dot org
2008-11-26 8:07 ` ebotcazou at gcc dot gnu dot org
2008-11-26 8:28 ` mt1 at systella dot fr
2008-11-26 11:41 ` ebotcazou at gcc dot gnu dot org
2008-12-03 4:08 ` jvdelisle at gcc dot gnu dot org
2008-12-03 9:14 ` ebotcazou at gcc dot gnu dot org [this message]
2008-12-05 5:47 ` jvdelisle at gcc dot gnu dot org
2008-12-05 7:41 ` ebotcazou at gcc dot gnu dot org
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=20081203091241.27870.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: link
Be 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).