public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fragabr at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/56779] [4.8/4.9 Regression] libstdc++.so: undefined reference to `libintl_textdomain' Date: Mon, 20 Jan 2014 19:58:00 -0000 [thread overview] Message-ID: <bug-56779-4-NgUlMolpyt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56779-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56779 --- Comment #18 from Dâniel Fraga <fragabr at gmail dot com> --- (In reply to Jonathan Wakely from comment #15) > (In reply to Dâniel Fraga from comment #14) > Thanks for the quick response, that explains the problem. > > G++ finds the version in /usr/local/include first, so the library gets a > dependency on libintl_textdomain, but the configure checks find textdomain > in glibc, so thinks there is no need to link to libintl. So the solution is to change configure? >From gcc-bugs-return-441056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 20 19:59:50 2014 Return-Path: <gcc-bugs-return-441056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 18771 invoked by alias); 20 Jan 2014 19:59:50 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 18735 invoked by uid 48); 20 Jan 2014 19:59:46 -0000 From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/59888] ld: warning: PIE disabled. Absolute addressing (perhaps -mdynamic-no-pic) not allowed in code signed PIE ... Date: Mon, 20 Jan 2014 19:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dominiq at lps dot ens.fr X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59888-4-Dx3a7bi27j@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59888-4@http.gcc.gnu.org/bugzilla/> References: <bug-59888-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-01/txt/msg02198.txt.bz2 Content-length: 1569 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY888 --- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- When I opened this PR I missed the "-fshared". With it I get the linker error. On IRC Iain Sandoe gives the following workaround: (1) gfc -S F03_iso.f90 (2) apply the following patch: --- F03_iso.s 2014-01-20 20:54:05.000000000 +0100 +++ F03_iso_orig.s 2014-01-20 20:53:06.000000000 +0100 @@ -54,7 +54,7 @@ LCFI4: LCFI5: ret LFE1: - .const + .const_data .align 3 LC2: .quad _compute (3) gfc -shared F03_iso.s -o F03_iso.dylib (4) gfc F03_iso_main.f90 F03_iso.dylib with F03_iso_main.f90 being use F03_ISO_C use, intrinsic :: iso_c_binding implicit none integer :: F03_ISO_C_init integer :: i i = F03_ISO_C_init() print *, i end Then the executable outputs 4493950477 is the address 1 and otool -Lv gives F03_iso.dylib (compatibility version 0.0.0, current version 0.0.0) time stamp 2 Thu Jan 1 01:00:02 1970 /opt/gcc/gcc4.9w/lib/libgfortran.3.dylib (compatibility version 4.0.0, current version 4.0.0) time stamp 2 Thu Jan 1 01:00:02 1970 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1) time stamp 2 Thu Jan 1 01:00:02 1970 /opt/gcc/gcc4.9w/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) time stamp 2 Thu Jan 1 01:00:02 1970 /opt/gcc/gcc4.9w/lib/libquadmath.0.dylib (compatibility version 1.0.0, current version 1.0.0) time stamp 2 Thu Jan 1 01:00:02 1970
next prev parent reply other threads:[~2014-01-20 19:58 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-29 12:55 [Bug libstdc++/56779] New: " treeve at sourcemage dot org 2013-04-02 9:06 ` [Bug libstdc++/56779] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org 2013-05-31 10:58 ` jakub at gcc dot gnu.org 2013-06-25 18:44 ` fragabr at gmail dot com 2013-08-24 2:04 ` fragabr at gmail dot com 2013-10-16 9:51 ` jakub at gcc dot gnu.org 2013-10-17 0:17 ` fragabr at gmail dot com 2013-10-25 12:46 ` rguenth at gcc dot gnu.org 2013-10-25 13:03 ` fragabr at gmail dot com 2014-01-09 10:28 ` redi at gcc dot gnu.org 2014-01-09 13:00 ` fragabr at gmail dot com 2014-01-20 18:19 ` redi at gcc dot gnu.org 2014-01-20 18:22 ` redi at gcc dot gnu.org 2014-01-20 19:56 ` redi at gcc dot gnu.org 2014-01-20 19:58 ` fragabr at gmail dot com [this message] 2014-01-20 20:02 ` redi at gcc dot gnu.org 2014-01-22 18:34 ` redi at gcc dot gnu.org 2014-01-23 18:35 ` redi at gcc dot gnu.org 2014-01-23 18:40 ` redi at gcc dot gnu.org 2014-01-23 18:47 ` fragabr at gmail dot com 2014-01-23 19:18 ` jakub at gcc dot gnu.org 2014-01-23 19:25 ` fragabr at gmail dot com 2014-01-23 19:42 ` redi at gcc dot gnu.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=bug-56779-4-NgUlMolpyt@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).