I need to install a software from source.
During the configure command, I got an error :
checking for some_file... no
checking for SOMELIB - version >= 1.2.0... no
configure: error: a_software needs SOMELIB
But opensuse have installed SOMELIB6 which version is 1.6.0 which is >= 1.2.0
Generally speaking SOMELIB6 provides somelib.so.6 (somelib6.so.0) or which is not what the software is searching for.
Sometimes it is sufficient to make a link (somelib.so.6 → somelib.so or somelib6.so.0 → somelib.so.0 )
How to solve this kind of problem ?
I am looking for libgcrypt :
checking for libgcrypt-config... no
checking for LIBGCRYPT - version >= 1.2.0... no
configure: error: gnoMint needs libgcrypt
For the second, use zypper (this is from Tumbleweed);
zypper se --file-list libgcrypt-config
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+-----------------------+------------------------+--------
| libgcrypt-devel | The GNU Crypto Library | package
| libgcrypt-devel-32bit | The GNU Crypto Library | package
Note: For an extended search including not yet activated remote resources please use 'zypper
search-packages'.
First, realize that sometimes a library <package name> may have been renamed to something similar although not exact. Consider whether a slight name change in any way makes sense. Remember, a package name is just a name and may or may not be the same as its file contents, or the naming convention may be different from one system to the next (causing project problems when they build to different distros).
Do an Internet search for the desired RPM package or file which might turn up in places like RPM PBone, RPMfind, etc
Look up the project supporting the specific library to see whether it can be downloaded typically as a TAR file or compiled easily.
Always consider the source for whatever you install, whether you can trust its integrity and weight the risk you could damage your machine whether intentionally or not.
PS. And Malcolm points out that if you’re <building> something and not just installing a pre-built, then you may need the source headers for that package which will the package name with “-devel” appended when available.
1, 2, 3, 4, 5 does not help really because one don’t know the lib name or the file name “.so.” the installer is searching.
The generic name is libgcrypt
Opensuse use libgcrypt20 package ( which provide libgcrypt.so.20 ) (version 1.6.1) for opensuse leap 42.3
For Opensuse 10.1 the package is named libgcrypt and provide libgcrypt.so.20 version 1.2.4
On Fri 08 Jun 2018 03:16:03 PM CDT, malcolmlewis wrote:
jcdole;2868821 Wrote:
> I am trying to compile version 1.3.0 from sourceforge.
> I have put a bug request on sourceforge
>
> I Have not found the package on opensuse certainly due to a bad search
> on google ( just to “download.opensuse.org” ).
>
> I will try the package from :
> https://build.opensuse.org/package/show/home:ecsos/gnoMint
>
> Thank you for all your tips.
Hi
If still having issues, post back and will see if get some time today
for a rpm build for you.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On Fri 08 Jun 2018 07:16:03 PM CDT, malcolmlewis wrote:
malcolmlewis;2868841 Wrote:
> Hi
> So, running the autogen.sh script will fix things up… Have a
> test build on OBS;
> http://tinyurl.com/y9ezrlus
>
> Still need to fix the compile option flags…
>
Hi
And sorted, need to look at branching gnoMint and pushing the fix to
allow cflags to be set and remove the -Werror (as per their
ChangeLog)…
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I gave up its use because the level of aid was not sufficient in relation to my own knowledge of the domain.
For the same reason, after a try, I gave up the use of yast CA Management.
I have found a tutorial and writes a script to generate certificates from root ca cert, intermediate cert, up to server ca.
This is sufficient to make test locally.