Available for test: gcc-3.1.1-2 gcc2-2.95.3-8

Conrad Scott Conrad.Scott@dsl.pipex.com
Fri Jul 12 12:19:00 GMT 2002


"Christopher Faylor" <cgf@redhat.com> wrote:
> Adding an included path should not be necessary.  g++ -v should
> tell you why it can't find new.

I forgot to say so in the original email, but I assume the problem
is due to the -nostdinc++ that the cygwin DLL build uses, which is
why I thought it the include path should be added in the makefile.
But this is all from the easy position of little understanding :-)

The output from g++ -v is:

GNU CPP version 3.1.1 20020706 (prerelease) (cpplib) (80386, BSD
syntax)
#include "..." search starts here:
#include <...> search starts here:
 .
 /pack/src/cygwin/cygwin_daemon/winsup/cygwin/include
 /pack/src/cygwin/cygwin_daemon/winsup/cygwin
 /pack/src/cygwin/cygwin_daemon/newlib/libc/sys/cygwin
 /pack/src/cygwin/cygwin_daemon/newlib/libc/include
 /pack/src/cygwin/cygwin_daemon/newlib/libc/sys/cygwin/include
 /pack/src/cygwin/cygwin_daemon/winsup/w32api/include
 ../../../../cygwin_daemon/winsup/cygwin/config/i386
 /usr/lib/gcc-lib/i686-pc-cygwin/3.1.1/include
End of search list.
In file included from
../../../../cygwin_daemon/winsup/cygwin/cygserver_transport.cc:22:
../../../../cygwin_daemon/winsup/cygwin/safe_memory.h:25:15:
warning: new: No such file or directory

// Conrad





More information about the Cygwin-developers mailing list