public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Kai Henningsen <kai@cats.ms>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: GCC
Date: Thu, 30 Sep 1999 23:42:00 -0000	[thread overview]
Message-ID: <Pine.HPP.3.96.990914112901.27509A-100000@hp2.xraylith.wisc.edu> (raw)
Message-ID: <19990930234200.K2-kvIM2o8GTNshriu2KDvmhzjwg0Y6C0UTo2FxYf5A@z> (raw)
In-Reply-To: <E11QoD4-0006k0-00@charlotte.intern.cats.ms>

On Tue, 14 Sep 1999, Kai Henningsen wrote:

[ fyi, I've trimmed the To: and Cc: lists ]

> 
> Hmm. Thinking about it, one of the things I think I did shortly before
> the problem was adding /bin in front of the path, which points here:
> 
> bash-2.02$ mount
> Device              Directory           Type         Flags
> f:\cygnus\cygwin-b20\H-i586-cygwin32\bin  /bin                user         binmo
> de
> e:                  /                   user         binmode
> bash-2.02$
> 
> And the cpp crash I looked most into was just typing "cpp" at the
> bash prompt.

Thanks for this piece of information, which makes everything clear.

And there's your problem. The way GCC (both Cygnus' and my versions) finds
where to look for subprograms (eg., cpp.exe, cc1.exe), includes and
libraries is the following: 

1. find where the executable lives. eg., if you invoke gcc.exe as `gcc',
   it'll search through path and find /bin; if you invoke it complete
   pathname, it'll also find /bin.

2. Now, find everything relative to the parent directory of the bin
   directory, ie., /bin/..

3. Look for specs and so on using the prefix '/bin/../'

Now you see why it will fail. If you're going to mount /bin only this way, 
you'll (1) also either have to mount everything else symmetrically like on
Unix, (2) use GCC_EXEC_PREFIX to point to the installation.

Cygwin b20.1 handling of relative pathnames is broken, but good news is
that it's fixed in b21 thanks to cgf's rewrite of path handling code.

Here's the workaround for you:
  
  $ export PATH=/cygdrive/f/cygnus/cygwin-b20/H-i586-cygwin32/bin:/bin:$PATH

Your problem shows up since your installation is on F: drive, and that's
why I didn't catch it the first time.

btw, a better way to run configure is not to fake it into looking into
another directory for the proper shell, but the following:
  
  $ CONFIG_SHELL=</path/to/my/favorite/shell> /src/dir/configure [options]

eg., on HP-UX, it's common to the following:

  $ CONFIG_SHELL=/bin/posix/sh /src/dir/configure [options]

and on Cygwin:

  $ CONFIG_SHELL=bash /src/dir/configure [options]

I also tend to use SHELL variable with make, if Makefiles don't already
have it in there.

  $ make SHELL=bash all

Regards,
Mumit





--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~1999-09-30 23:42 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-23  8:50 GCC hark sng-
1999-08-23  9:59 ` GCC Mumit Khan
1999-08-31 23:49   ` GCC Mumit Khan
1999-09-13  8:01   ` GCC Kai Henningsen
1999-09-13  8:54     ` GCC Mumit Khan
1999-09-14  1:54       ` GCC Kai Henningsen
1999-09-14  9:41         ` Mumit Khan [this message]
1999-09-30 23:42           ` GCC Mumit Khan
1999-09-30 23:42         ` GCC Kai Henningsen
1999-09-30 23:42       ` GCC Mumit Khan
1999-09-30 23:42     ` GCC Kai Henningsen
1999-08-31 23:49 ` GCC hark sng-
  -- strict thread matches above, loose matches on Subject: below --
2008-08-18 11:56 GCC John Emmas
2008-08-18 12:11 ` GCC Hugh Sasse
2008-08-18 12:20   ` GCC John Emmas
2002-05-25  9:46 gcc hongxun lee
2002-01-02  9:14 gcc Givon Zirkind
2002-01-03 16:21 ` gcc Tim Prince
2001-05-07 17:49 gcc Bryan Higgins
2001-05-08  6:00 ` gcc Earnie Boyd
2001-03-31 11:06 gcc John Weeks
2001-03-31 13:06 ` gcc Christopher Faylor
2001-03-31 14:14   ` gcc John Weeks
2001-03-31 14:24     ` gcc Christopher Faylor
2000-11-09 11:01 GCC Earnie Boyd
2000-11-09  7:19 GCC Schaible, Joerg
2000-11-09  7:13 GCC Milan Stanojevic
2000-11-09  7:19 ` GCC Cal Erickson
2000-11-09 10:45   ` GCC Milan Stanojevic
1999-09-14  5:48 GCC Earnie Boyd
1999-09-14  6:54 ` GCC Kai Henningsen
1999-09-30 23:42   ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Earnie Boyd
1999-09-13  8:16 GCC Earnie Boyd
1999-09-14  2:00 ` GCC Kai Henningsen
1999-09-14  9:56   ` GCC Michael V. Nikolaev
1999-09-30 23:42     ` GCC Michael V. Nikolaev
1999-09-30 23:42   ` GCC Kai Henningsen
1999-09-30 23:42 ` GCC Earnie Boyd
1998-11-29 10:34 Gcc Haynes, Dan
1998-11-29  1:32 Gcc Holger Burkarth
1998-11-03 13:49 gcc marc_auslander
1998-07-08 10:01 GCC Earnie Boyd
1998-07-03 16:33 GCC Bruno da Rocha
1997-12-05  6:13 gcc Mark Young (in6)
1997-10-16 20:09 GCC Earnie Boyd
1997-10-15 17:59 GCC David Vang
1997-10-08  2:57 gcc Brad Haack
1997-09-24  2:09 gcc nazg
1997-09-23 13:38 gcc Earnie Boyd
1997-09-22  9:29 gcc Earnie Boyd
1997-09-22  6:23 gcc nazg
1997-09-20  0:35 gcc young lee

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.HPP.3.96.990914112901.27509A-100000@hp2.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=kai@cats.ms \
    /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).