Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit/sim] Add common/common.m4; Was: [commit/sim] switch autoconf 2.59
Date: Thu, 13 Jan 2005 21:50:00 -0000	[thread overview]
Message-ID: <41E6ECA1.2040209@gnu.org> (raw)
In-Reply-To: <Pine.BSF.4.58.0501122124370.77195@dair.pair.com>

Hans-Peter Nilsson wrote:
> On Wed, 12 Jan 2005, Andrew Cagney wrote:
> 
> 
>>I've also committed the attached.  It gets around the SIM_AC_COMMON
>>problem by inlining the macro's contents.
>>
>>Your turn :-)
> 
> 
> With current sources (after adding common.m4), CY_GNU_GETTEXT is
> not defined before use (checkout, configury and build as
> before):
> ...
> configure: configuring in frv
> ...
> /n/asic/slask/hp/fixsimbreakage/src/sim/frv/configure: CY_GNU_GETTEXT: command not found
> ...
> (further problems ignored.)
> 
> The bug seen above can be fixed by sincluding aclocal.m4 before
> common.m4, putting the definition before the call.  (After that
> I then see some disturbing warnings when compiling
> sim/frv/sem.c, but those aren't any fault of the configury at
> least, so that's to be considered a success.)
> 
> I'm not sure why you didn't just sinclude common.m4 from
> aclocal.m4 and why you didn't remove SIM_AC_COMMON from
> aclocal.m4.  Therefore I don't know how you want the above and
> the worry below actually fixed and so I'll pass back the "your
> turn". ;-)

(I don't like nested includes, and aclocal.m4 should just contain macro 
definitions :-)

Have a look at common/configure.ac.  It's still calling SIM_AC_COMMON 
with a parameter, hence my reason for keeping the SIM_AC_COMMON macro 
(well for at least the moment).

To do like you suggest would mean adding AC_CONFIG_HEADER to 
*/configure.ac (possibly not a bad thing - common/ is probably still 
broken).

> The biggest problem is that I don't understand why breaking out
> SIM_AC_COMMON to common.m4 should help at all, but it does.

Yea, weird :-)

I'll flip the sinclude order.

Andrew


  parent reply	other threads:[~2005-01-13 21:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08  3:40 Andrew Cagney
2005-01-08  4:07 ` Daniel Jacobowitz
2005-01-10 16:18 ` Andrew Cagney
2005-01-11 20:20 ` Hans-Peter Nilsson
2005-01-11 21:06   ` Andrew Cagney
2005-01-12  1:17     ` Hans-Peter Nilsson
2005-01-12  1:26       ` Andrew Cagney
2005-01-12  2:00         ` Hans-Peter Nilsson
2005-01-12 16:29           ` [commit/sim] Force generation of configure and other stuff; Was: " Andrew Cagney
2005-01-12 17:15             ` [commit/sim] Add common/common.m4; " Andrew Cagney
2005-01-13  4:04               ` Hans-Peter Nilsson
2005-01-13 13:17                 ` Hans-Peter Nilsson
2005-01-13 21:50                 ` Andrew Cagney [this message]
2005-01-14 20:11                   ` [commit/sim] flip and separate; Was: " Andrew Cagney
2005-01-14 21:46                     ` Hans-Peter Nilsson
2005-01-12 17:53             ` [commit/sim] Force generation of configure and other stuff; " Hans-Peter Nilsson
2005-01-12 18:12               ` Andrew Cagney
2005-01-12 18:19                 ` Hans-Peter Nilsson
2005-01-12 18:50                   ` Andrew Cagney
2005-01-13  2:01             ` Hans-Peter Nilsson

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=41E6ECA1.2040209@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hp@bitrange.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