From: Daniel Jacobowitz <drow@false.org>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, teawater <teawater@gmail.com>
Subject: Re: [PATCH 4/4] catch syscall -- try 4 -- Build system, testcase and documentation
Date: Sun, 01 Feb 2009 19:50:00 -0000 [thread overview]
Message-ID: <20090201195010.GM4597@caradoc.them.org> (raw)
In-Reply-To: <1232929837.26873.25.camel@miki>
On Sun, Jan 25, 2009 at 10:30:36PM -0200, Sérgio Durigan Júnior wrote:
> -HFILES_NO_SRCDIR = osf-share/cma_debug_client.h \
> +HFILES_NO_SRCDIR = osf-share/cma_debug_client.h linux-tdep.h \
Space there, not tab please.
> @@ -844,11 +857,38 @@ generated_files = config.h observer.h observer.inc ada-lex.c \
> $(COMPILE) $<
> $(POSTCOMPILE)
>
> -all: gdb$(EXEEXT) $(CONFIG_ALL)
> +all: gdb$(EXEEXT) $(CONFIG_ALL) xml-syscall-copy
> @$(MAKE) $(FLAGS_TO_PASS) DO=all "DODIRS=`echo $(SUBDIRS) | sed 's/testsuite//'`" subdir_do
> .PHONY: all-tui
> all-tui: $(TUI)$(EXEEXT)
>
> +xml-syscall-copy:
> + if [ "`cd $(srcdir) && pwd`" != "`pwd`" ] ; then \
> + mkdir -p ./$(XML_SYSCALLS_DIR) ; \
> + list='$(XML_SYSCALLS_FILES)' ; \
> + for file in $$list ; do \
> + f=$(srcdir)/$(XML_SYSCALLS_DIR)/$$file ; \
> + if test -f $$f ; then \
> + $(INSTALL_DATA) $$f \
> + ./$(XML_SYSCALLS_DIR) ; \
> + fi ; \
> + done ; \
> + fi ;
Why is this necessary? Is it for running GDB from the build
directory? If that's it, please add a comment.
Also, this and xml-syscall-install need a ".PHONY:" since they are not
the names of real files.
> +# Until "catch syscall" is implemented on other targets...
> +if {![istarget "hppa*-hp-hpux*"] && ![istarget "*-linux*"]} then {
> + continue
> +}
> +
> +# This shall be updated whenever 'catch syscall' is implemented
> +# on some architecture.
> +#if { ![istarget "x86_64-*-linux*"] && ![istarget "i\[34567\]86-*-linux*"]
> +if { ![istarget "i\[34567\]86-*-linux*"]
> + && ![istarget "powerpc-*-linux*"] && ![istarget "powerpc64-*-linux*"] } {
> + continue
> +}
Or you can test at runtime: if it prints out "not supported on this
target yet" then issue an UNSUPPORTED and skip the rest of the test.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-02-01 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 0:31 Sérgio Durigan Júnior
2009-01-26 4:02 ` Eli Zaretskii
2009-01-26 5:04 ` Sérgio Durigan Júnior
2009-02-01 19:50 ` Daniel Jacobowitz [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=20090201195010.GM4597@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@linux.vnet.ibm.com \
--cc=teawater@gmail.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