From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: eliz@elta.co.il
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Fix compilation failure of remote-fileio.c
Date: Tue, 30 Dec 2003 08:26:00 -0000 [thread overview]
Message-ID: <20031230082625.140414B35A@berman.michael-chastain.com> (raw)
Hi Eli,
src/gdb/configure is produced with this version of autoconf:
ftp://sources.redhat.com/pub/binutils/autoconf-000227.tar.bz2
This version of autoconf identifies itself as "autoconf version 2.13",
but produces different "configure" files than autoconf 2.13.
Fun fun fun!
The difference is that autoconf-000227 has some "--site-file"
stuff in it that I don't even understand. But that's the blessed
version for gdb.
eli> Because running Autoconf 2.13 installed on fencepost.gnu.org
eli> produces quite a few errors about undefined macros. What am I missing?
Oddly, when I run the real autoconf 2.13 on current cvs HEAD,
it does run. It just produces a different "configure" than the
version in cvs. autoconf 000227 produces the identical "configure".
So if you are getting "undefined macros" then there is something
even more wrong.
I would recommend:
-- download autoconf 000227
-- build your own private copy of it
-- check that it generates identical "configure"
Do that before banging on configure.in
eli> Also, if it _is_ Autoconf 2.13, then it seems like it doesn't know
eli> about AC_CHECK_MEMBER, so what should I put in configure.in for
eli> testing the existence of st_blocks?
Maybe cut-and-paste from the l_addr check?
Michael C
next reply other threads:[~2003-12-30 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 8:26 Michael Elizabeth Chastain [this message]
2003-12-30 9:12 ` Eli Zaretskii
2003-12-30 10:34 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2003-12-30 19:20 Michael Elizabeth Chastain
2003-12-28 13:50 Eli Zaretskii
2003-12-28 23:38 ` Daniel Jacobowitz
2003-12-29 7:01 ` Eli Zaretskii
2003-12-29 16:01 ` Daniel Jacobowitz
2003-12-30 7:20 ` Eli Zaretskii
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=20031230082625.140414B35A@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=eliz@elta.co.il \
--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