public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <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:56:00 -0000	[thread overview]
Message-ID: <bug-56779-4-CKdn8XYaX8@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 #17 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #16)
> >    AC_SEARCH_LIBS(gettext, intl, [], USE_NLS=no)
> 
> seems a bit crude, as it results in this link test:

It also doesn't help solve the bug :-)

Yes, I realised later that we need a custom test that ensures we use the
correct lib to match whichever libintl.h is included.


  parent reply	other threads:[~2014-01-20 19:56 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 [this message]
2014-01-20 19:58 ` fragabr at gmail dot com
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-CKdn8XYaX8@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: 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).