Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: gdb-patches@sources.redhat.com
Cc: newlib@sources.redhat.com,binutils@sources.redhat.com,gcc-patches@gcc.gnu.org
Subject: Re: [RFA] toplevel: Always use in tree makeinfo in texinfo subdir
Date: Fri, 18 Jun 2004 13:50:00 -0000	[thread overview]
Message-ID: <40D2E485.9090102@gnu.org> (raw)
In-Reply-To: <20040618113448.GF593@cygbert.vinschen.de>

> +USUAL_MAKEINFO = `if [ -f $$r/texinfo/makeinfo/makeinfo ] || pwd | grep /texinfo$ > /dev/null ; \

You should at least quote '/texinfo$'.

You may also look into supporting extra_configure_flags and 
extra_make_flags Autogen variables for modules.  Then just define them 
to USUAL_MAKEINFO="$$r/texinfo/makeinfo/makeinfo".

Maybe this will allow major cleanups WRT the way gcc is handled in the 
toplevel Makefile, so it is worth considering it.

Paolo


  reply	other threads:[~2004-06-18 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 11:35 Corinna Vinschen
2004-06-18 13:50 ` Paolo Bonzini [this message]
     [not found] ` <40D7E527.2010805@gnu.org>
2004-06-22 22:16   ` Alexandre Oliva
2004-06-23  8:45     ` Paolo Bonzini

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=40D2E485.9090102@gnu.org \
    --to=bonzini@gnu.org \
    --cc=binutils@sources.redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=newlib@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