<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">took you how long to think of a recovery, which is embedded with lies?<br class=""><br class="">rootie, are you going to do something about this pathological liar? should i dig up the tickets where he makes baseless accusations and never responds because he likes to abuse his power?<br class=""><br class="">anyways let’s revisit his post, which he conveniently truncates in his response to the mailing list:<br class=""><br class=""><blockquote type="cite" class="">Well -- of course 10.6-PPC needs lots and lots and lots and lots of special workarounds.<br class=""><br class="">10.6-PPC is basically 10.5 PPC wearing lipstick and a wig.<br class=""><br class=""><b class="">It is very very different from 10.6 / Intel / libc++. It builds with gcc, not clang. It links against libstdc++, nott libc++</b>. It does not have the 10.6 kernel features or framework / library supports. It is much more like an early version of 10.5, which is why you need special workarounds all over the damn place for it to make it behave like 10.5 even though it reports itself as 10.6<br class=""><br class=""></blockquote><br class="">question: where in ken cunningham’s response above, is his implication (given) obvious? <br class="">answer: it isn’t because that’s not what he said. he’s lying to salvage his hunger to appear intelligent to this list.<br class=""><br class="">what this liar stated was that 10.6-ppc uses libc++ and that the 10.6-x86_64 variant does not.<br class=""><br class="">but this is what ken does: he lies and puts words in others mouths, just like his unrelenting attacks on my nodejs patches, which he stopped after i asked pointed questions.<br class=""><br class="">you should be careful ken. it’s pretty obvious, when someone gathers your responses and attitude towards me, where it’s coming from.<br class=""><br class="">be very careful. <br class=""><br class=""><blockquote type="cite" class="">On Jan 26, 2025, at 4:51 PM, Ken Cunningham <<a href="mailto:ken.cunningham.webuse@gmail.com" class="">ken.cunningham.webuse@gmail.com</a>> wrote:<br class=""><br class="">MacPorts defaults all builds on 10.6 to libc++, and has done for YEARS now, exactly so that supporting 10.6 won't be a huge, silly project of workarounds.<br class=""><br class="">libsdtc++ is supported only so far as it takes to bootstrap libc++<br class=""><br class="">Everything else you said was pretty much drivel, as usual, and I'll just leave it fester.<br class=""><br class="">Ken<br class=""><br class=""><br class=""></blockquote><br class=""></body></html>