Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Andrew Cagney <cagney@gnu.org>
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 04:04:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.58.0501122124370.77195@dair.pair.com> (raw)
In-Reply-To: <41E55AB7.1060802@gnu.org>

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". ;-)

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.

Editing aclocal:SIM_AC_COMMON to look *exactly* like common.a4
(or indeed leaving it the same; the ifelse does the same) and
this diff to sim/frv/configure.ac (note order of sincludes
assumed fixed as per above):

--- configure.ac.fixed  Thu Jan 13 04:25:38 2005
+++ configure.ac        Thu Jan 13 04:33:45 2005
@@ -3,7 +3,7 @@ AC_PREREQ(2.59)dnl
 AC_INIT(Makefile.in)

 sinclude(../common/aclocal.m4)
-sinclude(../common/common.m4)
+SIM_AC_COMMON

 SIM_AC_OPTION_ENDIAN(BIG_ENDIAN)
 SIM_AC_OPTION_ALIGNMENT(STRICT_ALIGNMENT)

*should* do the same.  But it doesn't; it seems for example
AC_CANONICAL_SYSTEM and AC_PROG_CC aren't called (and from that
point configury derails causing declarations and macros wrong
and missing at compile time).  Weird.  A prominent note that the
contents of common.m4 must not be wrapped and called as a macro
seems in order.  The comment at the top of common.m4
"autoconf.info says this should be called right after AC_INIT"
doesn't tell the important part of the story.

brgds, H-P


  reply	other threads:[~2005-01-13  4:04 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 [this message]
2005-01-13 13:17                 ` Hans-Peter Nilsson
2005-01-13 21:50                 ` Andrew Cagney
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=Pine.BSF.4.58.0501122124370.77195@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=cagney@gnu.org \
    --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