Hi Steve, Don't bother. I managed to build it finally. It was (presumably) an incompatibility of the gcc and w32api versions used in my build environment. The new compiler runs fine but with a deterioration in code quality. But that is another story...
Cheers, Ralf "Steve Underwood" <ste...@coppice.org> schrieb im Newsbeitrag news:3f55e3f9.3040...@coppice.org... > Ralf Guetlein wrote: > > >Hi there, > > > >I'm also trying to build my "own" mspgcc. > >Here's my problem: > > > >- Similar setup as loren. See below. > >- Binutils build OK. > >- Build of mspgcc unsuccessful > > > >When I come to the stage where xgcc is called several times to compile > >libgcc.S: > >- the first attempts of xgcc work but need some 10 minutes to run (each) > >- then after a handful of calls to xgcc, it issues an error about a failed > > attempt to allocate about 900 MBytes (!) of mem > > > >Anybody there with the same or similar problems? > >Any suggestions for changing setup? > > > >My build environment is > > > >Athlon XP 2400+ > >512 MB RAM > >Windows XP SP1 > >Binutils 20030307 > >GCC 3.2.3 ( gcc reports version 3.2 20020927. ) > >w32api 2.3 > > > >My sources: > > > >Binutils 2.14 > >GCC 3.3.1 > >MSPGCC 3.4 > > > > I have no idea whether GCC 3.3.1 works with the mspgcc code. I don't > know of anyone else who has tried it. I have never seen the strange > behaviour you describe. You said xgcc works a few times. Does it produce > the correct output? > > Regards, > Steve > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf
