From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Joshua Ismael Haase Hernández" <hahj87@gmail.com>,
supervision@list.skarnet.org
Subject: Re: s6 v2.9.2.0 compiles only disabling execline
Date: Thu, 08 Oct 2020 00:22:11 +0000 [thread overview]
Message-ID: <em62d2df3e-b6f2-4a6b-a1d8-a34b9fb8a56b@elzian> (raw)
In-Reply-To: <CA+ypG2b3OC4hhUEeK0Bw-BGj919hzzZrG_2m63h+4oau-_fMkw@mail.gmail.com>
>I'm building s6 from source on latest git tags and it seems to fail because
>it cannot link execline:
>
>./configure --disable-execline; make # works
>
>./configure; make # fails with message
>exec gcc -o s6-ftrig-listen -pipe -Wall -std=c99 -fno-exceptions
>-fno-unwind-tables -fno-asynchronous-unwind-tables -Wa,--noexecstack
>-ffunction-sections -fdata-sections -O2 -fomit-frame-pointer
>-fno-stack-protector -Wl,--sort-section=alignment -Wl,--sort-common
>-Wl,--gc-sections src/pipe-tools/s6-ftrig-listen.o libs6.a.xyzzy -lexecline
>-lskarnet
>/home/linuxbrew/.linuxbrew/bin/ld: cannot find -lexecline
>collect2: error: ld returned 1 exit status
>make: *** [Makefile:138: s6-ftrig-listen] Error 1
>
>Execline is installed and available.
>
>$ ls /usr/lib/execline/
>libexecline.a
>
>Any clues about how to solve this?
./configure --with-lib=/usr/lib/execline
Alternatively, build execline with --libdir=/usr/lib so the
static libraries can be found in the default linker path.
Yeah, it's annoying. It's the result of an initial design decision that
was theoretically logical but that has brought nothing but headaches
since. I don't want to change the default libdir, but I will probably
have to do it at some point because a lot of users are bumping on this.
--
Laurent
next prev parent reply other threads:[~2020-10-08 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 20:52 Joshua Ismael Haase Hernández
2020-10-07 21:30 ` Joshua Ismael Haase Hernández
2020-10-08 0:22 ` Laurent Bercot [this message]
2020-10-08 4:15 ` Joshua Ismael Haase Hernández
2020-10-08 9:05 ` Laurent Bercot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=em62d2df3e-b6f2-4a6b-a1d8-a34b9fb8a56b@elzian \
--to=ska-supervision@skarnet.org \
--cc=hahj87@gmail.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).