From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Failed builds of kbuild and cdrdao with "undefined reference to `__alloca'"
Date: Sat, 10 Feb 2018 23:07:42 +0100 [thread overview]
Message-ID: <1987439.LOUiqFuUr8@pinacolada> (raw)
In-Reply-To: <20180210023904.mmez2u5uwrohabqr@solfire>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
Am Samstag, 10. Februar 2018, 03:39:04 CET schrieb tuxic@posteo.de:
>
> > What's your sys-libs/glibc ?!
>
> [I] sys-libs/glibc
> Installed versions: 9999(2.2)^s(09:54:43 AM 02/04/2018)
Heh, guessed so. Welcome to the wonderful world of early testing.
It will take some time until the rest of Gentoo catches up with the changes in
glibc-2.27 (and later).
In the meantime I suggest you file bug reports (with Gentoo, and if there's no
newer upstream version yet, also with upstream). Patches will eventually
materialize.
Please always indicate clearly which version of glibc (i.e., either the
version, or in case of 9999, the commit or precise date/time).
[Just for the record, running glibc-9999 on your main system is in my opinion
crazy. And I package that thing.]
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2018-02-10 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 14:03 [gentoo-user] Failed builds of kbuild and cdrdao with "undefined reference to `__alloca'" tuxic
2018-02-04 19:29 ` [gentoo-user] " Ian Zimmerman
2018-02-09 21:02 ` [gentoo-user] " Andreas K. Huettel
2018-02-10 2:39 ` tuxic
2018-02-10 22:07 ` Andreas K. Huettel [this message]
2018-02-12 10:31 ` Joerg Schilling
2018-02-13 4:23 ` tuxic
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=1987439.LOUiqFuUr8@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-user@lists.gentoo.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