Lpc2000

Hi All,

Some times are just weird....

I was happily running GNUARM 3.4.3 on my laptop, with a full
install of Cygwin (a leftover from my adventures with Eclipse,
it ran fine without that as well, when I just checked the
'install Cygwin libs' box during install.)

Then, three things were done on that laptop:

- I upgraded the virus scanner to a more recent version
- I un-installed the Cygwin stuff, as it was __large__ and
completely unused, other than the DLL's for GNUARM, and
then re-installed GNUARM 3.4.3, but with the checkbox set,
for local libs.
- I also installed MSPGCC, for the TI 430, which also uses
(its own copy of) the Cyg dll's.

Now... since that, I am no longer able to run GCC. Not the
ARM version, and not the MSP version. I uninstalled the lot,
reinstalled only GNUARM, even tried one with (again !) the
entire Cygwin system... nada!

GCC kinda works, or, rather, all the small tools seem to
work, but GCC itself bombs out when trying to compile just
about anything:

--------------------
arm-elf-gcc -mcpu=arm7tdmi -mthumb-interwork -std=gnu99 -Os -gdwarf-
2 -Wall -msoft-float -Wstrict-prototypes -Wimplicit -Wshadow -
Wunused -Wmissing-declarations -Wmissing-prototypes -Wnested-
externs -Wpointer-arith -Wredundant-decls -Wreturn-type -Wstrict-
prototypes -Wswitch -I./include -DE2294 -I. -c conf.c -o conf.o

arm-elf-gcc: Internal error: Segmentation fault (program cc1)
Please submit a full bug report.

See <URL:http://gcc.gnu.org/bugs.html> for instructions.
---------------------

As said, I have tried just about every combination of install
sequences, including disabling the virusscanner, to no avail.

Is there a way to track down where cc1 is dying?

It could be that it is trying to load a Cyg dll that doesn't
exist, for example, but how do we check/trace that ?

Thanks lots for any help,

Fred




[Non-text portions of this message have been removed]

DECwiz (Fred van Kempen) wrote:

>--------------------
>arm-elf-gcc -mcpu=arm7tdmi -mthumb-interwork -std=gnu99 -Os -gdwarf-
>2 -Wall -msoft-float -Wstrict-prototypes -Wimplicit -Wshadow -
>Wunused -Wmissing-declarations -Wmissing-prototypes -Wnested-
>externs -Wpointer-arith -Wredundant-decls -Wreturn-type -Wstrict-
>prototypes -Wswitch -I./include -DE2294 -I. -c conf.c -o conf.o
>
>arm-elf-gcc: Internal error: Segmentation fault (program cc1)
>Please submit a full bug report.
>
>See <URL:http://gcc.gnu.org/bugs.html> for instructions.
>---------------------
>
>As said, I have tried just about every combination of install
>sequences, including disabling the virusscanner, to no avail.
>
>Is there a way to track down where cc1 is dying?
>
>It could be that it is trying to load a Cyg dll that doesn't
>exist, for example, but how do we check/trace that ?
>
>  
>
Maybe it's just problem with different versioni of cygwin1.dll (or 
whatever it's name)?
Maybe different toolsets are using different versions? IIRC I got 
similar problems ;-(

-- 
Jerzy Lelusz
Electronics Engineer

Geola Technologies Ltd
Sussex Innovation Centre
Science Park Square
BN1 9SB Falmer, East Sussex
United Kingdom
phone: +44 1273 704 443
fax:   +44 1273 704 477

On Thursday 01 September 2005 00:26, DECwiz (Fred van Kempen) wrote:
> Hi All,
>
> Some times are just weird....
>
> I was happily running GNUARM 3.4.3 on my laptop, with a full
> install of Cygwin (a leftover from my adventures with Eclipse,
> it ran fine without that as well, when I just checked the
> 'install Cygwin libs' box during install.)
>
> Then, three things were done on that laptop:
>
> - I upgraded the virus scanner to a more recent version
> - I un-installed the Cygwin stuff, as it was __large__ and
> completely unused, other than the DLL's for GNUARM, and
> then re-installed GNUARM 3.4.3, but with the checkbox set,
> for local libs.
> - I also installed MSPGCC, for the TI 430, which also uses
> (its own copy of) the Cyg dll's.
>
> Now... since that, I am no longer able to run GCC. Not the
> ARM version, and not the MSP version. I uninstalled the lot,
> reinstalled only GNUARM, even tried one with (again !) the
> entire Cygwin system... nada!
>
> GCC kinda works, or, rather, all the small tools seem to
> work, but GCC itself bombs out when trying to compile just
> about anything:

My preference is to install gygwin from the cygwin site and then install 
gnuarm **without installing the DLLs that come with gnuarm**.


I have found that this always works for me but other combos had various probs.