Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.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 00:46:00 -0000	[thread overview]
Message-ID: <20090318003531.GI31979@adacore.com> (raw)
In-Reply-To: <m31vsvncks.fsf@fleche.redhat.com>

Hi Tom,

> This one includes some changes to the top-level configury for
> libiconv.  If you download libiconv, untar it in the src tree, and
> rename the directory to "libiconv", it will automatically be built.

Wow - you really went all the way to make it easy for anyone to
build GDB with a full libiconv... I don't know if it was really
necessary, but from what I saw in your patch, it didn't seem to
cost much.

> If you do not have libiconv at all, gdb will use a phony iconv that
> supports the minimum required for gdb to work.

One of the things I might add later to this is an option to force
the use of the dummy libiconv, like a --without-libiconv option
or some such.  Not sure yet if AdaCore is going to be interested
in that option, or not. If I can, I'd rather build a static libiconv
and configure GDB to use that.

> Let me know what you think.  If you have access to non-Linux hosts,
> please try this out.

I've only quickly scanned the patch, I'm a total ignorant about
iconv stuff. But I'm okay with the general approach.

-- 
Joel


  parent reply	other threads:[~2009-03-18  0:35 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 [this message]
2009-03-18  1:14                         ` Tom Tromey

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=20090318003531.GI31979@adacore.com \
    --to=brobecker@adacore.com \
    --cc=andreolb@gmail.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=tromey@redhat.com \
    /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