linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: FW: Need openssh for embedded linux on 440GP
Date: 12 Mar 2003 08:11:09 -0800	[thread overview]
Message-ID: <52zno0woo2.fsf@topspin.com> (raw)
In-Reply-To: <995FF289C9D69747A09E42992644595405B236B3@penguin.adic.com>


    brian> As an update to what's written below, I did try
    brian> cross-compiling and that was even less successful than
    brian> compiling on my embedded target.

I cross-compiled OpenSSH 3.5 for the 440GP.  I did have to go through
the "configure" file and hard-code all the tests that try to run
programs.

 - Roland

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2003-03-12 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 13:09 FW: Need openssh for embedded linux on 440GP brian.auld
2003-03-12 14:11 ` Wolfgang Denk
2003-03-12 16:11 ` Roland Dreier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12 15:47 brian.auld

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=52zno0woo2.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=brian.auld@adic.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).