Hi Riccardo, I have installed your config and patches, reset the build system, and I have things building.
Will see how it goes! Best, Ken On 2018-01-05, at 3:53 PM, Riccardo Mottola wrote: > Hi Ken, > > Riccardo Mottola via macports-users wrote: >> I actually use a different one, it is not commited (*), I attach it here. >> It disables several problematic features: The goal is currently to "finish >> the build" and see if we start up the browser. >> Slowly we can then debug enable things again, but with a priority. >> It makes no sense to concentrate on the first issue found when there are >> maybe other important features missing. >> >> > > Did you get my patches and build configuration I sent you off-list? > > How fare do you get now? I'm still stuck at the same point before Christmas > > > Riccardo >> >> The miracle didn't happen yet :) >> >> I attach some other local patches whcich are either mere hacks or written in >> a way upsteam does not approve. >> >> 1) stuff to disable SSE2 and AVX2 in libvpx >> 2) patch to disable SKIA completely. It is disabled on current PPC builds, >> might be difficult to enable in the future >> 3) patch to work around some libstdc++ namespace issues. Perhaps there are >> better ways, it is very strange that TT maintainer does NOT have this >> issues, while from some bug I found in GCC and MacPorts they look like >> issues with older OS's. My guess is that a newer version of GCC might help. >> I think the GCC headers are not correctly working around the missing >> functions because "something" is not enabled. The patch comes out of the GCC >> 4.8 headers themselves, but without the ifdef's inside >> >> Since you need to pach configure, I am sorry, but you need to remove your >> build directory and restart from scatch. > > You may apply them blindly or check them one by one. For SKIA you can trust > me, AVX2 is possibly compiler and configuration related, if you use gcc 4.8 > as suggested, go with that one to. > The patch 3) about libstcc is very interesting, since the maintainer doesn't > needed it. You could try without. > >> (**) I just found out that my Mailer GNUMail currently chokes on >> attachments... will send you them in a different way. More details on that >> Later > > Fixed that too :) > > Riccardo
