Re: Problem building pidgin (talkatu)
What branch are you on? Bitbucket removed mercurial support multiple years ago.. Or more specifically, where did you clone pidgin from? The canonical repository is at https://keep.imfreedom.org/pidgin/pidgin/ and the default branch is up to date and pointing to the proper talkatu repository at https://keep.imfreedom.org/talkatu/talkatu. On Sun, Apr 3, 2022 at 1:46 PM Konstantin Kharlamov wrote: > Regarding the error: it is trying to fetch talkatu repo, but the repo was > deleted, which is why you're getting a 404. This really should be reported > to > the developers. It is trivial to fix: just replace (I presume in > meson.build, > but am not sure, you might want to grep for the string over the sources) > the > > https://bitbucket.com/pidgin/talkatu > > with > > https://keep.imfreedom.org/talkatu/talkatu/ > > that's the new URL of the repo. > > With that said: I am not sure you're really doing the correct thing. You > see, > you're trying to build a 3.0 version of Pidgin, that's the development > version, > which AFAIK has major changes to plugin API. Latest stable Pidgin release > is > 2.14.8. > > Is there any particular reason you're trying to build Pidgin from sources? > It is > usually in repositories of all distros, so there should be no reason in > doing > that other than wanting to do the Pidgin development (not even a plugin > development, that one doesn't require building Pidgin from sources). > > On Sun, 2022-04-03 at 14:19 -0400, Ralph Hyre (edu edition) wrote: > > I've not seen 400 errors before, but it seems that the attempt to build > > talkatu - as part of a pidgin source build, is causing one. > > > > ralphw7@asimov:~/src/pidgin/Pidgin-master$ meson build > > The Meson build system > > Version: 0.53.2 > > Source dir: /home/ralphw7/src/pidgin/Pidgin-master > > Build dir: /home/ralphw7/src/pidgin/Pidgin-master/build > > Build type: native build > > Project name: pidgin > > Project version: 3.0.0-devel > > C compiler for the host machine: cc (gcc 9.4.0 "cc (Ubuntu > > 9.4.0-1ubuntu1~20.04.1) 9.4.0") > > C linker for the host machine: cc ld.bfd 2.34 > > Host machine cpu family: x86_64 > > Host machine cpu: x86_64 > > Program sed found: YES (/usr/bin/sed) > > Program mkmesonconf.py found: YES > > (/home/ralphw7/src/pidgin/Pidgin-master/mkmesonconf.py) > > Has header "sys/wait.h" : YES > > Has header "fcntl.h" : YES > > Has header "unistd.h" : YES > > Has header "stdint.h" : YES > > Checking for size of "time_t" : 8 > > Checking for function "inet_aton" : YES > > Checking for function "gethostent" : YES > > Checking for function "socket" : YES > > Checking for function "getaddrinfo" : YES > > Checking for function "inet_ntop" : YES > > Checking for function "getifaddrs" : YES > > Header has symbol "socklen_t" : YES > > Checking whether type "struct sockaddr" has member "sa_len" : NO > > Header has symbol "IPV6_V6ONLY" : YES > > Library m found: YES > > Found pkg-config: /usr/bin/pkg-config (0.29.1) > > Run-time dependency glib-2.0 found: YES 2.64.6 > > Run-time dependency gio-2.0 found: YES 2.64.6 > > Run-time dependency gobject-2.0 found: YES 2.64.6 > > Run-time dependency gthread-2.0 found: YES 2.64.6 > > Found CMake: /usr/bin/cmake (3.16.3) > > Run-time dependency gobject-introspection-1.0 found: NO (tried pkgconfig > > and cmake) > > Run-time dependency gtk+-3.0 found: YES 3.24.20 > > Run-time dependency talkatu found: NO (tried pkgconfig and cmake) > > abort: HTTP Error 404: Not Found > > Traceback (most recent call last): > > File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line > 129, > > in run > > return options.run_func(options) > > File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 245, > in > > run > > app.generate() > > ... more python stack trace > > File "/usr/lib/python3.8/subprocess.py", line 364, in check_call > > raise CalledProcessError(retcode, cmd) > > subprocess.CalledProcessError: Command '['/usr/bin/hg', 'clone', ' > > https://bitbucket.com/pidgin/talkatu', 'talkatu']' returned non-zero > exit > > status 255. > > > > What's the run-time dependency trying to be resolved here? > > > > All I had to do so far, was install gtk3 and the meson build environment. > > > > I'm on ubuntu 20.04:lsb_release -a > > No LSB modules are available. > > Distributor ID: Ubuntu > > Description: Ubuntu 20.04.4 LTS > > Release: 20.04 > > Codename: focal > > ___ > > Support@pidgin.im mailing list > > Want to unsubscribe? Use this link: > > https://lists.pidgin.im/listinfo/support > > ___ > Support@pidgin.im mailing list > Want to unsubscribe? Use this link: > https://lists.pidgin.im/listinfo/support -- Thanks, -- Gary Kramlich ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://lists.pidgin.im/listinfo/support
Re: Problem building pidgin (talkatu)
Regarding the error: it is trying to fetch talkatu repo, but the repo was deleted, which is why you're getting a 404. This really should be reported to the developers. It is trivial to fix: just replace (I presume in meson.build, but am not sure, you might want to grep for the string over the sources) the https://bitbucket.com/pidgin/talkatu with https://keep.imfreedom.org/talkatu/talkatu/ that's the new URL of the repo. With that said: I am not sure you're really doing the correct thing. You see, you're trying to build a 3.0 version of Pidgin, that's the development version, which AFAIK has major changes to plugin API. Latest stable Pidgin release is 2.14.8. Is there any particular reason you're trying to build Pidgin from sources? It is usually in repositories of all distros, so there should be no reason in doing that other than wanting to do the Pidgin development (not even a plugin development, that one doesn't require building Pidgin from sources). On Sun, 2022-04-03 at 14:19 -0400, Ralph Hyre (edu edition) wrote: > I've not seen 400 errors before, but it seems that the attempt to build > talkatu - as part of a pidgin source build, is causing one. > > ralphw7@asimov:~/src/pidgin/Pidgin-master$ meson build > The Meson build system > Version: 0.53.2 > Source dir: /home/ralphw7/src/pidgin/Pidgin-master > Build dir: /home/ralphw7/src/pidgin/Pidgin-master/build > Build type: native build > Project name: pidgin > Project version: 3.0.0-devel > C compiler for the host machine: cc (gcc 9.4.0 "cc (Ubuntu > 9.4.0-1ubuntu1~20.04.1) 9.4.0") > C linker for the host machine: cc ld.bfd 2.34 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program sed found: YES (/usr/bin/sed) > Program mkmesonconf.py found: YES > (/home/ralphw7/src/pidgin/Pidgin-master/mkmesonconf.py) > Has header "sys/wait.h" : YES > Has header "fcntl.h" : YES > Has header "unistd.h" : YES > Has header "stdint.h" : YES > Checking for size of "time_t" : 8 > Checking for function "inet_aton" : YES > Checking for function "gethostent" : YES > Checking for function "socket" : YES > Checking for function "getaddrinfo" : YES > Checking for function "inet_ntop" : YES > Checking for function "getifaddrs" : YES > Header has symbol "socklen_t" : YES > Checking whether type "struct sockaddr" has member "sa_len" : NO > Header has symbol "IPV6_V6ONLY" : YES > Library m found: YES > Found pkg-config: /usr/bin/pkg-config (0.29.1) > Run-time dependency glib-2.0 found: YES 2.64.6 > Run-time dependency gio-2.0 found: YES 2.64.6 > Run-time dependency gobject-2.0 found: YES 2.64.6 > Run-time dependency gthread-2.0 found: YES 2.64.6 > Found CMake: /usr/bin/cmake (3.16.3) > Run-time dependency gobject-introspection-1.0 found: NO (tried pkgconfig > and cmake) > Run-time dependency gtk+-3.0 found: YES 3.24.20 > Run-time dependency talkatu found: NO (tried pkgconfig and cmake) > abort: HTTP Error 404: Not Found > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mesonbuild/mesonmain.py", line 129, > in run > return options.run_func(options) > File "/usr/lib/python3/dist-packages/mesonbuild/msetup.py", line 245, in > run > app.generate() > ... more python stack trace > File "/usr/lib/python3.8/subprocess.py", line 364, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['/usr/bin/hg', 'clone', ' > https://bitbucket.com/pidgin/talkatu', 'talkatu']' returned non-zero exit > status 255. > > What's the run-time dependency trying to be resolved here? > > All I had to do so far, was install gtk3 and the meson build environment. > > I'm on ubuntu 20.04:lsb_release -a > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 20.04.4 LTS > Release: 20.04 > Codename: focal > ___ > Support@pidgin.im mailing list > Want to unsubscribe? Use this link: > https://lists.pidgin.im/listinfo/support ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://lists.pidgin.im/listinfo/support
Re: Problem building Pidgin.
On 5/5/21 11:16 AM, DAVID MAY wrote: > I also tried building Pidgin 2.14.4 with MSYS2. Documentation, such as > it is, assumes a Cygwin environment but suggests MSYS (not MSYS2) can be > used with "tweaks" to the build scripts. You need a win32-dev directory that contains all of our dependencies. The easiest way to get that right now is from https://data.imfreedom.org/pidgin/win32-dev.7z > Anyway running configure results in the following error: > > ... > checking for inet_aton... no > checking for inet_aton in -lresolv... no > configure: error: inet_aton not found Pidgin 2 on windows doesn't use autotools. You build it using `make -f Makefile.mingw` in the root of the source code. > Looking at the Pidgin 2.14.4 source code there are multiple bare > inet_aton() calls - with no #ifdefs nor macro magic to substitute a > Win32 alternative. > > Which suggests there is no way this thing is going to build with MSYS2. There's a bunch of nonsense in pidgin2 that makes this work, serious you don't want to dig into it and we replaced most if not all of it in pidgin 3 already. > The reason I tried building Pidgin 3.0 is that the documentation, such > as it is, claims to build with MSYS2 - and indeed a talkatu standalone > project does build cleanly out of the box even though the Pidgin project > fails to build a talkatu sub-project. Pidgin3 under msys2 currently requires msys2 packages and will not be distribute-able outside of msys2. We're working on a solution for that, but limited resources makes that difficult. Thanks, -- Gary Kramlich ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://lists.pidgin.im/listinfo/support
Re: Problem building Pidgin.
I also tried building Pidgin 2.14.4 with MSYS2. Documentation, such as it is, assumes a Cygwin environment but suggests MSYS (not MSYS2) can be used with "tweaks" to the build scripts. Anyway running configure results in the following error: ... checking for inet_aton... no checking for inet_aton in -lresolv... no configure: error: inet_aton not found Looking at the Pidgin 2.14.4 source code there are multiple bare inet_aton() calls - with no #ifdefs nor macro magic to substitute a Win32 alternative. Which suggests there is no way this thing is going to build with MSYS2. The reason I tried building Pidgin 3.0 is that the documentation, such as it is, claims to build with MSYS2 - and indeed a talkatu standalone project does build cleanly out of the box even though the Pidgin project fails to build a talkatu sub-project. On 5/05/2021 9:53 pm, Konstantin Kharlamov wrote: > Btw, it might help if you say what exactly are you trying to achieve. You see, > if for example you just want to work on some Pidgin plugin, then I don't think > you need to compile libpurple either. Simply installing Pidgin from > installation > binaries for your system should give you libpurple. > > On Wed, 2021-05-05 at 16:49 +0300, Konstantin Kharlamov wrote: >> Disclaimer: just a random user here. >> >> So, before anything else: I suspect you don't want the latest upstream >> Pidgin. >> You see, latest released version is 2.14.4, and if you want to develop a >> libpurple plugin, you better use that one. The 3.0 version was never >> released, >> and devs thinking about releasing it for a long time already. I also think it >> might have introduced some incompatibilities (since it is a new major >> version), >> so, anyway, I don't think you currently want it. >> >> --- >> >> With that said, if you are really interested in latest upstream libpurple, >> then… >> Regarding the error: I looked at `meson.build` file, it tries to find the >> talkatu subproject in the system (by using pkg-config, I suppose like `pkg- >> config --cflags --libs talkatu` or something similar), fails at that, then >> searches "talkatu" directory in `subprojects/` subdirectory, fails again. Idk >> what results in the error regarding "Mercurial" though (does Meson try to >> download a subproject? I never knew it does that), but I suppose if you clone >> `talkatu` into `subprojects/` sub-directory, the error will go away. >> >> But you don't need all that since you only want libpurple. You can safely >> disable `gtkui`. That is, execute something like `meson build -Dgtkui=false` >> (if >> you look at paragraph with talkatu dependency, you'll see it is only checked >> when gtkui is enabled). >> >> On Wed, 2021-05-05 at 21:11 +0800, DAVID MAY wrote: >>> Hello, >>> >>> Sorry if this is the wrong forum, but this is the first time I have >>> worked with Pidgin. >>> >>> I am experiencing an error when I attempt to build Pidgin 3.0 on Windows >>> with MSYS2. Actually, I am only interested in working with libpurple >>> but it does not seem to be possible to build libpurple as a standalone >>> project. >>> >>> I cloned the Pidgin 3.0 Mercurial repository. However meson.build for >>> Pidgin 3.0 fails with an error message which states that Mercurial is >>> not installed. This cannot be correct: I can clone the talkatu >>> Mercurial repository using MSYS2 Mercurial; Meson builds talkatu as a >>> standalone project; the build products talkatu pass all the tests and >>> the demo program works. >>> >>> >>> The full Pidgin 3.0 meson.build output I see is this: >>> >>> $ meson build >>> The Meson build system >>> Version: 0.58.0 >>> Source dir: C:/msys64/home/david/projects/pidgin >>> Build dir: C:/msys64/home/david/projects/pidgin/build >>> Build type: native build >>> Project name: pidgin >>> Project version: 3.0.0-devel >>> C compiler for the host machine: cc (gcc 10.2.0 "cc (Rev11, Built by >>> MSYS2 project) 10.2.0") >>> C linker for the host machine: cc ld.bfd 2.36.1 >>> Host machine cpu family: x86_64 >>> Host machine cpu: x86_64 >>> Program gettext found: YES (C:\msys64\mingw64\bin/gettext.EXE) >>> Program C:/msys64/mingw64/bin/meson found: YES >>> (C:/msys64/mingw64/bin/meson.exe) >>> Program mkmesonconf.py found: YES (C:/msys64/mingw64/bin/python.exe >>> C:/msys64/home/david/projects/pidgin/mkmesonconf.py) >>> Program xgettext found: YES (C:\msys64\mingw64\bin/xgettext.EXE) >>> Library ws2_32 found: YES >>> Library dnsapi found: YES >>> Has header "sys/wait.h" : NO >>> Has header "unistd.h" : YES >>> Has header "fcntl.h" : YES >>> Has header "stdint.h" : YES >>> Checking for size of "time_t" : 8 >>> Header has symbol "socklen_t" : YES >>> Checking whether type "struct sockaddr" has member "sa_len" : NO >>> Library m found: YES >>> Found pkg-config: C:\msys64\mingw64\bin/pkg-config.EXE (0.29.2) >>> Run-time dependency glib-2.0 found: YES 2.68.1 >>> Run-time dependency gio-2.0 found: YES 2.68.1 >>> Run-time dependency gobject-2.0 found: YES 2.68.1 >>>
Re: Problem building Pidgin.
Btw, it might help if you say what exactly are you trying to achieve. You see, if for example you just want to work on some Pidgin plugin, then I don't think you need to compile libpurple either. Simply installing Pidgin from installation binaries for your system should give you libpurple. On Wed, 2021-05-05 at 16:49 +0300, Konstantin Kharlamov wrote: > Disclaimer: just a random user here. > > So, before anything else: I suspect you don't want the latest upstream Pidgin. > You see, latest released version is 2.14.4, and if you want to develop a > libpurple plugin, you better use that one. The 3.0 version was never released, > and devs thinking about releasing it for a long time already. I also think it > might have introduced some incompatibilities (since it is a new major > version), > so, anyway, I don't think you currently want it. > > --- > > With that said, if you are really interested in latest upstream libpurple, > then… > Regarding the error: I looked at `meson.build` file, it tries to find the > talkatu subproject in the system (by using pkg-config, I suppose like `pkg- > config --cflags --libs talkatu` or something similar), fails at that, then > searches "talkatu" directory in `subprojects/` subdirectory, fails again. Idk > what results in the error regarding "Mercurial" though (does Meson try to > download a subproject? I never knew it does that), but I suppose if you clone > `talkatu` into `subprojects/` sub-directory, the error will go away. > > But you don't need all that since you only want libpurple. You can safely > disable `gtkui`. That is, execute something like `meson build -Dgtkui=false` > (if > you look at paragraph with talkatu dependency, you'll see it is only checked > when gtkui is enabled). > > On Wed, 2021-05-05 at 21:11 +0800, DAVID MAY wrote: > > Hello, > > > > Sorry if this is the wrong forum, but this is the first time I have > > worked with Pidgin. > > > > I am experiencing an error when I attempt to build Pidgin 3.0 on Windows > > with MSYS2. Actually, I am only interested in working with libpurple > > but it does not seem to be possible to build libpurple as a standalone > > project. > > > > I cloned the Pidgin 3.0 Mercurial repository. However meson.build for > > Pidgin 3.0 fails with an error message which states that Mercurial is > > not installed. This cannot be correct: I can clone the talkatu > > Mercurial repository using MSYS2 Mercurial; Meson builds talkatu as a > > standalone project; the build products talkatu pass all the tests and > > the demo program works. > > > > > > The full Pidgin 3.0 meson.build output I see is this: > > > > $ meson build > > The Meson build system > > Version: 0.58.0 > > Source dir: C:/msys64/home/david/projects/pidgin > > Build dir: C:/msys64/home/david/projects/pidgin/build > > Build type: native build > > Project name: pidgin > > Project version: 3.0.0-devel > > C compiler for the host machine: cc (gcc 10.2.0 "cc (Rev11, Built by > > MSYS2 project) 10.2.0") > > C linker for the host machine: cc ld.bfd 2.36.1 > > Host machine cpu family: x86_64 > > Host machine cpu: x86_64 > > Program gettext found: YES (C:\msys64\mingw64\bin/gettext.EXE) > > Program C:/msys64/mingw64/bin/meson found: YES > > (C:/msys64/mingw64/bin/meson.exe) > > Program mkmesonconf.py found: YES (C:/msys64/mingw64/bin/python.exe > > C:/msys64/home/david/projects/pidgin/mkmesonconf.py) > > Program xgettext found: YES (C:\msys64\mingw64\bin/xgettext.EXE) > > Library ws2_32 found: YES > > Library dnsapi found: YES > > Has header "sys/wait.h" : NO > > Has header "unistd.h" : YES > > Has header "fcntl.h" : YES > > Has header "stdint.h" : YES > > Checking for size of "time_t" : 8 > > Header has symbol "socklen_t" : YES > > Checking whether type "struct sockaddr" has member "sa_len" : NO > > Library m found: YES > > Found pkg-config: C:\msys64\mingw64\bin/pkg-config.EXE (0.29.2) > > Run-time dependency glib-2.0 found: YES 2.68.1 > > Run-time dependency gio-2.0 found: YES 2.68.1 > > Run-time dependency gobject-2.0 found: YES 2.68.1 > > Run-time dependency gthread-2.0 found: YES 2.68.1 > > Run-time dependency gobject-introspection-1.0 found: YES 1.66.1 > > Run-time dependency nice found: YES 0.1.18 > > Run-time dependency gtk+-3.0 found: YES 3.24.29 > > Found CMake: C:\msys64\mingw64\bin/cmake.EXE (3.20.2) > > Run-time dependency talkatu found: NO (tried pkgconfig and cmake) > > > > meson.build:273:2: ERROR: Mercurial program not found. > > > > > > > ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://lists.pidgin.im/listinfo/support
Re: Problem building Pidgin.
Disclaimer: just a random user here. So, before anything else: I suspect you don't want the latest upstream Pidgin. You see, latest released version is 2.14.4, and if you want to develop a libpurple plugin, you better use that one. The 3.0 version was never released, and devs thinking about releasing it for a long time already. I also think it might have introduced some incompatibilities (since it is a new major version), so, anyway, I don't think you currently want it. --- With that said, if you are really interested in latest upstream libpurple, then… Regarding the error: I looked at `meson.build` file, it tries to find the talkatu subproject in the system (by using pkg-config, I suppose like `pkg- config --cflags --libs talkatu` or something similar), fails at that, then searches "talkatu" directory in `subprojects/` subdirectory, fails again. Idk what results in the error regarding "Mercurial" though (does Meson try to download a subproject? I never knew it does that), but I suppose if you clone `talkatu` into `subprojects/` sub-directory, the error will go away. But you don't need all that since you only want libpurple. You can safely disable `gtkui`. That is, execute something like `meson build -Dgtkui=false` (if you look at paragraph with talkatu dependency, you'll see it is only checked when gtkui is enabled). On Wed, 2021-05-05 at 21:11 +0800, DAVID MAY wrote: > Hello, > > Sorry if this is the wrong forum, but this is the first time I have > worked with Pidgin. > > I am experiencing an error when I attempt to build Pidgin 3.0 on Windows > with MSYS2. Actually, I am only interested in working with libpurple > but it does not seem to be possible to build libpurple as a standalone > project. > > I cloned the Pidgin 3.0 Mercurial repository. However meson.build for > Pidgin 3.0 fails with an error message which states that Mercurial is > not installed. This cannot be correct: I can clone the talkatu > Mercurial repository using MSYS2 Mercurial; Meson builds talkatu as a > standalone project; the build products talkatu pass all the tests and > the demo program works. > > > The full Pidgin 3.0 meson.build output I see is this: > > $ meson build > The Meson build system > Version: 0.58.0 > Source dir: C:/msys64/home/david/projects/pidgin > Build dir: C:/msys64/home/david/projects/pidgin/build > Build type: native build > Project name: pidgin > Project version: 3.0.0-devel > C compiler for the host machine: cc (gcc 10.2.0 "cc (Rev11, Built by > MSYS2 project) 10.2.0") > C linker for the host machine: cc ld.bfd 2.36.1 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program gettext found: YES (C:\msys64\mingw64\bin/gettext.EXE) > Program C:/msys64/mingw64/bin/meson found: YES > (C:/msys64/mingw64/bin/meson.exe) > Program mkmesonconf.py found: YES (C:/msys64/mingw64/bin/python.exe > C:/msys64/home/david/projects/pidgin/mkmesonconf.py) > Program xgettext found: YES (C:\msys64\mingw64\bin/xgettext.EXE) > Library ws2_32 found: YES > Library dnsapi found: YES > Has header "sys/wait.h" : NO > Has header "unistd.h" : YES > Has header "fcntl.h" : YES > Has header "stdint.h" : YES > Checking for size of "time_t" : 8 > Header has symbol "socklen_t" : YES > Checking whether type "struct sockaddr" has member "sa_len" : NO > Library m found: YES > Found pkg-config: C:\msys64\mingw64\bin/pkg-config.EXE (0.29.2) > Run-time dependency glib-2.0 found: YES 2.68.1 > Run-time dependency gio-2.0 found: YES 2.68.1 > Run-time dependency gobject-2.0 found: YES 2.68.1 > Run-time dependency gthread-2.0 found: YES 2.68.1 > Run-time dependency gobject-introspection-1.0 found: YES 1.66.1 > Run-time dependency nice found: YES 0.1.18 > Run-time dependency gtk+-3.0 found: YES 3.24.29 > Found CMake: C:\msys64\mingw64\bin/cmake.EXE (3.20.2) > Run-time dependency talkatu found: NO (tried pkgconfig and cmake) > > meson.build:273:2: ERROR: Mercurial program not found. > > > ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: https://lists.pidgin.im/listinfo/support
