[omniORB] Building omniORB 304 on RH 7.1 with gcc 2.96

[Duncan Grisby]

On Monday 29 April, Patrick Hubert wrote:

> In other words, what is the purpose/reason of the 'external_merge'
> presence in the path?

Yes, you should remove the external_merge. It's there because the gcc
2.96 platform file accidentally escaped from the internal build system
used at AT&T. At AT&T we had a slightly different (even more complex,
if you can believe that!) build system. For the external release, the
files in a directory called external_merge were overlaid on the
internal version.

Now that AT&T Labs Cambridge is history, so is the external_merge
mechanism, but some of its effects live on.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --