public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tromey@adacore.com>, Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/5] Remove gdb/testsuite/configure
Date: Sat, 5 Jun 2021 11:51:05 +0200	[thread overview]
Message-ID: <aa3aa4de-461f-0be5-f68e-86876a7332ce@suse.de> (raw)
In-Reply-To: <874kehsn2y.fsf@tromey.com>

On 6/1/21 3:59 PM, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
> 
>>> -EXTRA_RULES = @EXTRA_RULES@
>>> +ifeq ($(build_canonical),$(host_canonical))
>>> +ifeq ($(host_canonical),$(target_canonical))
>>> +ifneq (,$(findstring gnu,$(host_canonical)))
>>> +EXTRA_RULES = read1
>>> +endif
>>> +endif
>>> +endif
> 
> Simon> Could the read1 artifacts be built as a dependency of the "make
> Simon> check-read1" target (so, on-demand)?  Either way is fine with me, but it
> Simon> would just be a little bit less complexity.
> 
> Sure.  If anybody relies on being able to do this without using 'make',
> there's already a 'read1' convenience target that can be used.
> 
> I'm going to check this in with this change.
> 

So, before this commit we had:
...
$ ( cd build/gdb/testsuite/; make check READ1=1
RUNTESTFLAGS=gdb.base/info-types-c.exp )
gcc -o read1.so
/home/vries/gdb_versions/devel/src/gdb/testsuite/lib/read1.c -Wall -g
-shared -fPIC
Making expect-read1
Nothing to be done for all...
Making a new config file...
make check-single
...

And after:
...
$ ( cd build/gdb/testsuite/; make check READ1=1
RUNTESTFLAGS=gdb.base/info-types-c.exp )
Nothing to be done for all...
Making a new config file...
make check-single
make[1]: Entering directory
'/home/vries/gdb_versions/devel/build/gdb/testsuite'
rootme=`pwd`; export rootme;
srcdir=/home/vries/gdb_versions/devel/src/gdb/testsuite ; export srcdir
; EXPECT=`if [ "${READ1}" != "" ] ; then echo ${rootme}/expect-read1;
elif [ -f ${rootme}/../../expect/expect ] ; then echo
${rootme}/../../expect/expect ; else echo expect ; fi` ; export EXPECT ;
EXEEXT= ; export EXEEXT ;
LD_LIBRARY_PATH=$rootme/../../expect:$rootme/../../libstdc++:$rootme/../../tk/unix:$rootme/../../tcl/unix:$rootme/../../bfd:$rootme/../../opcodes:$LD_LIBRARY_PATH;
export LD_LIBRARY_PATH; if [ -f ${rootme}/../../expect/expect ] ; then
TCL_LIBRARY=${srcdir}/../../tcl/library ; export TCL_LIBRARY ; fi ; ` if
[ -f ${srcdir}/../../dejagnu/runtest ]; then echo
${srcdir}/../../dejagnu/runtest; else if [ "x86_64-pc-linux-gnu" =
"x86_64-pc-linux-gnu" ]; then echo runtest; else t='s,y,y,'; echo
runtest | sed -e $t; fi; fi` --status gdb.base/info-types-c.exp
ERROR: unable to find expect in the PATH
make[1]: *** [Makefile:206: check-single] Error 1
make[1]: Leaving directory
'/home/vries/gdb_versions/devel/build/gdb/testsuite'
make: *** [Makefile:159: check] Error 2
...

Then after running check-read1, this works again.

Personally I'm fine with no longer supporting this.  But perhaps others
use READ1=1 in combination with some nonstandard make target?  I'm not sure.

Anyway, if we decide to leave things as they are now, we should document
this in gdb/testsuite/README:
...
 Examples:

         make -j10 check-read1 TESTS="*/paginate-*.exp"
-        make -j10 check READ1="1"
...

Thanks,
- Tom

  reply	other threads:[~2021-06-05  9:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 19:27 [PATCH 0/5] Some gdb build cleanups Tom Tromey
2021-05-28 19:27 ` [PATCH 1/5] Remove gdb/testsuite/configure Tom Tromey
2021-05-29  3:44   ` Simon Marchi
2021-06-01 13:59     ` Tom Tromey
2021-06-05  9:51       ` Tom de Vries [this message]
2021-06-09 14:35         ` Tom Tromey
2021-06-09 14:46           ` Tom de Vries
2021-08-07  1:03   ` Tom de Vries
2021-05-28 19:27 ` [PATCH 2/5] Always build 'all' in gdb/testsuite Tom Tromey
2021-05-28 19:27 ` [PATCH 3/5] Apply silent Makefile rules to gdb/testsuite Tom Tromey
2021-05-28 19:27 ` [PATCH 4/5] Clean up gdb's --enable-shared Tom Tromey
2021-05-28 19:27 ` [PATCH 5/5] Remove some gdb/data-directory special cases Tom Tromey
2021-05-29  3:50 ` [PATCH 0/5] Some gdb build cleanups Simon Marchi

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=aa3aa4de-461f-0be5-f68e-86876a7332ce@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).