public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: "Andrew Sidwell" <nevermiah@hotmail.com>
Cc: cygwin@cygwin.com
Subject: Re: gcc problems
Date: Wed, 02 Jan 2002 14:34:00 -0000	[thread overview]
Message-ID: <4.3.1.2.20020102170410.023a3f88@pop.ma.ultranet.com> (raw)
In-Reply-To: <F40bCECaDxr16ic0Db000009386@hotmail.com>

At 04:41 PM 1/2/2002, Andrew Sidwell wrote:
>>Hello all,
>>  I'm sorry if this has been solved before, but I can't see it on the
>>mailing list archives, so I'm guessing it's not.
>
><snip>
>
>Here's a clarification of the error messages and what caused them:
>
>On a compile using GCC, a little error box with the title 'Error Starting Program' pops up, with the text, "The COLLECT2.EXE file is linked to missing export CYGWIN1.DLL:_ctype_.".
>
>In the Cygwin window itself, there is the message:
>
>gcc: installation problem, cannot exec '/usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/collect2..exe': Permission denied.
>
>I'm using Win98SE, without any bcc tools, etc. installed.
>
>Thanks in advance,
>--
>Andrew Sidwell, takkaria on IRC


How'd you manage to install gcc without binutils?  Did you use setup.exe 
and consciously override the install of binutils (installing gcc will 
install binutils if you tell it not to)?  If you didn't use setup.exe,
then that's your problem.  The solution to either of these two scenarios
is "don't do that"(tm).  The way to avoid these types of problems in 
general is to use setup.exe and do what it tells you unless you're 
absolutely sure that your needs aren't met by setup.exe.  If setup.exe
won't give you what you want, you're free to proceed with any experimental
installation that you like of course.  Unfortunately for you (perhaps),
this list can't invest any time finding the problems in your custom 
configuration, assuming that's what you have or were targetting.  

Hope that helps some,



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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-01-02 22:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02 13:42 Andrew Sidwell
2002-01-02 14:34 ` Larry Hall (RFK Partners, Inc) [this message]
2002-01-02 14:38   ` Larry Hall (RFK Partners, Inc)
2002-01-02 16:58 ` Robert Collins
  -- strict thread matches above, loose matches on Subject: below --
2004-06-29 15:39 GCC problems Larry Hall
2004-06-29 14:28 Robert Golovniov
2004-04-29 23:59 gcc problems Derek Farren Gause
2004-04-30  5:28 ` Christopher Faylor
2002-01-01  8:53 Andrew Sidwell
2001-12-12  9:07 GCC problems gahan
2001-12-12 22:01 ` Tim Prince

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=4.3.1.2.20020102170410.023a3f88@pop.ma.ultranet.com \
    --to=lhall@rfk.com \
    --cc=cygwin@cygwin.com \
    --cc=nevermiah@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).