From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Provide pid_to_exec_file on Solaris (PR tdep/17903)
Date: Wed, 19 Sep 2018 17:50:00 -0000 [thread overview]
Message-ID: <yddfty5gyws.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <03828c1b15ed6b82a82e30b7a139bc76@polymtl.ca> (Simon Marchi's message of "Wed, 19 Sep 2018 10:53:15 -0400")
Hi Simon,
> On 2018-09-19 10:48, Tom Tromey wrote:
>> procfs.c is one of the cloexec holdouts, because I could never compile
>> it.
>> But I guess once the buildbot is up I can do it :)
>
> I don't know if you are registered to the gcc compile farm announce mailing
> list, so just in case, there are now some Solaris machines (perhaps the
> same as Rainer is using for the buildbot?):
>
> https://lists.tetaneutral.net/pipermail/cfarm-announces/2018-September/000002.html
they aren't: I've got two Solaris 11.4 kernel zones (sparc and x86)
intended to run both the buildbots and in principle fit for addition to
the compile farm. However, a transparent integration probably won't be
possible because University policy requires prior acceptance (though
online) of the Acceptable Use Policy.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2018-09-19 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 14:19 Rainer Orth
2018-09-19 14:36 ` Joel Brobecker
2018-09-19 17:44 ` Rainer Orth
2018-09-19 18:06 ` Joel Brobecker
2018-09-19 14:49 ` Tom Tromey
2018-09-19 14:53 ` Simon Marchi
2018-09-19 17:50 ` Rainer Orth [this message]
2018-09-19 17:47 ` Rainer Orth
2018-09-20 9:27 ` Rainer Orth
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=yddfty5gyws.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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