From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Mike Frysinger <vapier@gentoo.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/5] sim: drop configure scripts for simple ports
Date: Tue, 22 Jun 2021 21:05:06 -0400 [thread overview]
Message-ID: <6d81e053-3470-e106-9556-e20e2610545a@polymtl.ca> (raw)
In-Reply-To: <20210620055519.22229-3-vapier@gentoo.org>
On 2021-06-20 1:55 a.m., Mike Frysinger via Gdb-patches wrote:
> These ports only use the pieces that have been unified, so we can
> merge them into the common configure script and get rid of their
> unique one entirely.
>
> We still compile & link separate run programs, and have dedicated
> subdir Makefiles, but the configure script portion is merged.
Starting with this patch (I think) the file sim/aarch64/Makefile gets
generated with a wrong srcdir value:
srcdir = ..//home/simark/src/binutils-gdb/sim/aarch64
Which causes:
make[2]: Entering directory '/home/simark/build/binutils-gdb/sim/aarch64'
Makefile:34: ..//home/simark/src/binutils-gdb/sim/aarch64/../../gdb/silent-rules.mk: No such file or directory
make[2]: *** No rule to make target '..//home/simark/src/binutils-gdb/sim/aarch64/../../gdb/silent-rules.mk'. Stop.
make[2]: Leaving directory '/home/simark/build/binutils-gdb/sim/aarch64'
That's strange. I deleted sim/ completely and it still happens. For
reference, here's my top-level configure line:
.../configure 'CC=ccache gcc' 'CXX=ccache g++' '--with-system-readline' '--with-system-zlib' '--disable-gold' '--disable-ld' '--disable-gprof' '--disable-gas' '--enable-targets=all' '--with-expat=yes' '--with-python=python3' '--with-guile=guile-2.0' '--with-intel-pt' '--with-babeltrace' '--with-debuginfod' '--enable-libctf' 'CFLAGS=-g3 -O0 -fsanitize=address -fmax-errors=1 -fdiagnostics-color=always' 'CXXFLAGS=-g3 -O0 -fsanitize=address -D_GLIBCXX_DEBUG=1 -fmax-errors=1 -fdiagnostics-color=always' 'LDFLAGS=-fuse-ld=gold -fsanitize=address' '--enable-silent-rules'
Simon
next prev parent reply other threads:[~2021-06-23 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 5:55 [PATCH 1/5] sim: hw: rework configure option & device selection Mike Frysinger via Gdb-patches
2021-06-20 5:55 ` [PATCH 2/5] sim: unify hardware settings Mike Frysinger via Gdb-patches
2021-06-20 5:55 ` [PATCH 3/5] sim: drop configure scripts for simple ports Mike Frysinger via Gdb-patches
2021-06-23 1:05 ` Simon Marchi via Gdb-patches [this message]
2021-06-23 2:09 ` Mike Frysinger via Gdb-patches
2021-06-23 2:59 ` [PATCH] sim: switch common srcdir to abs_srcdir Mike Frysinger via Gdb-patches
2021-06-23 13:01 ` Simon Marchi via Gdb-patches
2021-06-20 5:55 ` [PATCH 4/5] sim: rx: merge with common configure script Mike Frysinger via Gdb-patches
2021-06-20 5:55 ` [PATCH 5/5] sim: hw: move cfi & glue to common code Mike Frysinger via Gdb-patches
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=6d81e053-3470-e106-9556-e20e2610545a@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=vapier@gentoo.org \
/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