Re: [Gimp-user] [Hangout - NYLXS] Debian 11, updated, Gimp 2.10.22 - bad clone tool

[Dedeco Balaco via gimp-user-list]

Em 19/10/2021 17:09, Liam R E Quin escreveu:
> 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.

The configure script was and is here. I would be able to understand the
configure file was not in the source directory. Let me show the output
of it, with the options i used:

$ ./configure --with-gimpdir=/dev/shm/.raiz/tmp/ --with-html-dir=/dev/shm/.raiz/
    doc/ --disable-default-binary --with-desktop-dir=/dev/shm/.raiz/bin/ --prefi
    x=/dev/shm/.raiz/
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-li
    nux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format.
    .. func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libr
    aries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking dependency style of gcc... gcc3
checking whether to enable maintainer-specific portions of Makefiles... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for target architecture... x86_64-unknown-linux-gnu
checking for some Win32 platform... no
checking for native Win32... no
checking for library containing strerror... none required
checking whether make sets $(MAKE)... (cached) yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether to turn on debugging... no
checking whether to turn on profiling... no
checking whether gcc understands -Wdeclaration-after-statement... yes
checking whether gcc understands -Wmissing-prototypes... yes
checking whether gcc understands -Wmissing-declarations... yes
checking whether gcc understands -Winit-self... yes
checking whether gcc understands -Wpointer-arith... yes
checking whether gcc understands -Wold-style-definition... yes
checking whether gcc understands -Wformat-security... yes
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking whether time.h and sys/time.h may both be included... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/times.h usability... yes
checking sys/times.h presence... yes
checking for sys/times.h... yes
checking for sys/wait.h... (cached) yes
checking for unistd.h... (cached) yes
checking for pid_t... yes
checking return type of signal handlers... void
checking for vprintf... yes
checking for _doprnt... no
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for fsync... yes
checking for difftime... yes
checking for mmap... yes
checking whether binary relocation support should be enabled... no
checking for _NL_MEASUREMENT_MEASUREMENT... yes
checking whether NLS is requested... yes
checking for intltool >= 0.36.3... 0.51.0 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.32.1
checking for XML::Parser... ok
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for iso-codes... yes
checking for BABL... no
configure: error: Package requirements (babl >= 0.0.22) were not met:

No package 'babl' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables BABL_CFLAGS
and BABL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

$ 


> Unless you have, say, 64G of RAM or more, /dev/shm isn't a good
> destination to use really.

I constantly monitor the use of RAM and swap in my computer. I have 16
GiB of RAM, and 16 GiB of swap. And 32 GiB of memory is a lot more than
i usually need to use, for everything i do. The only memory angry
software i use is a browser, _depending on the site_ i visit, or on the
time it has been running without a full (browser) restart.


>
> 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.

Yes, unfortunately.

> 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.

Yes. Other people said it works fine in 2.10.24 too.

Since one or two days ago, there is a question i have been waiting an
answer, in this list: is the behaviour change i describe in my problem
possible to achieve with normal changes in 2.10.22 settings?


> 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.

I have some accessibility tools actived for me. To see where the mouse
pointer is, i (press and) _release_ the ctrl key, as i show in this
short video:

https://sendvid.com/e6ifmtj8

I am using Mate Desktop in Debian.

> If that's  not what is going  on  for you, try renaming your gimp 
> profile folder and then starting gimp.I

I cannot tell if what i said above explains Gimp's behaviour for me. I
use ctrl + keys and several other shortcuts in all other applications.


_______________________________________________
gimp-user-list mailing list
List address:    gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list