From Newsgroup: comp.os.linux.misc

I'm currently helping a friend upgrade his copy of Darktable.
The latest snag is that the build process wants GCC 12, while
his machine, running Mint 21, only has GCC 11. After scanning
the web for advice, I've tried to upgrade the compiler. At
best I got to where typing "gcc --version" on the command line
reports version 12, but Darktable's build.sh still managed to
find (and reject) the old GCC 11. Any ideas, short of doing
a dist-upgrade to Mint 22?
--
/~\ Charlie Gibbs | In this world there are
\ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
X I'm really at ac.dekanfrus | 1. Those who can extrapolate
/ \ if you read it the right way. | from incomplete data.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On Mon, 03 Aug 2026 06:05:43 GMT, Charlie Gibbs wrote:

... Darktable's build.sh still managed to find (and reject) the old
GCC 11.

Looking at the package source (on Debian), it looks like Darktable
uses CMake to drive its builds. That build.sh is little more than a
wrapper around CMake, and in particular it allows you to pass custom
options to CMake.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-08-03, Lawrence DrCOOliveiro wrote:

On Mon, 03 Aug 2026 06:05:43 GMT, Charlie Gibbs wrote:

... Darktable's build.sh still managed to find (and reject) the old
GCC 11.

Looking at the package source (on Debian), it looks like Darktable
uses CMake to drive its builds. That build.sh is little more than a
wrapper around CMake, and in particular it allows you to pass custom
options to CMake.

There's no configure script?
--
Nuno Silva
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

Am 03.08.26 um 08:05 schrieb Charlie Gibbs:

I'm currently helping a friend upgrade his copy of Darktable.
The latest snag is that the build process wants GCC 12, while
his machine, running Mint 21, only has GCC 11. After scanning
the web for advice, I've tried to upgrade the compiler. At
best I got to where typing "gcc --version" on the command line
reports version 12, but Darktable's build.sh still managed to
find (and reject) the old GCC 11. Any ideas, short of doing
a dist-upgrade to Mint 22?

Is gcc11 still installed?

Maybe it picks that by using a full path.

Is there any reason not to upgrade the OS?
--
Gru|f
Marco

Please send unsolicited mail to dustbin12@stinkedores.dorfdsl.de
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:

I'm currently helping a friend upgrade his copy of Darktable.
The latest snag is that the build process wants GCC 12, while
his machine, running Mint 21, only has GCC 11. After scanning
the web for advice, I've tried to upgrade the compiler. At
best I got to where typing "gcc --version" on the command line
reports version 12, but Darktable's build.sh still managed to
find (and reject) the old GCC 11. Any ideas, short of doing
a dist-upgrade to Mint 22?

The build system should ask which compiler to use. You can set it either
via envars (like CC), switches to the build system, or by editing the
build system files (like Makefile). If it's Cmake, there's a 'ccmake'
something something (read the manual for it). You could install, for
example, /opt/gcc-15/bin and then tell it /opt/gcc-15/bin/gcc for the
compiler.

You might also try temporarily hiding your system compiler, but that's
kind of hacky.

You sure this won't work? https://github.com/darktable-org/darktable/releases/download/release-5.6.0/Darktable-5.6.0-x86_64.AppImage
--
PGP Key ID: 781C A3E2 C6ED 70A6 B356 7AF5 B510 542E D460 5CAE
"The Internet should always be the Wild West!"
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-08-03, Nuno Silva <nunojsilva@invalid.invalid> wrote:

On 2026-08-03, Lawrence DrCOOliveiro wrote:

On Mon, 03 Aug 2026 06:05:43 GMT, Charlie Gibbs wrote:

... Darktable's build.sh still managed to find (and reject) the old
GCC 11.

Looking at the package source (on Debian), it looks like Darktable
uses CMake to drive its builds. That build.sh is little more than a
wrapper around CMake, and in particular it allows you to pass custom
options to CMake.

There's no configure script?

There isn't one called "configure", so "./configure" is not an option.
There is, however, a file called ConfigureChecks.cmake. I've an
old-school guy who's comfortable enough with make that I've never
found a reason to get into the complexities of cmake.
--
/~\ Charlie Gibbs | In this world there are
\ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
X I'm really at ac.dekanfrus | 1. Those who can extrapolate
/ \ if you read it the right way. | from incomplete data.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 2026-08-03, jayjwa <jayjwa@atr2.ath.cx.invalid> wrote:

Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:

I'm currently helping a friend upgrade his copy of Darktable.
The latest snag is that the build process wants GCC 12, while
his machine, running Mint 21, only has GCC 11. After scanning
the web for advice, I've tried to upgrade the compiler. At
best I got to where typing "gcc --version" on the command line
reports version 12, but Darktable's build.sh still managed to
find (and reject) the old GCC 11. Any ideas, short of doing
a dist-upgrade to Mint 22?

The build system should ask which compiler to use. You can set it either
via envars (like CC), switches to the build system, or by editing the
build system files (like Makefile). If it's Cmake, there's a 'ccmake' something something (read the manual for it). You could install, for
example, /opt/gcc-15/bin and then tell it /opt/gcc-15/bin/gcc for the compiler.

You might also try temporarily hiding your system compiler, but that's
kind of hacky.

You sure this won't work? https://github.com/darktable-org/darktable/releases/download/release-5.6.0/Darktable-5.6.0-x86_64.AppImage

No, my buddy has a camera that's new enough that the stock release
can't handle its raw format. We've found and built a modified
libraw.a that works, but we have to fold it into the sources
and re-build it.
--
/~\ Charlie Gibbs | In this world there are
\ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
X I'm really at ac.dekanfrus | 1. Those who can extrapolate
/ \ if you read it the right way. | from incomplete data.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On Tue, 04 Aug 2026 17:44:28 GMT, Charlie Gibbs wrote:

There is, however, a file called ConfigureChecks.cmake.

Files with names ending in rCL.cmakerCY are usually rCLmodulesrCY included
from the actual CMake build scripts for various special functions
(e.g. doing specific checks needed to detect the presence of
particular libraries). The CMake build scripts are the files called rCLCMakeLists.txtrCY you will commonly find scattered through the source directories. The top-level one is the main one, which includes the
others.

I've an old-school guy who's comfortable enough with make that I've
never found a reason to get into the complexities of cmake.

Think of CMake as a rCLmeta-buildrCY system -- a system to drive build
systems. On Linux/Unix, it typically generates files to drive GNU
Make, and I think there is also the option for Ninja as an alternative back-end.

On other platforms, it can generate Visual Studio project files (on
Windows) and XCode project files (on macOS) for driving the
corresponding build tools endemic to those platforms.
--- Synchronet 3.22a-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.misc

On 04/08/2026 18:44, Charlie Gibbs wrote:

Update: my buddy did the upgrade and now has GCC 12. That
should enable us to continue with the project, so I'll
consider the matter closed. Trying to substitute a compiler
that's not part of a given release sounds like too much
work and potential hassle - I've heard horror stories about
"Frankendebian", etc. - so in future I'll just do the full
upgrade (after taking comprehensivce backups, of course).

One way to check if an upgrade is going to work is to configure the
machine for USB boot an install a new OS on a USB drive
--
In theory, there is no difference between theory and practice.
In practice, there is.
-- Yogi Berra

--- Synchronet 3.22a-Linux NewsLink 1.2