On Sep 7, 2014, at 9:24 PM, Ryan Schmidt <[email protected]> wrote:
> > On Sep 7, 2014, at 10:15 PM, Thomas G Lockhart <[email protected]> > wrote: >> >> #35818 and I’ve just posted a patch. There has been some activity on this >> ticket (which I missed; my email address has changed) but afaict the patches >> already applied plus my small patch file just posted should be enough to get >> a self-consistent build. btw trac would not let me supersede the >> Portfile.diff which was already there so I just posted an additional one. > > I'm looking into this now. Some of your changes are unnecessary or should be > changed, and other changes are needed as well. I'll write in the ticket when > I'm done. > OK. afaict the patch is very small so I’ll be curious to see what was unnecessary and what was wrong. btw, I’ve been occasionally playing with updating omniORB (and omniORBpy) to the latest versions. They have always failed to build and I’d figured it was some breakage in the code for MacOS, but it turns out to be a Portfile problem where /opt/local/include is put on the compiler command line before the build directory paths are listed. If there is an older version of omniORB already installed, and if the include files are not fully compatible, then the build breaks. I’m guessing that it was the stuff added to make sure that the MacPorts compiler flags are used, but the omniORB makefiles are not using things in the expected order. A bad side effect. Will start tracking that down now too… - Tom _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
