From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: GNU grep developers <grep-devel@gnu.org>,
Paul Eggert <eggert@cs.ucla.edu>,
Bruce Dubbs <bruce.dubbs@gmail.com>,
Jim Meyering <jim@meyering.net>
Subject: Re: libsigsegv on LinuxFromScratch
Date: Sat, 19 Sep 2020 01:24:25 +0200 [thread overview]
Message-ID: <2990514.c6dJG7T8G4@omega> (raw)
In-Reply-To: <e33aca4a-5e06-afd2-43da-acedf861ce64@gmail.com>
Bruce Dubbs wrote in
<https://lists.gnu.org/r/grep-devel/2020-09/msg00052.html>
<https://lists.gnu.org/r/grep-devel/2020-09/msg00053.html> :
> > checking for libsigsegv... yes
> > checking how to link with libsigsegv... -lsigsegv
>
> I get:
>
> checking for libsigsegv... yes
> checking how to link with libsigsegv... /usr/lib/libsigsegv.so
> /usr/lib/libc.a
Is this really a multiline string (also in the value of LIBSIGSEGV in
config.status)? Or are these space-separated values?
In the latter case, is linking with libc.a normally working?
Also, if there is a file /usr/lib/libsigsegv.la, can you please show
its contents?
Bruno
next prev parent reply other threads:[~2020-09-18 23:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2a6xnu1sv.fsf@meyering.net>
[not found] ` <075a970b-f6aa-d2bb-e007-609a711085b2@gmail.com>
[not found] ` <CA+8g5KGBjFfHzafN2WFH6az5bQR8f68B1J-ETVWEBXvuDUL5rA@mail.gmail.com>
[not found] ` <17a0fe42-3ac6-9209-6f60-cddb5467f263@gmail.com>
[not found] ` <994fd316-0420-4b94-a1de-fea7d891c4ac@gmail.com>
2020-09-18 22:16 ` new snapshot available: grep-3.4-almost.26-5419 Paul Eggert
2020-09-18 22:42 ` Bruce Dubbs
2020-09-18 23:24 ` Bruno Haible [this message]
2020-09-18 23:47 ` libsigsegv on LinuxFromScratch Bruce Dubbs
2020-09-19 8:06 ` Bruce Dubbs
2020-09-19 23:47 ` Bruno Haible
2020-09-20 1:16 ` Bruce Dubbs
2020-09-20 23:15 ` Paul Eggert
2020-09-23 0:58 ` stack bounds Bruno Haible
2020-09-23 1:28 ` Paul Eggert
2020-10-10 12:08 ` Bruno Haible
2020-10-10 20:10 ` Paul Eggert
2020-10-10 21:49 ` Bruno Haible
2020-10-11 18:49 ` Paul Eggert
2020-10-11 22:08 ` Bruno Haible
2020-10-11 22:56 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2990514.c6dJG7T8G4@omega \
--to=bruno@clisp.org \
--cc=bruce.dubbs@gmail.com \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=grep-devel@gnu.org \
--cc=jim@meyering.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).