public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Randall R Schulz <rrschulz@cris.com>
To: "Kesrin Hanprasert" <kesrin_h@hotmail.com>, cygwin@cygwin.com
Subject: Re: Some question
Date: Sat, 16 Feb 2002 20:22:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20020216200849.023abd20@pop3.cris.com> (raw)
In-Reply-To: <F86TgbLYluLCTaogxLD00002eff@hotmail.com>

Ms. Hanprasert,

I'm not sure kindness is exactly the predominant mood here, but answers can 
be gotten, if solicited just so...


Since your questions appear to be about using XFree86 for Cygwin, you 
probably want to ask on the mailing list devoted specifically to that topic 
area.

Look here for information archives of that list: 
<http://www.cygwin.com/ml/cygwin-xfree/>. I assume you already know about 
the main page for that project, <http://xfree86.cygwin.com/>.

All subscription operations for Cygwin "official" lists are described and 
handled here: <http://cygwin.com/lists.html>. An excerpt from the latter 
half of that page, where the aforementioned "official" lists are enumerated 
and briefly described:

-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
cygwin-xfree: (<http://cygwin.com/ml/cygwin-xfree/>) a list for discussion 
of all things related to XFree86 on Cygwin (Cygwin/XFree86). If you have 
questions about how to use, configure, install, build, or develop with 
Cygwin/XFree86, this is the list for you. If you have general questions 
about using Cygwin/XFree86, please see the Cygwin/XFree86 User's Guide  or 
the Cygwin/XFree86 FAQ.
-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-


Good luck.

Randall Schulz
Mountain View, CA USA


At 19:31 2002-02-16, you wrote:
>Dear Sir/Madam
>       I am learning about Cygwin/Xfree, nobody known that here then I 
> must learning step by step by myself. I follow as Cygwin/Xfree User 
> Guide. At the Cross compiling(Chapter 2), I can't open a shell on my 
> cross compiling build host. I think,when I double-click at cygwin icon 
> after I created an archive of the content of the /lib and /include. Colud 
> you more explain the step for open a shell on my cross compiling build 
> host for me? And I would like to ask something as:
>      - For step of transfer cygwin-lib.tgz, cygwin-include.tgz to my 
> build host, I will make /cygwin/i686-pc-cygwin/ directory in root, that 
> right? Then I must close cygwin first, and open a shell after, is't it?
>     - How can open a shell on my cross compiling build host?
>    - I install Cygwin/Xfree on Windows98 then tne native host is 
> Windows98 and the built host is Cygwin, don't is?
>
>Thank you for your kindness?
>Ms. Kesrin Hanprasert


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      reply	other threads:[~2002-02-17  4:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-16 19:31 Kesrin Hanprasert
2002-02-16 20:22 ` Randall R Schulz [this message]

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=5.1.0.14.2.20020216200849.023abd20@pop3.cris.com \
    --to=rrschulz@cris.com \
    --cc=cygwin@cygwin.com \
    --cc=kesrin_h@hotmail.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).