FollowUp/RE: RTEMS-gcc-2.95.1 Build Question

[Jmills at TGA.com (John Mills)]

Marc, et al -

MS- If you really must use Winnt, it might be better to 
MS- run linux in a virtual machine (eg vmware) for the 
MS- purposes of compiling rtems.

Thanks for your comments.

I am building in Linux (RH6.0), but can't run 'bit sh' successfully when my
GCC choice is 'gcc-2.95.1'. I have been more successful linking,
configuring, and building "by hand" with simple scripts in the sequence
suggested for 'Using MS-Windows ...". In WinNT, make-3.77 still fails to
recurse into 'build_rtems' subdirectories (even after trying David Fiddes'
advice). That's another battle for another day, and not principally in my
behalf! &;^)

My failure to build
'.../tools/build-sh-tools/<CPU>-rtems/libiberty/libstdc++.a' through missing
*.h files also occurs when I run 'bit sh' in a fresh set of patched sources.
I do notice that 'bit' did not delete 'egcs-1.1b/gcc/f/' and
'egcs-1.1b/gcc/objc' from 'src/gcc'. I get a clean 'bit' run if I do this
manually; I had expected it was done by 'bit' or 'common.sh'.

I will try again with 'gcc-2.95.1', linked in place of 'egcs-2.95.1' into
'src'.

  John Mills, Sr. Software Engineer
  TGA Technologies, Inc.
  100 Pinnacle Way, Suite 140
  Norcross, GA 30071-3633
  e-mail: jmills at tga.com
  Phone: 770-441-2100 ext.124 (voice)
         770-449-7740 (FAX)