Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	bauerman@br.ibm.com,         andreolb@gmail.com,
	gdb-patches@sourceware.org
Subject: Re: [PATCH] PR exp/9103
Date: Wed, 18 Mar 2009 01:14:00 -0000	[thread overview]
Message-ID: <m3k56nk6a5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090318003531.GI31979@adacore.com> (Joel Brobecker's message of "Tue\, 17 Mar 2009 20\:35\:31 -0400")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> One of the things I might add later to this is an option to
Joel> force the use of the dummy libiconv, like a --without-libiconv
Joel> option or some such.

FWIW this only requires changing a single #if -- the one in
gdb_wchar.h.  I tested this sort of build by hacking in "0 &&" there :-)

Joel> Not sure yet if AdaCore is going to be interested in that
Joel> option, or not. If I can, I'd rather build a static libiconv and
Joel> configure GDB to use that.

Assuming you have your own tree, like the now-ancient Cygnus "devo"
tree, I would suggest simply importing libiconv.  From what I can tell
it has fairly modest porting requirements; it can't be too hard to
port it to any oddball machines you may have.  Then, it will be used
when needed, and built (but ignored) when not.

There may be machines where configure will pick the system iconv but
where gdb will not work properly.  I am happy to help deal with
problems along these lines.

Tom


      reply	other threads:[~2009-03-18  0:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c3f94bcc0903101928g3d767b7ah60ac81e8b6f77de@mail.gmail.com>
2009-03-11 15:37 ` Andre Oliveira Loureiro do Baixo
2009-03-11 16:30   ` Daniel Jacobowitz
2009-03-11 17:09     ` Andre Oliveira Loureiro do Baixo
2009-03-11 17:13       ` Tom Tromey
2009-03-11 18:37         ` Andre Oliveira Loureiro do Baixo
2009-03-11 20:29           ` Thiago Jung Bauermann
2009-03-11 22:25             ` Tom Tromey
2009-03-12  1:11               ` Tom Tromey
2009-03-13 23:37                 ` Joel Brobecker
2009-03-13 23:38                   ` Joel Brobecker
2009-03-14  1:41                     ` Tom Tromey
2009-03-14  0:10                   ` Mark Kettenis
2009-03-17 20:06                     ` Tom Tromey
2009-03-17 22:12                       ` Eli Zaretskii
2009-03-18  3:07                         ` Tom Tromey
2009-03-18  4:20                           ` Eli Zaretskii
2009-03-18 17:11                             ` Tom Tromey
2009-03-18 20:30                               ` Eli Zaretskii
2009-03-18  0:46                       ` Joel Brobecker
2009-03-18  1:14                         ` Tom Tromey [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=m3k56nk6a5.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=andreolb@gmail.com \
    --cc=bauerman@br.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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