Re: Trying to build on Mint 20 ... [msg...@gmail.com]
Thanks to Pawel for pointing out what I should have seen. You did have the library itself, but not the files which tell configure where to find it. On 2021.10.05 16:47, Mike Witt via balsa-list wrote: It looks like that was it. I must have been missing that library. Now it configures and builds. Thank you so much for all your help! -Mike On 10/05/2021 02:04:35 PM, Pawel Salek wrote: libenchant-2.so.2.2.15 or similar is just the shared library that can be used to execute balsa but insufficient to compile. enchant.pc is typically a part of a 'dev' package containing configuration, header files, and sometimes some configuration. The dev package is called libenchant-2-dev on Ubuntu. On Tue, Oct 5, 2021 at 1:24 AM Mike Witt via balsa-list < balsa-list@gnome.org> wrote: > On 10/04/2021 04:41:44 PM, Jack via balsa-list wrote: > > On 2021.10.04 18:29, Mike Witt via balsa-list wrote: > >>> Those look OK to me. Can you post part of config.log? > >> > >> I'm so sorry. I didn't really know about config.log. I'm really not > >> used to doing this. There are some very obvious errors in there, for > >> example: > > When things go well, config.log becomes irrelevant. It helps when > > things do not go well, as now. Also, "obvious" is a very relative > > term. Once you have much more experience tracking down problems like > > this, you will recognize that those particular errors are really not > > important at all (more below.) > >> > >> gcc: error: unrecognized command line option '-V' > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-qversion'; did you > >> mean '--version'? > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-V' > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-qversion'; did you > >> mean '--version'? > >> gcc: fatal error: no input files > >> > >> Do you want me to post the whole log? > > > It should not be necessary, but don't try to extract single lines. > > Post the contiguous set of the last twenty or so lines before: > > > > ## ## > > ## Cache variables. ## > > ## ## > > Sorry, I thought I did that. Here they are. It seems to be looking for > "enchant.pc" -- as far as I can tell, I don't have that (or I don't > know where to look for it). > > configure:14357: $? = 1 > configure:14371: $PKG_CONFIG --exists --print-errors " enchant != 1.6.1 > " > Package enchant was not found in the pkg-config search path. > Perhaps you should add the directory containing `enchant.pc' > to the PKG_CONFIG_PATH environment variable > No package 'enchant' found > configure:14374: $? = 1 > configure:14388: result: no > No package 'enchant' found > configure:14404: error: Package requirements ( enchant != 1.6.1 ) were > not met: > > No package 'enchant' 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 SPELL_CFLAGS > and SPELL_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > > ## ## > ## Cache variables. ## > ## ## > > ac_cv_build=x86_64-pc-linux-gnu > ac_cv_c_compiler_gnu=yes > ac_cv_env_AUTOCRYPT_CFLAGS_set= > ac_cv_env_AUTOCRYPT_CFLAGS_value= > ac_cv_env_AUTOCRYPT_LIBS_set= > ac_cv_env_AUTOCRYPT_LIBS_value= > ac_cv_env_BALSA_AB_CFLAGS_set= > ac_cv_env_BALSA_AB_CFLAGS_value= > ac_cv_env_BALSA_AB_LIBS_set= > ac_cv_env_BALSA_AB_LIBS_value= > ac_cv_env_BALSA_CFLAGS_set= > ac_cv_env_BALSA_CFLAGS_value= > ac_cv_env_BALSA_LIBS_set= > ac_cv_env_BALSA_LIBS_value= > ac_cv_env_CANBERRA_CFLAGS_set= > ac_cv_env_CANBERRA_CFLAGS_value= > ac_cv_env_CANBERRA_LIBS_set= > ac_cv_env_CANBERRA_LIBS_value= > ac_cv_env_CC_set= > ac_cv_env_CC_value= > ac_cv_env_CFLAGS_set= > ac_cv_env_CFLAGS_value= > ac_cv_env_CPPFLAGS_set= > ac_cv_env_CPPFLAGS_value= > ac_cv_env_CPP_set= > ac_cv_env_CPP_value= > ac_cv_env_GCR_CFLAGS_set= > ac_cv_env_GCR_CFLAGS_value= > ac_cv_env_GCR_LIBS_set= > ac_cv_env_GCR_LIBS_value= > ac_cv_env_GPGME_CFLAGS_set= > ac_cv_env_GPGME_CFLAGS_value= > ac_cv_env_GPGME_LIBS_set= > ___ > balsa-list mailing list > balsa-list@gnome.org > https://mail.gnome.org/mailman/listinfo/balsa-list > ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
It looks like that was it. I must have been missing that library. Now it configures and builds. Thank you so much for all your help! -Mike On 10/05/2021 02:04:35 PM, Pawel Salek wrote: libenchant-2.so.2.2.15 or similar is just the shared library that can be used to execute balsa but insufficient to compile. enchant.pc is typically a part of a 'dev' package containing configuration, header files, and sometimes some configuration. The dev package is called libenchant-2-dev on Ubuntu. On Tue, Oct 5, 2021 at 1:24 AM Mike Witt via balsa-list < balsa-list@gnome.org> wrote: > On 10/04/2021 04:41:44 PM, Jack via balsa-list wrote: > > On 2021.10.04 18:29, Mike Witt via balsa-list wrote: > >>> Those look OK to me. Can you post part of config.log? > >> > >> I'm so sorry. I didn't really know about config.log. I'm really not > >> used to doing this. There are some very obvious errors in there, for > >> example: > > When things go well, config.log becomes irrelevant. It helps when > > things do not go well, as now. Also, "obvious" is a very relative > > term. Once you have much more experience tracking down problems like > > this, you will recognize that those particular errors are really not > > important at all (more below.) > >> > >> gcc: error: unrecognized command line option '-V' > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-qversion'; did you > >> mean '--version'? > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-V' > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-qversion'; did you > >> mean '--version'? > >> gcc: fatal error: no input files > >> > >> Do you want me to post the whole log? > > > It should not be necessary, but don't try to extract single lines. > > Post the contiguous set of the last twenty or so lines before: > > > > ## ## > > ## Cache variables. ## > > ## ## > > Sorry, I thought I did that. Here they are. It seems to be looking for > "enchant.pc" -- as far as I can tell, I don't have that (or I don't > know where to look for it). > > configure:14357: $? = 1 > configure:14371: $PKG_CONFIG --exists --print-errors " enchant != 1.6.1 > " > Package enchant was not found in the pkg-config search path. > Perhaps you should add the directory containing `enchant.pc' > to the PKG_CONFIG_PATH environment variable > No package 'enchant' found > configure:14374: $? = 1 > configure:14388: result: no > No package 'enchant' found > configure:14404: error: Package requirements ( enchant != 1.6.1 ) were > not met: > > No package 'enchant' 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 SPELL_CFLAGS > and SPELL_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > > ## ## > ## Cache variables. ## > ## ## > > ac_cv_build=x86_64-pc-linux-gnu > ac_cv_c_compiler_gnu=yes > ac_cv_env_AUTOCRYPT_CFLAGS_set= > ac_cv_env_AUTOCRYPT_CFLAGS_value= > ac_cv_env_AUTOCRYPT_LIBS_set= > ac_cv_env_AUTOCRYPT_LIBS_value= > ac_cv_env_BALSA_AB_CFLAGS_set= > ac_cv_env_BALSA_AB_CFLAGS_value= > ac_cv_env_BALSA_AB_LIBS_set= > ac_cv_env_BALSA_AB_LIBS_value= > ac_cv_env_BALSA_CFLAGS_set= > ac_cv_env_BALSA_CFLAGS_value= > ac_cv_env_BALSA_LIBS_set= > ac_cv_env_BALSA_LIBS_value= > ac_cv_env_CANBERRA_CFLAGS_set= > ac_cv_env_CANBERRA_CFLAGS_value= > ac_cv_env_CANBERRA_LIBS_set= > ac_cv_env_CANBERRA_LIBS_value= > ac_cv_env_CC_set= > ac_cv_env_CC_value= > ac_cv_env_CFLAGS_set= > ac_cv_env_CFLAGS_value= > ac_cv_env_CPPFLAGS_set= > ac_cv_env_CPPFLAGS_value= > ac_cv_env_CPP_set= > ac_cv_env_CPP_value= > ac_cv_env_GCR_CFLAGS_set= > ac_cv_env_GCR_CFLAGS_value= > ac_cv_env_GCR_LIBS_set= > ac_cv_env_GCR_LIBS_value= > ac_cv_env_GPGME_CFLAGS_set= > ac_cv_env_GPGME_CFLAGS_value= > ac_cv_env_GPGME_LIBS_set= > ___ > balsa-list mailing list > balsa-list@gnome.org > https://mail.gnome.org/mailman/listinfo/balsa-list > ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
libenchant-2.so.2.2.15 or similar is just the shared library that can be used to execute balsa but insufficient to compile. enchant.pc is typically a part of a 'dev' package containing configuration, header files, and sometimes some configuration. The dev package is called libenchant-2-dev on Ubuntu. On Tue, Oct 5, 2021 at 1:24 AM Mike Witt via balsa-list < balsa-list@gnome.org> wrote: > On 10/04/2021 04:41:44 PM, Jack via balsa-list wrote: > > On 2021.10.04 18:29, Mike Witt via balsa-list wrote: > >>> Those look OK to me. Can you post part of config.log? > >> > >> I'm so sorry. I didn't really know about config.log. I'm really not > >> used to doing this. There are some very obvious errors in there, for > >> example: > > When things go well, config.log becomes irrelevant. It helps when > > things do not go well, as now. Also, "obvious" is a very relative > > term. Once you have much more experience tracking down problems like > > this, you will recognize that those particular errors are really not > > important at all (more below.) > >> > >> gcc: error: unrecognized command line option '-V' > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-qversion'; did you > >> mean '--version'? > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-V' > >> gcc: fatal error: no input files > >> gcc: error: unrecognized command line option '-qversion'; did you > >> mean '--version'? > >> gcc: fatal error: no input files > >> > >> Do you want me to post the whole log? > > > It should not be necessary, but don't try to extract single lines. > > Post the contiguous set of the last twenty or so lines before: > > > > ## ## > > ## Cache variables. ## > > ## ## > > Sorry, I thought I did that. Here they are. It seems to be looking for > "enchant.pc" -- as far as I can tell, I don't have that (or I don't > know where to look for it). > > configure:14357: $? = 1 > configure:14371: $PKG_CONFIG --exists --print-errors " enchant != 1.6.1 > " > Package enchant was not found in the pkg-config search path. > Perhaps you should add the directory containing `enchant.pc' > to the PKG_CONFIG_PATH environment variable > No package 'enchant' found > configure:14374: $? = 1 > configure:14388: result: no > No package 'enchant' found > configure:14404: error: Package requirements ( enchant != 1.6.1 ) were > not met: > > No package 'enchant' 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 SPELL_CFLAGS > and SPELL_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > > ## ## > ## Cache variables. ## > ## ## > > ac_cv_build=x86_64-pc-linux-gnu > ac_cv_c_compiler_gnu=yes > ac_cv_env_AUTOCRYPT_CFLAGS_set= > ac_cv_env_AUTOCRYPT_CFLAGS_value= > ac_cv_env_AUTOCRYPT_LIBS_set= > ac_cv_env_AUTOCRYPT_LIBS_value= > ac_cv_env_BALSA_AB_CFLAGS_set= > ac_cv_env_BALSA_AB_CFLAGS_value= > ac_cv_env_BALSA_AB_LIBS_set= > ac_cv_env_BALSA_AB_LIBS_value= > ac_cv_env_BALSA_CFLAGS_set= > ac_cv_env_BALSA_CFLAGS_value= > ac_cv_env_BALSA_LIBS_set= > ac_cv_env_BALSA_LIBS_value= > ac_cv_env_CANBERRA_CFLAGS_set= > ac_cv_env_CANBERRA_CFLAGS_value= > ac_cv_env_CANBERRA_LIBS_set= > ac_cv_env_CANBERRA_LIBS_value= > ac_cv_env_CC_set= > ac_cv_env_CC_value= > ac_cv_env_CFLAGS_set= > ac_cv_env_CFLAGS_value= > ac_cv_env_CPPFLAGS_set= > ac_cv_env_CPPFLAGS_value= > ac_cv_env_CPP_set= > ac_cv_env_CPP_value= > ac_cv_env_GCR_CFLAGS_set= > ac_cv_env_GCR_CFLAGS_value= > ac_cv_env_GCR_LIBS_set= > ac_cv_env_GCR_LIBS_value= > ac_cv_env_GPGME_CFLAGS_set= > ac_cv_env_GPGME_CFLAGS_value= > ac_cv_env_GPGME_LIBS_set= > ___ > balsa-list mailing list > balsa-list@gnome.org > https://mail.gnome.org/mailman/listinfo/balsa-list > ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
On 10/04/2021 04:41:44 PM, Jack via balsa-list wrote: On 2021.10.04 18:29, Mike Witt via balsa-list wrote: Those look OK to me. Can you post part of config.log? I'm so sorry. I didn't really know about config.log. I'm really not used to doing this. There are some very obvious errors in there, for example: When things go well, config.log becomes irrelevant. It helps when things do not go well, as now. Also, "obvious" is a very relative term. Once you have much more experience tracking down problems like this, you will recognize that those particular errors are really not important at all (more below.) gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files Do you want me to post the whole log? It should not be necessary, but don't try to extract single lines. Post the contiguous set of the last twenty or so lines before: ## ## ## Cache variables. ## ## ## Sorry, I thought I did that. Here they are. It seems to be looking for "enchant.pc" -- as far as I can tell, I don't have that (or I don't know where to look for it). configure:14357: $? = 1 configure:14371: $PKG_CONFIG --exists --print-errors " enchant != 1.6.1 " Package enchant was not found in the pkg-config search path. Perhaps you should add the directory containing `enchant.pc' to the PKG_CONFIG_PATH environment variable No package 'enchant' found configure:14374: $? = 1 configure:14388: result: no No package 'enchant' found configure:14404: error: Package requirements ( enchant != 1.6.1 ) were not met: No package 'enchant' 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 SPELL_CFLAGS and SPELL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. ## ## ## Cache variables. ## ## ## ac_cv_build=x86_64-pc-linux-gnu ac_cv_c_compiler_gnu=yes ac_cv_env_AUTOCRYPT_CFLAGS_set= ac_cv_env_AUTOCRYPT_CFLAGS_value= ac_cv_env_AUTOCRYPT_LIBS_set= ac_cv_env_AUTOCRYPT_LIBS_value= ac_cv_env_BALSA_AB_CFLAGS_set= ac_cv_env_BALSA_AB_CFLAGS_value= ac_cv_env_BALSA_AB_LIBS_set= ac_cv_env_BALSA_AB_LIBS_value= ac_cv_env_BALSA_CFLAGS_set= ac_cv_env_BALSA_CFLAGS_value= ac_cv_env_BALSA_LIBS_set= ac_cv_env_BALSA_LIBS_value= ac_cv_env_CANBERRA_CFLAGS_set= ac_cv_env_CANBERRA_CFLAGS_value= ac_cv_env_CANBERRA_LIBS_set= ac_cv_env_CANBERRA_LIBS_value= ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set= ac_cv_env_CFLAGS_value= ac_cv_env_CPPFLAGS_set= ac_cv_env_CPPFLAGS_value= ac_cv_env_CPP_set= ac_cv_env_CPP_value= ac_cv_env_GCR_CFLAGS_set= ac_cv_env_GCR_CFLAGS_value= ac_cv_env_GCR_LIBS_set= ac_cv_env_GCR_LIBS_value= ac_cv_env_GPGME_CFLAGS_set= ac_cv_env_GPGME_CFLAGS_value= ac_cv_env_GPGME_LIBS_set= ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
On 2021.10.04 18:29, Mike Witt via balsa-list wrote: Those look OK to me. Can you post part of config.log? I'm so sorry. I didn't really know about config.log. I'm really not used to doing this. There are some very obvious errors in there, for example: When things go well, config.log becomes irrelevant. It helps when things do not go well, as now. Also, "obvious" is a very relative term. Once you have much more experience tracking down problems like this, you will recognize that those particular errors are really not important at all (more below.) gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files Do you want me to post the whole log? It should not be necessary, but don't try to extract single lines. Post the contiguous set of the last twenty or so lines before: ## ## ## Cache variables. ## ## ## Don't do any additional editing. Those errors about -V are really not important, They are errors from gcc which tell configure about which gcc features are or are not present. While running, configure creates lots of small test programs which it tries to compile, and it uses the results (very often compile failures) to know what features are available, which it uses to create the Makefiles which are then used to compile the program you are interested in. (Remember, configure can handle a whole bunch of different compilers than gcc and different OSs than Linux.) I'm looking for the lines from config.log instead of the console because they generally have additional information. ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
Those look OK to me. Can you post part of config.log? I'm so sorry. I didn't really know about config.log. I'm really not used to doing this. There are some very obvious errors in there, for example: gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files Do you want me to post the whole log? Look for the lines ## ## ## Cache variables. ## ## ## and post the ten or twenty lines above those. That should include the error message and will give an idea exactly where in configure it is failing. Make sure you include some lines above any which have "result: no" in them. Here are those, for whatever it's worth: configure:14050: checking whether to use an external spell checker configure:14250: result: configure enchant configure:14347: checking for enchant != 1.6.1 configure:14354: $PKG_CONFIG --exists --print-errors " enchant != 1.6.1 " Package enchant was not found in the pkg-config search path. Perhaps you should add the directory containing `enchant.pc' to the PKG_CONFIG_PATH environment variable No package 'enchant' found configure:14357: $? = 1 configure:14371: $PKG_CONFIG --exists --print-errors " enchant != 1.6.1 " Package enchant was not found in the pkg-config search path. Perhaps you should add the directory containing `enchant.pc' to the PKG_CONFIG_PATH environment variable No package 'enchant' found configure:14374: $? = 1 configure:14388: result: no No package 'enchant' found configure:14404: error: Package requirements ( enchant != 1.6.1 ) were not met: No package 'enchant' 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 SPELL_CFLAGS and SPELL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. ## ## ## Cache variables. ## ## ## ac_cv_build=x86_64-pc-linux-gnu ac_cv_c_compiler_gnu=yes ac_cv_env_AUTOCRYPT_CFLAGS_set= ac_cv_env_AUTOCRYPT_CFLAGS_value= ac_cv_env_AUTOCRYPT_LIBS_set= ac_cv_env_AUTOCRYPT_LIBS_value= ac_cv_env_BALSA_AB_CFLAGS_set= ac_cv_env_BALSA_AB_CFLAGS_value= ac_cv_env_BALSA_AB_LIBS_set= ac_cv_env_BALSA_AB_LIBS_value= ac_cv_env_BALSA_CFLAGS_set= ac_cv_env_BALSA_CFLAGS_value= ac_cv_env_BALSA_LIBS_set= ac_cv_env_BALSA_LIBS_value= ac_cv_env_CANBERRA_CFLAGS_set= ac_cv_env_CANBERRA_CFLAGS_value= ac_cv_env_CANBERRA_LIBS_set= ac_cv_env_CANBERRA_LIBS_value= ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set= ac_cv_env_CFLAGS_value= ac_cv_env_CPPFLAGS_set= ac_cv_env_CPPFLAGS_value= ac_cv_env_CPP_set= ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
On 2021.10.04 16:56, Mike Witt via balsa-list wrote: On 10/04/2021 02:40:23 PM, Jack via balsa-list wrote: On 2021.10.04 16:05, Mike Witt via balsa-list wrote: On 10/04/2021 01:35:26 PM, Jack via balsa-list wrote: The full configure command line you used, with all parameters and switches. (I don't expect there to be a problem there, but you never know.) I'm just saying ./configure That should be fine. I don't know if it will help, but try creating a new directory "build" there, cd into it, then do ../configure. The other thing you might try is to use meson. It works pretty much the same - cd into build, then "meson ..". I'm still trying to figure out why configure is failing for me. I made a new subdirectory and did ../configure -- no difference. I don't know anything about "meson" but I installed it, and in that same subdirectory I just typed: meson It still complained about "enchant" not being found. But maybe meson needs some parameters or something. Other than pointing to the root of the source tree, it shouldn't need anything else for default settings. I've got a /usr/bin/enchant, /usr/lib/x86_64-linux-gnu/enchant, and /usr/share/enchant -- if that helps. There should be a libenchant-2.so.2.2.8 and a libenchant.so.1.6.0 (or something close, and some variants.) It is the .so. file that is being tested for. If they exist, we need to dig deeper. If you can't find them, check the list of files installed with any of the enchant packages you have installed, although I would be surprised if Mint omitted the .so files from the package. I've got: /usr/lib/x86_64-linux-gnu/libenchant-2.so.2.2.8 /usr/lib/x86_64-linux-gnu/libenchant.so.1.6.0 k Is there some way to check if it's looking in those places? Those look OK to me. Can you post part of config.log? Look for the lines ## ## ## Cache variables. ## ## ## and post the ten or twenty lines above those. That should include the error message and will give an idea exactly where in configure it is failing. Make sure you include some lines above any which have "result: no" in them. ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
On 10/04/2021 02:40:23 PM, Jack via balsa-list wrote: On 2021.10.04 16:05, Mike Witt via balsa-list wrote: On 10/04/2021 01:35:26 PM, Jack via balsa-list wrote: The full configure command line you used, with all parameters and switches. (I don't expect there to be a problem there, but you never know.) I'm just saying ./configure That should be fine. I don't know if it will help, but try creating a new directory "build" there, cd into it, then do ../configure. The other thing you might try is to use meson. It works pretty much the same - cd into build, then "meson ..". I'm still trying to figure out why configure is failing for me. I made a new subdirectory and did ../configure -- no difference. I don't know anything about "meson" but I installed it, and in that same subdirectory I just typed: meson It still complained about "enchant" not being found. But maybe meson needs some parameters or something. Other than pointing to the root of the source tree, it shouldn't need anything else for default settings. I've got a /usr/bin/enchant, /usr/lib/x86_64-linux-gnu/enchant, and /usr/share/enchant -- if that helps. There should be a libenchant-2.so.2.2.8 and a libenchant.so.1.6.0 (or something close, and some variants.) It is the .so. file that is being tested for. If they exist, we need to dig deeper. If you can't find them, check the list of files installed with any of the enchant packages you have installed, although I would be surprised if Mint omitted the .so files from the package. I've got: /usr/lib/x86_64-linux-gnu/libenchant-2.so.2.2.8 /usr/lib/x86_64-linux-gnu/libenchant.so.1.6.0 Is there some way to check if it's looking in those places? ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
On 2021.10.04 16:05, Mike Witt via balsa-list wrote: On 10/04/2021 01:35:26 PM, Jack via balsa-list wrote: The full configure command line you used, with all parameters and switches. (I don't expect there to be a problem there, but you never know.) I'm just saying ./configure That should be fine. I don't know if it will help, but try creating a new directory "build" there, cd into it, then do ../configure. The other thing you might try is to use meson. It works pretty much the same - cd into build, then "meson ..". I'm still trying to figure out why configure is failing for me. I made a new subdirectory and did ../configure -- no difference. I don't know anything about "meson" but I installed it, and in that same subdirectory I just typed: meson It still complained about "enchant" not being found. But maybe meson needs some parameters or something. Other than pointing to the root of the source tree, it shouldn't need anything else for default settings. I've got a /usr/bin/enchant, /usr/lib/x86_64-linux-gnu/enchant, and /usr/share/enchant -- if that helps. There should be a libenchant-2.so.2.2.8 and a libenchant.so.1.6.0 (or something close, and some variants.) It is the .so. file that is being tested for. If they exist, we need to dig deeper. If you can't find them, check the list of files installed with any of the enchant packages you have installed, although I would be surprised if Mint omitted the .so files from the package. ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ... [msg...@gmail.com]
On 10/04/2021 01:35:26 PM, Jack via balsa-list wrote: The full configure command line you used, with all parameters and switches. (I don't expect there to be a problem there, but you never know.) I'm just saying ./configure I don't know if it will help, but try creating a new directory "build" there, cd into it, then do ../configure. The other thing you might try is to use meson. It works pretty much the same - cd into build, then "meson ..". I'm still trying to figure out why configure is failing for me. I made a new subdirectory and did ../configure -- no difference. I don't know anything about "meson" but I installed it, and in that same subdirectory I just typed: meson It still complained about "enchant" not being found. But maybe meson needs some parameters or something. I've got a /usr/bin/enchant, /usr/lib/x86_64-linux-gnu/enchant, and /usr/share/enchant -- if that helps. ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Fwd: Re: Trying to build on Mint 20 ... [msg...@gmail.com]
On 2021.10.04 15:21, Mike Witt via balsa-list wrote: For some reason, when I reply it doesn't seem to go to the list. What mail software are you using? There should be an explicit "reply to list" or "reply to group" command/button/menu item. In a pinch, "reply all" should also work, but check the headers before hitting "send." ==quoted message from Mike Witt , subject “Re: Trying to build on Mint 20 ...”== Sorry about that. I downloaded balsa-2.6.3.tar.xz and untarred it. Then I'm running the configure command. I've run it many times and up until I hit enchant I was able to find and install everything. Is there any other into I can give you? The full configure command line you used, with all parameters and switches. (I don't expect there to be a problem there, but you never know.) I normally just use the version of Balsa that's availalbe by default, but unfortunately the one that comes with this version of Mint is 2.6.0-2, which apparently doesn't work well. So I don't really have any experience building it. Additional question - where is your build directory? I untarred into balsa-2.6.3 and I'm trying to build right in there. I don't know if it will help, but try creating a new directory "build" there, cd into it, then do ../configure. The other thing you might try is to use meson. It works pretty much the same - cd into build, then "meson ..". I'm still trying to figure out why configure is failing for me. On 10/04/2021 12:00:53 PM, Jack via balsa-list wrote: First - what is the exact command you used? (configure or meson full command line.) Also, are you building from git or a tarball (if so, which version?) On 10/4/21 13:19, Mike Witt via balsa-list wrote: I'm trying to build Balsa on Mint 20. I'm currently stuck on configure telling me: checking whether to use an external spell checker... configure enchant checking for enchant != 1.6.1 ... no configure: error: Package requirements ( enchant != 1.6.1 ) were not met: No package 'enchant' found AFAICT I've got and enchant that is not 1.6.1: enchant is already the newest version (1.6.0-11.3build1). enchant-2 is already the newest version (2.2.8-1ubuntu0.20.04.1). I'm on Gentoo and actually have enchant 2.3.0 and see that 2.3.1 is available, but 2.2.8 should certainly work. I have no problem configuring with meson, but I can't test now with configure, as I'm getting a different strange error I need to track down. Additional question - where is your build directory? I create a build dir below the root of the repository. (I'm also building from git, not a tarball, but I don't think that should matter, although I hope those aren't famous last words.) ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Fwd: Re: Trying to build on Mint 20 ... [msg...@gmail.com]
For some reason, when I reply it doesn't seem to go to the list.--- Begin Message --- Sorry about that. I downloaded balsa-2.6.3.tar.xz and untarred it. Then I'm running the configure command. I've run it many times and up until I hit enchant I was able to find and install everything. Is there any other into I can give you? I normally just use the version of Balsa that's availalbe by default, but unfortunately the one that comes with this version of Mint is 2.6.0-2, which apparently doesn't work well. So I don't really have any experience building it. Additional question - where is your build directory? I untarred into balsa-2.6.3 and I'm trying to build right in there. On 10/04/2021 12:00:53 PM, Jack via balsa-list wrote: First - what is the exact command you used? (configure or meson full command line.) Also, are you building from git or a tarball (if so, which version?) On 10/4/21 13:19, Mike Witt via balsa-list wrote: I'm trying to build Balsa on Mint 20. I'm currently stuck on configure telling me: checking whether to use an external spell checker... configure enchant checking for enchant != 1.6.1 ... no configure: error: Package requirements ( enchant != 1.6.1 ) were not met: No package 'enchant' found AFAICT I've got and enchant that is not 1.6.1: enchant is already the newest version (1.6.0-11.3build1). enchant-2 is already the newest version (2.2.8-1ubuntu0.20.04.1). I'm on Gentoo and actually have enchant 2.3.0 and see that 2.3.1 is available, but 2.2.8 should certainly work. I have no problem configuring with meson, but I can't test now with configure, as I'm getting a different strange error I need to track down. Additional question - where is your build directory? I create a build dir below the root of the repository. (I'm also building from git, not a tarball, but I don't think that should matter, although I hope those aren't famous last words.) ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list --- End Message --- ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
Re: Trying to build on Mint 20 ...
First - what is the exact command you used? (configure or meson full command line.) Also, are you building from git or a tarball (if so, which version?) On 10/4/21 13:19, Mike Witt via balsa-list wrote: I'm trying to build Balsa on Mint 20. I'm currently stuck on configure telling me: checking whether to use an external spell checker... configure enchant checking for enchant != 1.6.1 ... no configure: error: Package requirements ( enchant != 1.6.1 ) were not met: No package 'enchant' found AFAICT I've got and enchant that is not 1.6.1: enchant is already the newest version (1.6.0-11.3build1). enchant-2 is already the newest version (2.2.8-1ubuntu0.20.04.1). I'm on Gentoo and actually have enchant 2.3.0 and see that 2.3.1 is available, but 2.2.8 should certainly work. I have no problem configuring with meson, but I can't test now with configure, as I'm getting a different strange error I need to track down. Additional question - where is your build directory? I create a build dir below the root of the repository. (I'm also building from git, not a tarball, but I don't think that should matter, although I hope those aren't famous last words.) ___ balsa-list mailing list balsa-list@gnome.org https://mail.gnome.org/mailman/listinfo/balsa-list
