www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/12/28/14:13:27

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 28 Dec 2004 14:13:15 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Rainer Dunker <rainer DOT dunker AT web DOT de>
cc: cygwin AT cygwin DOT com
Subject: Re: gcc installation problem and solution
In-Reply-To: <1847507151@web.de>
Message-ID: <Pine.GSO.4.61.0412281409110.1357@slinky.cs.nyu.edu>
References: <1847507151 AT web DOT de>
MIME-Version: 1.0

On Tue, 28 Dec 2004, Rainer Dunker wrote:

> Having installed gcc (package version 3.3.3-3, cygwin.dll 1.5.10-3,
> WinNT 4), I had the following problem:
>
> # gcc helloworld.c -o helloworld
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../i686-pc-cygwin/bin/ld: installation problem, cannot exec `/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../i686-pc-cygwin/bin/ld': Invalid argument
> collect2: ld returned 255 exit status
>
> Moreover, a popup window appeared after the gcc call, saying that NTVDM
> complains about an invalid instruction.
>
> This turned out to be a problem of the gcc installation. The directory
> /usr/i686-pc-cygwin/bin contained these entries:
>
> -rwxr-xr-x    1 myname     mkgroup_       26 Dec 27 15:11 ar.exe*
> -rwxr-xr-x    1 myname     mkgroup_       26 Dec 27 15:11 as.exe*
> -rwxr-xr-x    1 myname     mkgroup_       26 Dec 27 15:11 ld.exe*
> -rwxr-xr-x    1 myname     mkgroup_       26 Dec 27 15:11 nm.exe*
> -rwxr-xr-x    1 myname     mkgroup_       30 Dec 27 15:11 ranlib.exe*
> -rwxr-xr-x    1 myname     mkgroup_       29 Dec 27 15:11 strip.exe*
>
> These are supposed to be symbolic links to the executables in the
> /usr/bin directory, but - for whatever reason - the setup program did
> not install them in a way that they were used as symlinks afterwards
> (for example, ar.exe is a text file with contents
> "!<symlink>/usr/bin/ar.exe"). So I removed them and created symlinks to
> the proper executables manually; after that, the problem was gone.
>
> I'm posting this here because I've not yet found any hint directly
> pointing from the mentioned error messages to this specific problem
> cause.
>
> Best regards,
> Rainer

Please review and follow the Cygwin problem reporting guidelines at
<http://cygwin.com/problems.html>, particularly the bit about attaching
(as an uncompressed text *attachment*) the output of "cygcheck -svr" on
your system.  In the absense of these details, here's a guess:

Did you install Cygwin on a remote share?  If so, see
<http://cygwin.com/faq/faq_3.html#SEC66>.  BTW, it's the only entry about
"symlinks" in the FAQ.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019