<html><head></head><body style="text-align:left; direction:ltr;"><div>Hi David,</div><div><br></div><div>Sorry I got a busy week.</div><div><br></div><div>On Mon, 2021-11-15 at 18:50 +1100, David Bannon wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On Sun, 2021-11-14 at 16:40 +0100, Abou Al Montacir wrote:</div><div><br></div><pre>Version: 1:5.2+dfsg-11+deb11u1</pre><div><br></div><div>Hmm, against my 1:4.2 .....</div></blockquote><div>Should not matter too much</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><pre>I think I forgot to say that you need to use the serial rather than the VGA output of QEMU. </pre><div>Use meny View/serial0 or hit Ctrl+Alt+3 (may need shift depending on keyboard).</div><div><br></div><div>I suspect thats more my problem than anything.</div><div><br></div><div>So, I tried connecting via a serial port (wow, long time since I used minicom) and, yes, I can connect to install process that way. But its pretty useless for what I had in mind, I had planned to try and build Lazarus and tomboy-ng, both are GTK (or Qt) apps so, not very useful over a serial interface !</div><div><br></div><div>So, do I assume that the sparc emulation does not do a GUI interface ?</div></blockquote><div>Yes, or needs advanced QEMU knowledge I don't have.</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div><br></div><div>I'm going anyway to check ppc64el for doublecmd on a porter machine, so I may test on it rather than building a qemu image.</div><div><br></div><div>I can build a viable ppc64el vm here so I can do that test for you if you like ? Right now it has a FPC and Lazarus direct from FPC themselves rather than a Debian install but I can 'fix' that.</div></blockquote><div>It ise preferable to use Debian packaged FPC in order to build for Debian. Otherwise you package may FTBFS</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><div>Especially if I can come to grips with this backing_file approach. ;-)</div></blockquote><div>The backing file approache is only for COW (Copy On Write). This allow you to have a VM image that never get corrupted whatever you do.</div><div>It helps testing install/remove/upgrade without breaking your base image, or the need to have a backup image.</div><pre style="caret-color: rgb(46, 52, 54); color: rgb(46, 52, 54); font-variant-caps: normal; letter-spacing: normal; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0.4); -webkit-text-stroke-width: 0px; text-decoration: none;">-- <br></pre><pre style="caret-color: rgb(46, 52, 54); color: rgb(46, 52, 54); font-variant-caps: normal; letter-spacing: normal; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-tap-highlight-color: rgba(0, 0, 0, 0.4); -webkit-text-stroke-width: 0px; text-decoration: none;">Cheers,
Abou Al Montacir</pre><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"></blockquote></body></html>