On 04/03, Laurent Bercot wrote:
> If rpm doesn't have an alternatives system to get the useless binaries out
> of the way, and if /usr/sbin is unusable, then there's nothing left but
> "add another directory to the global PATH", which is super invasive.
RHEL and Fedora have an alternatives
On 12/04, Jens Rehsack wrote:
> > Am 04.12.2019 um 06:30 schrieb J. Lewis Muir :
> > Your rationale for using /etc/ld.so.conf makes sense to me.
> >
> > However, at
> >
> > http://xahlee.info/UnixResource_dir/_/ldpath.html
> >
> > David Barr
Hello!
I compiled s6 2.9.0.1 and the skalibs 2.9.1.0 and execline 2.5.3.0
dependencies with shared libraries enabled and static libraries disabled
on RHEL 7, and when I run s6-svscan, it can't find libs6.so.2.9:
# /opt/local/bin/s6-svscan -S /run/service
/opt/local/bin/s6-svscan: error
On 12/03, Laurent Bercot wrote:
> > Since I'm not using static libraries, I would not expect to need the
> > "--with-lib" configure option.
>
> The --disable-static flag only tells the build system not to
> build the static execline library. By default, executables are still
> built against the
Hello!
On x86_64 RHEL 7.7 with GCC 4.8.5, configuring and compiling execline
2.5.3.0 against skalibs 2.9.1.0 (which has been compiled with the
"--disable-static" configure option) with
$ ./configure --prefix=/opt/local/encap/execline-2.5.3.0 --enable-shared
--disable-static
On 12/02, Laurent Bercot wrote:
> > src/libunixonacid/textclient_server_init_fromsocket.c:56:3: warning:
> > dereferencing type-punned pointer will break strict-aliasing rules
> > [-Wstrict-aliasing]
> >*(int *)CMSG_DATA(c) = fd[1] ;
> >^
>
> Yeah, some compilers actually print that
Hello!
On x86_64 RHEL 7.7 with GCC 4.8.5, configuring and compiling skalibs
2.9.1.0 with
$ ./configure --disable-static
$ make
results in a clean compile except for the following two warnings:
exec gcc -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700 -Isrc/include -fPIC
