This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Fix mingw32 bootstrap regression.


On Sun, Dec 24, 2006 at 03:32:54PM -0500, Bob Rossi wrote:
> On Sun, Dec 24, 2006 at 02:24:08PM +0000, Pedro Alves wrote:
> > 'Bob Rossi' escreveu:
> > >> cc1 -E -lang-asm -quiet ...
> > >>xgcc.exe: CreateProcess: No such file or directory
> 
> > >Why wouldn't gcc be able to find this?
> > MinGW/native Windows apps don't know a thing about the /home/bobbybrasko
> > cygwin mount and xgcc should be a MinGW app.
> > That's why Danny has the following cygwin mount, and he puts the 
> > sources/builddir there:
> > 
> > c:\developex on /developex type system (binmode)
> > 
> > This way, both cygwin and MinGW will resolve the /developex path to the 
> > same dir.
> > (/ on the MinGW side will resolve to the root of the current drive.  )
> 
> Thanks Pedro! That got me further. I have yet another error.

I've narrowed this down further. It's another cygwin/mingw problem.
Basically, in /developex/gcc/trunk/build/mingw32/libstdc++-v3/include
the make command 
  /developex/gcc/trunk/build/./gcc/xgcc -shared-libgcc
  ...
  -I/developex/gcc/trunk/build/mingw32/libstdc++-v3/include/mingw32
  -I/developex/gcc/trunk/build/mingw32/libstdc++-v3/include
  ...
fails with,
  /developex/gcc/trunk/gcc/libstdc++-v3/include/precompiled/stdc++.h:37:19:
  error: cassert: No such file or directory^M
  /developex/gcc/trunk/gcc/libstdc++-v3/include/precompiled/stdc++.h:38:18:
  error: cctype: No such file or directory^M
...

If I do an ls -l /developex/gcc/trunk/build/mingw32/libstdc++-v3/include
which is in the -I section above I see,
  ...
  lrwxrwxrwx  1 bobbybrasko None    59 Dec 26 14:59 cassert ->
  /developex/gcc/trunk/gcc/libstdc++-v3/include/c_std/cassert
  lrwxrwxrwx  1 bobbybrasko None    58 Dec 26 14:59 cctype ->
  /developex/gcc/trunk/gcc/libstdc++-v3/include/c_std/cctype
  ...

Aha! They are symbolic links. I'm pretty sure the mingw compiler doesn't
know anything about this. Is this another configuration issue or a gcc
bootstrap bug?

Danny how do you get past this problem? Have you seen this before?

Thanks,
Bob Rossi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]