Re: [Gimp-user] [Hangout - NYLXS] Debian 11, updated, Gimp 2.10.22 - bad clone tool
- From: Ken Moffat <zarniwhoop ntlworld com>
- To: 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 18:21:07 +0100
On Tue, Oct 19, 2021 at 01:55:19AM -0400, facebook wrote:
On 10/18/21 21:14, Dedeco Balaco via gimp-user-list wrote:
I gave up compiling Gimp. It is too complex to compile. It demands
libraries of specific versions, and not only this. They also have to be
in specific intervals. Open source? Yes. But to compile it is a hard
work. So... not for normal people who just want to solve simple
problems, or change simple details which cannot be changed in settings.
why does autoconf not just work?
What has autoconf got to do with it ? If you try to compile a
package from git which lacks a configure script but provides
configure.ac, or sometimes if you patch the package, you need to
run autoconf - with the correct switches and, for some packages or
switches, you will need gtk-doc.
But for a normal release just use configure.
ĸen
--
A capitalist society is one where individuals own and acquire
property, at least for a few months until cooler objects come out.
-- Late Night Mash
- 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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]