On Tue, 5 Feb 2013 14:32:51 +0100 Jeroen Hegeman <[email protected]> wrote:
> Hi Parafin, > > > libstdc++ has nothing to do with MAC_OS_X_VERSION_MAX_ALLOWED, this > > macro is needed so that error will be produced if some function > > introduced after 10.6 release is used in code instead of failing in > > runtime (it has already happened once). > > Aha, thanks. That makes sense. > > > Why do you insist on using macports g++? > > I don't insist on anything. If possible, however, I would prefer not to muck > about with things like gcc_select too often. For some things on this machine > I need a version of GCC that is more recent than the one Apple provided, so > 4.6 is the default. I just know that I will forget to switch compilers at > some point in time for those things that need a different version. So if > Darktable works with the MacPorts GCC there is one less occasion for me to > make this mistake. The problem with libstdc++ is general one on OS X, not specific for darktable. So making GCC 4.6 a default compiler is a mistake. In any case you don't have to use gcc_select, there are CC and CXX variables. > > > Anyway, it's your time to > > waste, so go ahead and test it yourself. > > My apologies. I thought you would appreciate the feedback. It is known not to work, even macports guys did acknowledge that after some convincing. I know darktable builds with macports GCC 4.6, I did it myself. So if you manage to avoid triggering any crashes - good for you, but it's pretty useless information for us in general. No offense. > > Best regards, > Jeroen ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
