From: tran vanle <vantranbk@yahoo.com.au>
To: linuxppc-embedded@ozlabs.org
Subject: Not know how to build image and user application from ELDK 4.0
Date: Tue, 17 Oct 2006 00:21:37 +1000 (EST) [thread overview]
Message-ID: <20061016142137.34580.qmail@web33007.mail.mud.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
Hi every one
I have just installed ELDK 4.0 for TQM 8xxL and read it README but I don't know how to build my custom image or adding user application.Such as I want to build ssh and openssh but I don't know where to start and how to do it step by step.
Every one who HAD did it please guide me step by step to do it
Thanks for all
---------------------------------
On Yahoo!7
PS Trixi: Check back weekly for Trixi's latest update
[-- Attachment #2: Type: text/html, Size: 547 bytes --]
next reply other threads:[~2006-10-16 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 14:21 tran vanle [this message]
2006-10-16 19:20 ` Not know how to build image and user application from ELDK 4.0 Wolfgang Denk
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=20061016142137.34580.qmail@web33007.mail.mud.yahoo.com \
--to=vantranbk@yahoo.com.au \
--cc=linuxppc-embedded@ozlabs.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).