From: Benno Schulenberg <bensberg@telfort.nl>
To: bug-gnulib@gnu.org
Subject: commit eb32c992 causes trouble on older Debian
Date: Tue, 27 Apr 2021 13:01:29 +0200 [thread overview]
Message-ID: <04a87155-c80f-555e-8f39-67c00adeb296@telfort.nl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 939 bytes --]
Hi,
Commit eb32c992 from five days ago causes trouble when trying to compile
GNU nano from git on an older Debian box:
make[4]: Entering directory `/home/bens/NANO/lib'
depbase=`echo malloc/dynarray_at_failure.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -std=gnu11 -DHAVE_CONFIG_H -I. -I.. -I/usr/include/ncursesw -O1 -Wall
-MT malloc/dynarray_at_failure.o -MD -MP -MF $depbase.Tpo -c -o
malloc/dynarray_at_failure.o malloc/dynarray_at_failure.c &&\
mv -f $depbase.Tpo $depbase.Po
In file included from ./libc-config.h:162:0,
from malloc/dynarray_at_failure.c:20:
./cdefs.h:496:31: fatal error: bits/long-double.h: No such file or directory
compilation terminated.
When stepping back to the preceding commit (882243dc), things compile fine.
The most recent commit (4b071c11 at the moment) still shows the problem.
$lsb_release -d
Description: Debian GNU/Linux 7.10 (wheezy)
Benno
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-04-27 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 11:01 Benno Schulenberg [this message]
2021-04-27 18:28 ` commit eb32c992 causes trouble on older Debian Paul Eggert
2021-04-28 8:04 ` Benno Schulenberg
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=04a87155-c80f-555e-8f39-67c00adeb296@telfort.nl \
--to=bensberg@telfort.nl \
--cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).