From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Robert Bu <robert.bu@gmail.com>, gdb@sourceware.org
Subject: Re: Problem to build CVS head
Date: Thu, 10 Sep 2009 04:01:00 -0000 [thread overview]
Message-ID: <20090910040054.GD7489@adacore.com> (raw)
In-Reply-To: <m3r5ufo6kg.fsf@fleche.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 274 bytes --]
> There's a missing update to gdb/configure.ac. Someone will check in a
> fix soon. If nobody beats me to it I will do it tomorrow.
Argh! Problem reproduced when building with --without-python, and fixed
with the attached patch. Thanks for reporting the issue.
--
Joel
[-- Attachment #2: python-rename-configury.diff --]
[-- Type: text/x-diff, Size: 1628 bytes --]
commit 844dd7cf19e634ee7e39e70f82c00e17de949641
Author: Joel Brobecker <brobecker@adacore.com>
Date: Wed Sep 9 20:56:25 2009 -0700
* configure.ac: Fix the names of the python source and object files
following the renaming done in an earlier change.
* configure: Regenerate.
diff --git a/gdb/configure b/gdb/configure
index 2691e33..99acc2f 100755
--- a/gdb/configure
+++ b/gdb/configure
@@ -9323,8 +9323,8 @@ $as_echo "${PYTHON_CFLAGS}" >&6; }
else
# Even if Python support is not compiled in, we need to have these files
# included in order to recognize the GDB command "python".
- CONFIG_OBS="$CONFIG_OBS python.o python-value.o python-prettyprint.o"
- CONFIG_SRCS="$CONFIG_SRCS python/python.c python/python-value.c python/python-prettyprint.c"
+ CONFIG_OBS="$CONFIG_OBS python.o py-value.o py-prettyprint.o"
+ CONFIG_SRCS="$CONFIG_SRCS python/python.c python/py-value.c python/py-prettyprint.c"
fi
diff --git a/gdb/configure.ac b/gdb/configure.ac
index aa0bf75..b31d9b7 100644
--- a/gdb/configure.ac
+++ b/gdb/configure.ac
@@ -683,8 +683,8 @@ if test "${have_libpython}" = yes; then
else
# Even if Python support is not compiled in, we need to have these files
# included in order to recognize the GDB command "python".
- CONFIG_OBS="$CONFIG_OBS python.o python-value.o python-prettyprint.o"
- CONFIG_SRCS="$CONFIG_SRCS python/python.c python/python-value.c python/python-prettyprint.c"
+ CONFIG_OBS="$CONFIG_OBS python.o py-value.o py-prettyprint.o"
+ CONFIG_SRCS="$CONFIG_SRCS python/python.c python/py-value.c python/py-prettyprint.c"
fi
AC_SUBST(PYTHON_CFLAGS)
prev parent reply other threads:[~2009-09-10 4:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 2:31 Robert Bu
2009-09-10 2:51 ` Tom Tromey
2009-09-10 4:01 ` Joel Brobecker [this message]
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=20090910040054.GD7489@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=robert.bu@gmail.com \
--cc=tromey@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