gcc can't find cpp

[Allan Peda]

Welcome news that the directory structure may be simplified.

>From my perspective the confusion stems from trying to use cygwin to undertand the
gcc compilation process.  This being the case, it may be sufficient to simply
outline the steps to streamlining the directory heirarchy after installation.
Things like - libs should be /here/here mounted from (\Win32here\Win32here)
referenced by the environmental variable LIBPATH (%LIBPATH%) headers here, bins
are here and here- etc.

Someone else (yeah maybe me) could  perhaps write a script, or (avoiding using
bash to install bash) a simple ANSI C based launch program checks things and set
envir variables to the new simpler values if the dir tree is ok (using file tests,
whatever).

Just a thought.



Geoffrey Noer wrote:

> On Thu, Jan 14, 1999 at 10:55:11AM -0600, Vince Rice wrote:
> [...]
> > gcc is happily executing now. Now, if we can just convince Geoffrey to use a
> > directory structure someone besides a Martian can read <bg>.
>
> Hey, you callin' me a Martian?  :-)
>
> The directory structure we use in the Net distributions matches the
> official Cygnus release structure for the most part.  It's set up to
> cope with having a single tree that contains native and
> cross-compilers for different hosts.  Most people under Win32 don't
> need this complex a structure which is why a fair number of people
> complain about it.
>
> That said, it's possible we should change the structure for the Net
> distributions.  We'll think about it...
>
> --
> Geoffrey Noer
> noer@cygnus.com
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".