Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA/commit] use libiconv.a instead of -liconv for in-tree  libiconv
Date: Wed, 09 Dec 2009 10:12:00 -0000	[thread overview]
Message-ID: <20091209101221.GA2919@adacore.com> (raw)
In-Reply-To: <20091203225852.GG2877@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

> 2009-12-03  Joel Brobecker  <brobecker@adacore.com>
> 
>             * acinclude.m4: Link against in-tree libiconv by adding
>             libiconv.a to the LIBS instead of using -liconv.
>             * configure: Regenerate.

Now checked in.  I also committed the following comment update,
following feedback from Daniel:

2009-12-09  Joel Brobecker  <brobecker@adacore.com>

        * acinclude.m4: Update comment.

Cheers,
-- 
Joel

[-- Attachment #2: iconv-configure-comment.diff --]
[-- Type: text/x-diff, Size: 480 bytes --]

Index: acinclude.m4
===================================================================
RCS file: /cvs/src/src/gdb/acinclude.m4,v
retrieving revision 1.33
diff -u -p -r1.33 acinclude.m4
--- acinclude.m4	9 Dec 2009 10:07:13 -0000	1.33
+++ acinclude.m4	9 Dec 2009 10:09:34 -0000
@@ -169,7 +169,8 @@ case "x$am_cv_prog_cc_stdc" in
 esac
 ])
 
-dnl From Bruno Haible.
+dnl Originally from Bruno Haible, but with some modifications
+dnl for the GDB project.
 
 AC_DEFUN([AM_ICONV],
 [

      parent reply	other threads:[~2009-12-09 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 22:59 Joel Brobecker
2009-12-03 23:11 ` Daniel Jacobowitz
2009-12-04  1:14   ` Tom Tromey
2009-12-04  1:12 ` Tom Tromey
2009-12-04  3:28   ` Joel Brobecker
2009-12-09 10:12 ` Joel Brobecker [this message]

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=20091209101221.GA2919@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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