Re: [Gimp-user] [Hangout - NYLXS] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- From: Liam R E Quin <liam holoweb net>
- To: Dedeco Balaco <dedeco balaco yahoo com>, gimp-user-list gnome org
- Subject: Re: [Gimp-user] [Hangout - NYLXS] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Date: Tue, 19 Oct 2021 16:09:40 -0400
On Tue, 2021-10-19 at 15:48 -0300, Dedeco Balaco via gimp-user-list
wrote:
why does autoconf not just work?
[...]
. And the error is not in 'autoconf', but when i try the first
step: './configure'
Should i start it differently?
If the error is "configure: not found" or
bash: ./configure: No such file or directory
you need to run autogen.sh, using the --prefix=$HOME/opt option.
Unless you have, say, 64G of RAM or more, /dev/shm isn't a good
destination to use really.
To build GIMP 2.10.28 on an older Debian Linux, you will need to start
with building the following:
libmypaint (the 1.3 branch)
libgtk+2, libgdk2, glib from gnome, using jhbuild
babl (with meson; i'm not sure autoconf is still supported for babl and
gegl)
gegl
Install ALL of these into a custom prefix - if you put them into
/usr/local or / you will break your system.
Some of these have additional dependencies themselves.
GIMP is a very large and complex program.
Then finally you can take the gimp 2.10.28 source tarball and run
./autogen.sh --help, which will take a while and then list options.
Then you can run it again with the options you need -- including --
prefix above all.
But the Wiki page i shared with you the other day says all of this and
more.
If you want to build _older_ GIMP releases, don't bother - you'll need
to run them in a virtual machine with the appropriate Linux release in
it, e.g. using docker.
And having said all of that, you do not need to rebuild GIMP to get
clone working without the Alt key. I just tried here and it works
fine.
The one time i've seen a problem with Clone was when i had some
accessibility options enabled that show the current location of the
mouse pointer with concentric rings when i press control - with that
enabled the clone tool stopped working.
If that's not what is going on for you, try renaming your gimp
profile folder and then starting gimp.
Liam
--
Liam Quin - https://www.fromoldbooks.org/
with fabulous vintage art and fascinating texts to read.
https://www.delightfulcomputing.com/
Full-time "slave" in voluntary servitude
- References:
- [Gimp-user] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Re: [Gimp-user] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Re: [Gimp-user] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Re: [Gimp-user] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Re: [Gimp-user] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Re: [Gimp-user] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Re: [Gimp-user] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Re: [Gimp-user] [Hangout - NYLXS] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- Re: [Gimp-user] [Hangout - NYLXS] Debian 11, updated, Gimp 2.10.22 - bad clone tool
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]