public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygwin@cygwin.com
Cc: Teun Burgers <burgers@ecn.nl>
Subject: Re: g77 -mno-cygwin failed
Date: Thu, 25 Sep 2003 15:23:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.56.0309251120510.3193@slinky.cs.nyu.edu> (raw)
In-Reply-To: <Pine.GSO.4.56.0309251115420.3193@slinky.cs.nyu.edu>

On Thu, 25 Sep 2003, Igor Pechtchanski wrote:

> On Thu, 25 Sep 2003, Teun Burgers wrote:
>
> > Igor Pechtchanski wrote:
> >
> > > "g77 -mno-cygwin" will most likely call
> > > /usr/lib/gcc-lib/i686-pc-mingw/3.3.1/f771.exe, which should be part of the
> > > "gcc-mingw" package.  Unfortunately, "gcc-mingw" uses a weird packaging
> > > scheme (a tarball inside a tarball), so you couldn't have used the package
> > > search page to find that out.  Judging by the size of the tarball in the
> > > latest "gcc-mingw-20030911-2" package (1.3M) vs. the one in 20020817-5
> > > (2.1M), some files may be missing in the new version.
> >
> > There is a softlink missing in /usr/lib/gcc-lib/i686-pc-mingw32/3.3.1 and
> > hence missing in gcc-mingw-3.3.1-20030804.tar
> > Making this softlink from within this subdir fixes the problem:
> >
> > ln -s ../../i686-pc-cygwin/3.3.1/f771.exe f771.exe
> >
> > Teun
>
> No, no, no!  This will produce an executable linked with Cygwin (as can be
> verified by running "cygcheck" on it).  You don't want that -- you want
> MinGW executables to be regular Windows programs, using MSVCRT.DLL as
> their C/Fortran runtime.
>         Igor

Oops!  Apologies -- you were absolutely correct.  It's the "libgcc.a" that
needs to be Cygwin-independent; the executables are symlinked.

Note to self: verify the data before sending it to the list.  I usually
do.  Honest! :-D
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

  parent reply	other threads:[~2003-09-25 15:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25 14:11 Teun Burgers
2003-09-25 14:42 ` Igor Pechtchanski
2003-09-25 15:16   ` Teun Burgers
2003-09-25 15:20     ` Igor Pechtchanski
2003-09-25 15:22       ` Gerrit P. Haase
2003-09-25 15:23       ` Igor Pechtchanski [this message]
2003-09-25 15:34       ` Teun Burgers
2003-09-25 14:47 ` Roman Belenov
2003-09-25 15:12   ` Gerrit P. Haase
  -- strict thread matches above, loose matches on Subject: below --
2003-09-25  4:59 TX

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=Pine.GSO.4.56.0309251120510.3193@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=burgers@ecn.nl \
    --cc=cygwin@cygwin.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).