From: Daniel Jacobowitz <drow@mvista.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] disable-nls if msgfmt could not be found
Date: Tue, 18 Mar 2003 16:51:00 -0000 [thread overview]
Message-ID: <20030318165154.GA27537@nevyn.them.org> (raw)
In-Reply-To: <20030318034633.GO16507@gnat.com>
On Mon, Mar 17, 2003 at 07:46:34PM -0800, Joel Brobecker wrote:
> Hello,
>
> I hope I am sending this to the right list...
Sort of. Patches to toplevel configure need to also go to gcc-patches@
and binutils@; generally (i.e. in practice) only Alexandre Oliva and DJ
Delorie approve them.
> Some users building GDB on systems where msgfmt is not available were
> blocked when the build failed (in bfd, and probably another subdir
> that I can't remember). See
> http://sources.redhat.com/ml/gdb/2003-02/msg00310.html.
>
> Instead of adding the checks in each subdir, I thought that it might be
> better to do the check for msgfmt in the toplevel configure, and pass
> --disable-nls to the subdir configure commands if not found. The
> following patches tries to do this, and has been tested on a hpux box
> where msgfmt is missing, and on a linux machine where msgfmt was
> available.
>
> Ideally, we want to do the check for msgfmt only if --disable-nls was
> not already specified. However, the only consequence of not checking
> for the presence of --disable-nls is that we might have more than one
> --disable/enable-nls switches on the subdir configure commands. I
> think it will be ok, since I've placed the --disable-nls at the end
> so it should overide the user's switch. An AC_MSG_WARN may also have
> been nice, but I decided against it because seeing a warning even
> when the user has specified --disable-nls would seem strange...
>
> Would the following change be acceptable for inclusion?
>
> 2003-03-17 J. Brobecker <brobecker@gnat.com>
>
> * configure.in: Add check for msgfmt, configure subdir with
> --disable-nls if not found.
> * configure: Regenerate.
>
> --
> Joel
> Index: configure.in
> ===================================================================
> RCS file: /cvs/src/src/configure.in,v
> retrieving revision 1.158
> diff -c -3 -r1.158 configure.in
> *** configure.in 12 Mar 2003 20:47:07 -0000 1.158
> --- configure.in 18 Mar 2003 03:43:33 -0000
> ***************
> *** 1824,1829 ****
> --- 1824,1838 ----
> *) gxx_include_dir=${with_gxx_include_dir} ;;
> esac
>
> + # Check that msgfmt can be found in the PATH, or configure with
> + # --disable-nls to avoid a build failure.
> + AC_CHECK_PROG(MSGFMT, msgfmt, msgfmt, )
> + if [ test "x$MSGFMT" = "x" ]; then
> + build_configargs="${build_configargs} --disable-nls"
> + host_configargs="${host_configargs} --disable-nls"
> + target_configargs="${target_configargs} --disable-nls"
> + fi
> +
> FLAGS_FOR_TARGET=
> case " $target_configdirs " in
> *" newlib "*)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-18 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 3:46 Joel Brobecker
2003-03-18 16:51 ` Daniel Jacobowitz [this message]
2003-03-18 18:33 Joel Brobecker
2003-03-18 19:16 ` Joseph S. Myers
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=20030318165154.GA27537@nevyn.them.org \
--to=drow@mvista.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@sources.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