On Sun, 31 May 2020 09:02:51 -0700, Geoffrey Leach wrote:
> On Sun, 31 May 2020 16:29:54 +0200
> Andras Simon wrote:
>
> > 2020-05-31 16:08 UTC+02:00, Geoffrey Leach:
> > > I have a build that references '-lz'. This fails, because gcc
> > > expects to find libz.so in the library search path. Th
On Sun, 31 May 2020 16:29:54 +0200
Andras Simon wrote:
> 2020-05-31 16:08 UTC+02:00, Geoffrey Leach :
> > I have a build that references '-lz'. This fails, because gcc
> > expects to find libz.so in the library search path. The package
> > that installs zlib, zlib-1.2.11-21.fc32.x86_64 does not c
On Sun, 31 May 2020 16:29:54 +0200
Andras Simon wrote:
> I think that you need to install zlib-devel.
Yep, all the symlinks and such you need to build things
are always in the corresponding xxx-devel packages that
go with the original xxx package (almost always, anyway).
_
2020-05-31 16:08 UTC+02:00, Geoffrey Leach :
> I have a build that references '-lz'. This fails, because gcc expects
> to find libz.so in the library search path. The package that installs
> zlib, zlib-1.2.11-21.fc32.x86_64 does not create a symlink from
> libz.so.1.2.11
I think that you need to i
I have a build that references '-lz'. This fails, because gcc expects
to find libz.so in the library search path. The package that installs
zlib, zlib-1.2.11-21.fc32.x86_64 does not create a symlink from
libz.so.1.2.11
So, is this a bug in the package, or am I missing something? This
package is no