These patches are correct to the best of my knowlege / ability:
-
https://github.com/bukzor/s6-packaging/blob/dockerize/skalibs/debian/patches/01_link_against_librt_if_necessary.patch
-
https://github.com/bukzor/s6-packaging/blob/dockerize/execline/debian/patches/02_link_against_lib
I think the Right fix is to add -lskarnet to the requirments of execline.so
and s6.so similar to what I've done.
I was likely overzealous when I changed the .a requirements and should back
that bit out.
On Wed, Aug 12, 2015 at 10:18 AM, Buck Evan wrote:
> Removing the s6 patch gives essentially
Removing the s6 patch gives essentially the same issue:
dpkg-shlibdeps: warning: symbol open_write used by
debian/s6/usr/lib/x86_64-linux-gnu/libs6.so.2.2.0.0 found in none of the
libraries
dpkg-shlibdeps: warning: symbol byte_chr used by
debian/s6/usr/lib/x86_64-linux-gnu/libs6.so.2.2.0.0 found i
This is the compilation line for libexecline.so
exec gcc -o libexecline.so -std=c99 -fomit-frame-pointer -fno-exceptions
-fno-unwind-tables -fno-asynchronous-unwind-tables -Wa,--noexecstack
-fno-stack-protector
-pipe -Wall -fPIC -Wl,--hash-style=both -L/usr/lib/skalibs
-L/usr/lib/x86_64-linux-gn
Removing the execline patch results in:
dh_shlibdeps -O--parallel -O--autodest
dpkg-shlibdeps: warning: symbol waitpid_nointr used by
debian/execline/usr/lib/x86_64-linux-gnu/libexecline.so.2.1.3.0 found in
none of the libraries
dpkg-shlibdeps: warning: symbol PROG used by
debian/execline/usr/
On Wed, 12 Aug 2015 13:50:19 +0200
Olivier Brunel wrote:
> Hi Steve,
>
> On 08/11/15 20:40, Steve Litt wrote:
> > On Tue, 11 Aug 2015 19:58:59 +0200
> >
> > Hi j,
> >
> > I just got done reading http://jjacky.com/anopa/ .
> >
> > I love the inclusion of the needs directory, as well as directo
Hi Steve,
On 08/11/15 20:40, Steve Litt wrote:
> On Tue, 11 Aug 2015 19:58:59 +0200
>
> Hi j,
>
> I just got done reading http://jjacky.com/anopa/ .
>
> I love the inclusion of the needs directory, as well as directory
> after.
>
> I love the way you distinquish one-shots from long-run by whet
(Please follow-up this part of the thread to the skaware mailing-list.)
On 12/08/2015 08:37, Buck Evan wrote:
-
https://github.com/bukzor/s6-packaging/blob/dockerize/execline/debian/patches/02_link_against_libskarnet.patch
-
https://github.com/bukzor/s6-packaging/blob/dockeriz
On 12/08/2015 08:29, Buck Evan wrote:
apt-cache search is generally how people look for such things.
Certainly the word skalibs will be mentioned and will match on such a
search.
Oh, that's fine then.
I did some googling and I believe it derives from the apache process.
http://www.apache.or
A common trend is to display stderr in red.
This often makes reading a log more clear.
The current practice that I see for logging stdout and stderr in the
daemontools family is to run some equivalent of `exec 2>&1`, which
irretrievably interleaves the two streams.
Have any of you seen a clean i
10 matches
Mail list logo
