From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: tromey@redhat.com, Elena Zannoni <ezannoni@cygnus.com>,
Christopher Faylor <cgf@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: --args => build failure
Date: Fri, 09 Nov 2001 18:30:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20011122121440.01d54488@ics.u-strasbg.fr> (raw)
In-Reply-To: <87r8qrhg57.fsf@creche.redhat.com>
At 00:13 22/11/2001 , Tom Tromey a écrit:
> >>>>> "Elena" == Elena Zannoni <ezannoni@cygnus.com> writes:
>
>Elena> main.c changes are ok.
>
>Thanks! I think that's the last approval I need. I'll check the
>patch in this evening.
>
>I assume I should close the corresponding PRs. What is the gdb
>process for this? Do I simply close them? Put them in `feedback'?
>Or what?
Your patch does create a build failure for cygwin target.
This target apparently does not use fork-child.c
(at least it is not included into the libgdb.a)
and thus I get the following error when I try to build the current main CVS
tree:
$ make
rm -f gdb.exe
gcc -g -O2 -o gdb.exe \
main.o libgdb.a cli-decode.o cli-script.o cli-cmds.o cli-setshow.o
cli-utils.o m
i-out.o mi-console.o mi-cmds.o mi-cmd-var.o mi-cmd-break.o mi-cmd-stack.o
mi-cmd
-disas.o mi-main.o mi-parse.o mi-getopt.o ../bfd/libbfd.a
../readline/libread
line.a ../opcodes/libopcodes.a ./../intl/libintl.a ../libiberty/libiberty.a `if
test -r ../libtermcap/libtermcap.a; then echo ../libtermcap/libtermcap.a;
else e
cho -ltermcap; fi` -lm ../libiberty/libiberty.a -luser32 -limagehlp\
libgdb.a(gdbarch.o): In function `gdbarch_alloc':
/home/muller/gdb/build/gdb/../../src/gdb/gdbarch.c:509: undefined reference
to `
construct_inferior_arguments'
/home/muller/gdb/build/gdb/../../src/gdb/gdbarch.c:482: undefined reference
to `
construct_inferior_arguments'
collect2: ld returned 1 exit status
make: *** [gdb.exe] Error 1
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2001-11-22 11:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pierre Muller's message of "Thu, 22 Nov 2001 12:17:26 +0100">
[not found] ` <Elena Zannoni's message of "Wed, 21 Nov 2001 17:16:14 -0500">
[not found] ` <873d3mcpcu.fsf@creche.redhat.com>
[not found] ` <3BED93E7.9000104@cygnus.com>
[not found] ` <87snbmb9nm.fsf@creche.redhat.com>
2001-11-02 11:37 ` PATCH: --args Fernando Nasser
2001-11-08 17:15 ` Elena Zannoni
2001-11-08 19:33 ` Tom Tromey
2001-11-09 1:29 ` Andrew Cagney
2001-11-09 18:30 ` Pierre Muller [this message]
2001-11-09 21:48 ` PATCH: --args => build failure Pierre Muller
2001-11-09 23:40 ` Pierre Muller
2001-11-10 8:22 ` Tom Tromey
2001-11-10 8:34 ` Pierre Muller
2001-11-10 11:55 ` Christopher Faylor
2001-11-26 14:58 ` Michael Snyder
2001-11-13 8:56 ` Michael Snyder
2001-11-26 15:05 ` Christopher Faylor
2001-11-13 9:00 ` Christopher Faylor
[not found] <Elena>
[not found] ` <Zannoni's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Wed,>
[not found] ` <21>
[not found] ` <Nov>
[not found] ` <2001>
[not found] ` <17:16:14>
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=4.2.0.58.20011122121440.01d54488@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=cgf@redhat.com \
--cc=ezannoni@cygnus.com \
--cc=gdb-patches@sources.redhat.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