From: Eljay Love-Jensen <eljay@adobe.com>
To: frostflare <frostflare@bol.com.br>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: problems compile again
Date: Fri, 02 Apr 2004 16:17:00 -0000 [thread overview]
Message-ID: <6.0.3.0.2.20040402101412.01fbea28@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <HVJVSX$98510363145E35670116C785E1631BFD@bol.com.br>
Hi frostflare,
Because of email line limitations, it's hard to tell which line "line 35"
is. The ioperm function appears incomplete.
It appears you have an old version of CygWin installed.
Use the SETUP.EXE tool, located at <http://www.cygwin.com/> to install an
up-to-date version of CygWin and the GNU utilities. If you have the hard
drive space, I recommend installing everything (not including source code,
unless you really want that too).
HTH,
--Eljay
prev parent reply other threads:[~2004-04-02 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 15:46 frostflare
2004-04-02 16:17 ` Eljay Love-Jensen [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=6.0.3.0.2.20040402101412.01fbea28@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=frostflare@bol.com.br \
--cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).