mingw-users

Re: [Mingw-users] error Compiling glibc++ on mingw Msys-windows 98 SE

[Rob P. <rob...@gm...>]

No, I did do this from a completely clean freshly untarred source tree.



On Fri, 25 Feb 2005 07:14:34 -0500 (EST), Earnie Boyd
<ea...@us...> wrote:
> 
> <quote who="Rob Pollock">
> > Using these options to configure didn't work... still got errors from
> > build
> > process trying to "use" objects that aren't defined!!!
> >
> > I passed these options to the top level of ./configure.  I tried to
> > configure from
> > within the libstdc++ directory (which is the configure script that
> > these options apply to, i.e. --disable-libstdcxx-pch and
> > --disable-c-mbchar) and got "could not find
> > install.sh in ../../ [etc.] errors".
> >
> 
> You have to add the switches at the top build directory.  

I tried that first.  I still got errors with libstdc++ build trying to
include wchar
support, even with --disable-c-mbchar, so _then_ I tried to configure from 
within the libstdc++ subdirectory.

> > It seems the configure scripts in the lower level directories are
> > called by make in
> > the top level directory.  Maybe make never passes the options down to the
> > lower
> > levels (./gcc ./libstdc++ ./i686-mingw32 etc)
> >
> > I dunno WHATS going on.
> >
> > Do you think cross-compiling under cygwin is a better way to go??
> > (could be the ONLY way to go...)
> >
> 
> The problems you're having shouldn't go away just because you use cygwin
> instead.
> 
> > I thought this would be easier/faster.
> >
> 
> I build gcc with MSYS as a test for MSYS.  It should work for you.
> 
>

Re: [Mingw-users] error Compiling glibc++ on mingw Msys-windows 98 SE

[Alex P. <ap...@st...>]

Eric R. Krause wrote:

> Eric R. Krause wrote:
>
>> Rob Pollock wrote:
>>
>>> Using these options to configure didn't work... still got errors 
>>> from build
>>> process trying to "use" objects that aren't defined!!!
>>
>
> Sure enough, I (finally) got patient enough to wait for libstdc++-v3
> configure to complete under Win98 (I started it up late last night and 
> let it run while I slept), and when I woke up, the build had errored 
> out with the exact same errors that Rob got.
>
> And, whaddya know, in
> $target/libstdc++-v3/include/include/$target/bits/c++config.h[*], I see
>
>   /* #undef _GLIBCXX_HAVE_WCHAR_H */
>
> at line 666.  There is in fact some 'configure' confusion happening.

Evil code! Get an exorcist! ;-)

Re: [Mingw-users] error Compiling glibc++ on mingw Msys-windows 98 SE

[Rob P. <rob...@gm...>]

LOL!!
my sentiments exactly!!!!

line 666.... I just >KNEW< it!!!

Re: various followups.   I will try building from COMMAND.COM (instead
of rxvt)to see if that helps.  But if _that's_ not evil I don't know
_what_ is!!!

Thanks
Rob.

On Fri, 25 Feb 2005 16:59:19 -0800, Alex Perez
<ap...@st...> wrote:
> >
> > at line 666.  There is in fact some 'configure' confusion happening.
> 
> Evil code! Get an exorcist! ;-)
> 
> 
>

Re: [Mingw-users] error Compiling glibc++ on mingw Msys-windows 98 SE

[Eric R. K. <ekr...@ba...>]

Rob,

I give up on this one (for now, at least).  It's looking more and more 
like the problem is an interaction between Windows 9x and the way Cygwin 
1.3.x (and therefore MSYS) emulates the fork() function.

I believe bash forks to handle if/else constructs.  And the libstdc++-v3 
configure contains an if/else with two very long branches.  Such large 
scripts (and if/else branches) appear to choke bash on Windows, 
particularly on Windows 9x.


Eric

Re: [Mingw-users] error Compiling glibc++ on mingw Msys-windows 98 SE

[Rob P. <rob...@gm...>]

Thanks Eric,

Yup I think giving up is not a bad idea for now (I have).  Overall, it
hasn't been too bad since gcc itself built fine, but for g++/libstdc++
I might just have to try cross-compiling on my linux box instead
(something I wasn't planning on getting into). But that should keep me
amused for a while.

Thanks very much for all your efforts.  I can't afford to upgrade this
machine to Windows 2000 at the moment, and we need windows for various
reasons, so hence the reason for battling it out on Win9x.

cheers,
Rob Pollock.




On Fri, 25 Feb 2005 23:03:36 -0500, Eric R. Krause <ekr...@ba...> wrote:
> Rob,
> 
> I give up on this one (for now, at least).  It's looking more and more
> like the problem is an interaction between Windows 9x and the way Cygwin