[omniORB] Problems building omni2_8_develop branch

[Hinds, Robin]

I wonder if you could give me some advice.  I am trying to build the above
branch of the omniORB tree as downloaded from CVS yesterday.  Initially I
was trying to make it using a B20 version of cygwin and the compilation got
a certain way through and then terminated with the following error...

...      echo "VERSION 8.0" >> omniDynamic2.def; \
         echo "EXPORTS" >> omniDynamic2.def; \
         DUMPBIN.EXE /SYMBOLS ../omniDynamic2.lib | \
         egrep '^[^ ]+ +[^ ]+ +SECT[^ ]+ +[^ ]+ +\(\) +External +\| +\?[^
]*|^[^
 ]+ +[^ ]+ +SECT[^ ]+ +[^ ]+ +External +\| +\?[^?][^ ]*'|\
         egrep -v 'deleting destructor[^(]+\(unsigned int\)' | \
         cut -d'|' -f2 | \
         cut -d' ' -f2 | /bin/sort -u >> omniDynamic2.def; )
+ echo LIBRARY omniDynamic280_rt
+ echo VERSION 8.0
+ echo EXPORTS
+ DUMPBIN.EXE /SYMBOLS ../omniDynamic2.lib
+ egrep ^[^ ]+ +[^ ]+ +SECT[^ ]+ +[^ ]+ +\(\) +External +\| +\?[^ ]*|^[^ ]+
+[^
]+ +SECT[^ ]+ +[^ ]+ +External +\| +\?[^?][^ ]*
+ egrep -v deleting destructor[^(]+\(unsigned int\)
+ cut -d| -f2
+ cut -d  -f2
+ /bin/sort -u
/bin/sort: not found
make[4]: *** [omniDynamic2.def] Error 127
make[3]: *** [export] Error 2
make[2]: *** [export] Error 2
make[1]: *** [export] Error 2
make: *** [export] Error 2

I have set a path to the appropriate cygwin directory but the same problem
occurs.  I thought this may be due to the fact that I was using this beta
version of cygwin.  So I updated the version to cygwin 1.1 and then the
terminated immediatly giving the following error message...

bash-2.04$ make export
: No such file or directory
'.  Stop.onfig.mk to make target `..

I am compiling on a Windows NT4.0 machine and have altered the config.mk
accordingly.  The only other thing is that I am using Visual Studio 6.0
(Visual C++ 6.0).  Again I have set the LIB and INCLUDE variables but the
paths the are added are slightly different since there is no longer a
sharedIDE directory, but I have modified my path and the am able to find
cl.exe, so I presume this is not the problem.

One of my collegues has also found the same problem.  Some advice would be
much appreciated.

Thanks

Rob