From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: buildbot@sourceware.org
Subject: Re: proposed patch: gcc-fullest builder to build+check multilib -m32/-m64
Date: Sun, 29 Sep 2024 22:23:49 +0200 [thread overview]
Message-ID: <20240929202349.GG3393@gnu.wildebeest.org> (raw)
In-Reply-To: <Zvmz5LZM7ZI9mV1Y@elastic.org>
On Sun, Sep 29, 2024 at 04:09:08PM -0400, Frank Ch. Eigler wrote:
> Hi -
>
> > OK, adding argument names makes sense. () and [] seems to match. But
> > then... You are using a python "raw string literal". So no escape
> > sequences nside the " quotes. But still a double \ because one will be
> > eaten by the shell?
> >
> > I must admit I don't fully know what you are expecting at the shell
> > level or how precicely this comes out. Sorry.
>
> The dejagnu code expects to see \{ characters, so python should eat nothing,
> the shell forked by python should eat one (\\{ -> \{), leaving \{ for expect.
> That's the theory, but I'm not easily able to test this locally. ;)
Could you try with os.system? Don't know if that us exactly what
happens, but it might help. Something like:
python3 -c 'import os; os.system ("make check -k -j12 " + r"RUNTESTFLAGS=--target_board=unix\\{,-m32\\}" + " || true")'
Cheers,
Mark
next prev parent reply other threads:[~2024-09-29 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 17:43 Frank Ch. Eigler
2024-09-29 20:04 ` Mark Wielaard
2024-09-29 20:09 ` Frank Ch. Eigler
2024-09-29 20:23 ` Mark Wielaard [this message]
2024-09-29 20:34 ` Frank Ch. Eigler
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=20240929202349.GG3393@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=fche@elastic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).