From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: GLIBC Devel <libc-alpha@sourceware.org>
Subject: No rule to make target '.../check-abi-libcidn.out', needed by 'tests'. Stop.
Date: Sun, 10 Sep 2017 13:52:00 -0000 [thread overview]
Message-ID: <8281132.p2MZuEknP0@porto> (raw)
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Hi,
I'm trying to figure out why in our Gentoo builds the test fail consistently
(since 2.22 at least, many arches) with something like
make subdir=libidn -C libidn ..=../ tests
make[2]: Entering directory '/var/tmp/portage/sys-libs/glibc-2.26-r1/work/
glibc-2.26/libidn'
make[2]: *** No rule to make target '/var/tmp/portage/sys-libs/glibc-2.26-r1/
work/build-x86-x86_64-pc-linux-gnu-nptl/libidn/check-abi-libci
dn.out', needed by 'tests'. Stop.
make[2]: Leaving directory '/var/tmp/portage/sys-libs/glibc-2.26-r1/work/
glibc-2.26/libidn'
make[1]: *** [Makefile:216: libidn/tests] Error 2
make[1]: Leaving directory '/var/tmp/portage/sys-libs/glibc-2.26-r1/work/
glibc-2.26'
make: *** [Makefile:9: check] Error 2
Any hints on how to debug this?
It may well be a Gentoo-specific error, but I can't see any of our 2-3 patches
touch that area.
Full build log (xz-compressed) is here:
https://bugs.gentoo.org/attachment.cgi?id=493702
Thanks a lot in advance,
Andreas
https://github.com/gentoo/glibc/commits/gentoo/2.26
https://bugs.gentoo.org/show_bug.cgi?id=589370
https://bugs.gentoo.org/show_bug.cgi?id=623548
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-09-10 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 13:52 Andreas K. Huettel [this message]
2017-09-10 14:35 ` Andreas K. Huettel
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=8281132.p2MZuEknP0@porto \
--to=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.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).