On Tue, Dec 19, 2006 at 08:45:41PM -0500, Carlos O'Donell wrote:
> On Tue, Dec 19, 2006 at 07:29:17PM -0500, Bob Rossi wrote:
> > I'm sorry. I've run it 2 ways. With prefix=/c/mingw and with
> > prefix=/mingw. prefix=/mingw is the historically correct way to do this
> > from what I understand. I only tried it with /c/mingw once as a test to
> > see if it would work around the problem I found.
> > 
> > With --prefix=/mingw my configure line was,
> > 
> > mkdir gcc-builddir-0
> > cd gcc-builddir-0
> > ../gcc/configure \
> > --disable-werror \
> > --with-gmp=/home/bobbybrasko/gcc/gmp/gmp \
> > --with-mpfr=/home/bobbybrasko/gcc/mpfr/prefixdir \
> > --host=mingw32 \
> > --target=mingw32 \
> 
> What does your 'build' default to?

I'm not sure what you are asking, sorry. Is this what you want to know?
checking host system type... i386-pc-mingw32
checking target system type... i386-pc-mingw32
checking build system type... i386-pc-mingw32

> > --prefix=/mingw \
> > --program-suffix="-4.1" \
> > --with-gcc \
> > --with-gnu-ld \
> > --with-gnu-as \
> > --enable-threads=win32 \
> > --disable-nls \
> > --enable-languages=c,c++ \
> > --disable-win32-registry \
> > --disable-shared \
> > --enable-static \
> > --without-x \
> > --enable-libstdcxx-debug \
> > 2>&1 | tee configure-out.txt
> > 
> > Here was the build line,
> > cd gcc-builddir-0
> > make \
> > CFLAGS="-O2 -fomit-frame-pointer" \
> > CXXFLAGS="-mthreads -fno-omit-frame-pointer -O2" \
> > LDFLAGS=-s \
> > bootstrap 2>&1 | tee make-out.txt
> > 
> > And the debug info was found here,
> >   http://gcc.gnu.org/ml/gcc-patches/2006-12/msg01356.html
> > p->fname=/mingw/include cpp_PREFIX=C:/mingw cpp_PREFIX_len=8
> > 
> > Sorry about the confusion.
> 
> No worries. I'm sorry this broke the bootstrap process. We'll get it
> fixed with a little more work :-)
> 
> I have a new patch for you if you want to try. This one is completely
> untested, but I think it will do what you need.
> 
> If you can test this I would be *very* grateful, and then I can get this
> upstream.

Yup, this get's me past the problem that I was having. I still have the
same problem I've had all along. Maybe you'll know the solution.  

If I do a 
  make DESTDIR=/home/bobbybrasko/gcc/svn-trunk-orig/destdir install
and then I do
  $ PATH=/home/bobbybrasko/gcc/svn-trunk-orig/destdir/mingw/bin:$PATH gcc-4.1 -o main main.c              
I can compile a C hello world program. But if I do,
  $ PATH=/home/bobbybrasko/gcc/svn-trunk-orig/destdir/mingw/bin:$PATH g++-4.1 -o main main.cpp            
  main.cpp:1:20: error: iostream: No such file or directory                                               
  main.cpp: In function 'int main(int, char**)':                                                          
  main.cpp:8: error: 'cout' was not declared in this scope                                                
  main.cpp:8: error: 'endl' was not declared in this scope                                                
I can't compile a C++ hello world program.

Now, if I do 'tar -cvf mingw.tar mingw' and move it to another windows
machine, and then untar binutils, w32api, and mingw-runtime into the
directory and run like,
  set PATH=V:\black\files\gcc\mingw\bin;C:\windows\system32
and then
  gcc-4.1 -o main main.c
it works fine, but
  g++-4.1 -o main main.cpp 
gives the error, can not find iostream. I've attached the output of
g++-4.1 -v -o main main.cpp. If I move the mingw directory on that
machine to C:/mingw, I get the same exact results.

Now, unfortunatly, I confiured svn trunk with suffix -4.1. If I actually
use the gcc 4.1 release, I can get gcc and g++ to work on another
windows machine if it's located in C:/mingw only. Not if it's located in
say C:/foo/mingw.

So, I think things have gone from good 3.x series (used to be completly
relocatable), to bad in 4.1 series (can't relocate to anywhere but
C:/mingw or --prefix perhaps) to worse in svn trunk (can't get it to
work at all.

Now this may be entirely my fault, but at least I can reproduce the
differences between gcc-4.1.1 and trunk.

Any ideas? If not, do you know where I could send in such a problem? No
one seems to be able to help me.

Thanks,
Bob Rossi