Since I mentioned my problems with trying to start debugging a debug build
of hugin, I'll describe the partial answer I've found so far. Maybe anyone
else who would try to debug hugin would already know this stuff. But in
case that is not true:
I think CodeBlocks was failing because the under
On Wed, 2022-01-26 at 14:09 -0800, johnfi...@gmail.com wrote:
> On Saturday, January 22, 2022 at 10:39:36 AM UTC-5 johnfi...@gmail.com wrote:
>
> I ran make -j16
> Meanwhile I ran system monitor to see that about half my cpu capacity was in
> use
>
> Then my system crashed. Seemed to be a displ
On Saturday, January 22, 2022 at 10:39:36 AM UTC-5 johnfi...@gmail.com
wrote:
I ran make -j16
Meanwhile I ran system monitor to see that about half my cpu capacity was
in use
Then my system crashed. Seemed to be a display driver crash. Maybe there
is some problem in building hugin with j16,
On Saturday, January 22, 2022 at 1:27:25 PM UTC-5 bruno...@gmail.com wrote:
> The
> standard nouveau driver might not have all the top features, but in my
> experience it is very stable.
>
My experience has been very different. Years ago at work, I was using
several Centos systems with va
On Sat, 22 Jan 2022 at 15:39, johnfine2017 wrote:
> I got build instructions both from
> https://wiki.panotools.org/Hugin_Compiling_Fedora
> and from a recent post by Bruno suggesting
> The list of things to install is very different between those two sources.
> Is that first one obsolete?
The
I wanted to start this thread, even though I don't have a lot to ask/report
yet, because I'll otherwise forget things, and because someone might have
some useful feedback on what I have so far.
uname -a reports
Linux linux 5.15.15-200.fc35.x86_64 #1 SMP Sun Jan 16 17:37:06 UTC 2022
x86_64 x86_6
