From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] KPIT GNUSH compiler not sufficient to compile U-Boot under Cygwin
Date: Tue, 31 May 2005 10:08:19 -0400 [thread overview]
Message-ID: <429C6FD3.2040502@smiths-aerospace.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0505310935050.7018@localhost.localdomain>
Robert P. J. Day wrote:
> i went through something very much like this problem a while back,
> where the KPIT compiler was too dense to follow proper cygwin drive
> mappings.
>
> from memory (i don't have the system in front of me at the moment),
> i just created my cygwin home directory on d:\home, and set my
> environment HOME variable to d:\home\rday.
>
> in short, i set up cygwin and my home directory to not rely on any
> cygwin drive mapping, and that seemed to work. go figure.
>
> rday
I suspect the fundamental problem is with NTFS's limitations which
forces cygwin to do work-arounds to implement links and mounts.
Apparently kpit doesn't understand the work-arounds. I would "blame"
NTFS, not cygwin or kpit. Avoiding limitations and thus the
work-arounds is always the most practical solution.
gvb
P.S. I was intentionally generic on limitations and work-arounds...
cygwin itself is a workaround to win2k's limitations ;-)
prev parent reply other threads:[~2005-05-31 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 13:24 [U-Boot-Users] KPIT GNUSH compiler not sufficient to compile U-Boot under Cygwin Jonas Mark *
2005-05-31 13:38 ` Robert P. J. Day
2005-05-31 14:08 ` Jerry Van Baren [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=429C6FD3.2040502@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.