public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Paul_Koning@Dell.com
Cc: samuel.miing@gmail.com, binutils@sourceware.org, gcc@gcc.gnu.org,
	dje.gcc@gmail.com, dnovillo@google.com, gerald@pfeifer.com
Subject: Re: Automated Toolchain Building and Testing
Date: Thu, 29 Aug 2013 11:21:00 -0000	[thread overview]
Message-ID: <20130829081043.GG29134@lug-owl.de> (raw)
In-Reply-To: <C75A84166056C94F84D238A44AF9F6AD034CD86D@AUSX10MPC103.AMER.DELL.COM>

[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]

On Thu, 2013-08-29 01:18:32 +0000, Paul_Koning@Dell.com <Paul_Koning@Dell.com> wrote:
> On Aug 28, 2013, at 8:52 PM, Samuel Mi <samuel.miing@gmail.com> wrote:
> > On Thu, Aug 29, 2013 at 2:54 AM, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> > > On Thu, 2013-08-29 02:43:54 +0800, Samuel Mi <samuel.miing@gmail.com> wrote:
> > > > > ...or can you, instead of using the Java-based
> > > > > client part of Jenkins, issue all commands over a SSH (or maybe even
> > > > > Telnet...) session?  Is there a module for this available?
> > > > If making jenkins running on target systems you want whether old or
> > > > modern, then take a look at Jenkins-SSH
> > > > (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+SSH) to remotely
> > > > control over ssh.
> > > This looks like a SSH connector for the Jenkins server side, no?
> > No. Actually, Jenkins implements a built-in SSH server within itself.
> > At this point, it's consider to be a normal SSH server. So, you can
> > remotely access Jenkins server via SSH after setting up corresponding
> > configurations within it.
> 
> What non-antique Linux doesn't come with Python?

GCC and Binutils don't exclusively run on Linux platforms. Actually,
the Linux targets are those which are actually tested the most by
usual day-to-day usage.  I'd specifically like to run tests on
platforms that are _not_ used by large user bases, but still supported
by GCC.

Those platforms tend to be non-Linux, non-i386, non-recent, or any
combination if those. *This* is what I want to support. (It still
should also run on Linux, though.)

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:                   ...und wenn Du denkst, es geht nicht mehr,
the second  :                          kommt irgendwo ein Lichtlein her.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-08-29  8:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 10:03 Jan-Benedict Glaw
2013-08-28 10:39 ` Sebastian Huber
2013-08-28 21:26 ` Samuel Mi
2013-08-29  0:52   ` Jan-Benedict Glaw
2013-08-29  1:18     ` Samuel Mi
2013-08-29  7:23       ` Jan-Benedict Glaw
2013-08-29 10:02         ` Samuel Mi
2013-08-29 10:11           ` Dan Kegel
2013-08-29 10:23           ` Paul_Koning
2013-08-29 11:21             ` Jan-Benedict Glaw [this message]
2013-08-29 13:02     ` Rainer Orth
2013-08-29 14:33       ` Jan-Benedict Glaw
2013-08-29 22:40         ` Diego Novillo
2013-08-30  8:54           ` Jan-Benedict Glaw

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=20130829081043.GG29134@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=Paul_Koning@Dell.com \
    --cc=binutils@sourceware.org \
    --cc=dje.gcc@gmail.com \
    --cc=dnovillo@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=samuel.miing@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).