<html><head></head><body><div>On Sun, 2021-11-21 at 16:29 +0100, Abou Al Montacir wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hi David,</div><div><br></div><div>On Wed, 2021-11-17 at 11:05 +1100, David Bannon wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Just an update, I can build tomboy-ng fine on ppc64le using the current</div><div>FPC and Lazarus direct from the FPC. </div><div><br></div><div>I have pushed a new release of tomboy-ng up to my sponsor, Philipp and</div><div>it has pie hardening turned off for ppc64le, something I found</div><div>necessary and believe is worthy of further investigation. </div><div><br></div><div>I have not tested using Sid/Bookworm Debian FPC and Lazarus as they are</div><div>in somewhat of a state of flux at present so, because of that, and the</div><div>PIE issue, will leave this ticket open for now. </div></blockquote><div><br></div><div>What do you mean?</div></blockquote><div><br></div><div>PIE Issues - To make a stable binary for my app, I needed to turn off the hardening for the powerpc64 processor. I cannot, at this stage determine if FPC deliberately supports hardening on POWER, I need to do some more experiments. I suspect (but do not know) that FPC hardening may be limited to x86 and ARM.</div><div><br></div><div>I have not heard back from sponsor Philipp Huebner, (and thats unusual) so he may be unhappy about me disabling PIE Hardening on powerpc64. Honesly, I very much doubt anyone is going to use it there !</div><div><br></div><div>Sid/Bookworm Lazarus - At the time of writing, there was an issue with Lazarus that I think you have fixed already (thanks!) whereby the name of the package disagreed with the name that Lazarus uses internally (as shown in ide/version.inc). This confuses Lazarus when it rebuilds itself. I did not raise a bug because by time I went back to track it down, I found you had already fixed it. </div><div><br></div><div>The problem only arises when using the Lazarus IDE, not when using Lazarus's LCL to build an app. And this problem existed, a few weeks ago, in Bullseye, I have not been back there to test ....</div><div><br></div><div><br></div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>It is perfectly usable for daily usage. Maybe we can open a separate thread for that, or is there a ticket tracking this?</div></blockquote><div><br></div><div>No, no ticket, as you have fixed it in sid/bookworm, I guess you have it under control in bullseye, if you are unsure I can quickly build a fresh Bullseye and test.</div><div><br></div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>2. So, I built from source and the bigide version will not build due</div><div>to lhelp</div></blockquote><div><br></div><div><br></div></blockquote><div><br></div><div>Please open a ticket for that.</div></blockquote><div><br></div><div>OK, will do so (but I don't like logging bugs without trying to fix them myself). Its an assembler problem, FPC seems to make a basecontentprovider.s file that it calls the assembler on and that fails. I don't understand the process. Needs someone who understands POWER assembly code I am afraid. The message is -</div><div><br></div><div><font face="monospace" size="1">lib/powerpc64-linux/basecontentprovider.s:1112: Error: can't resolve `.text.n_basecontentprovider_$$_geturiprefix$ansistring$$ansistring' {.text.n_basecontentprovider_$$_geturiprefix$ansistring$$ansistring section} - `.BASECONTENTPROVIDER_$$_GETURIPREFIX$ANSISTRING$$ANSISTRING' {*UND* section}</font></div><div><br></div><div>It does not prevent me from building my app so should not be discussed in this thread, sorry !</div><div><br></div><div><br></div><div>Davo</div></body></html>