From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Failed builds of kbuild and cdrdao with "undefined reference to `__alloca'"
Date: Sun, 4 Feb 2018 11:29:10 -0800 [thread overview]
Message-ID: <20180204192910.s3nrs6ezj6zeobim@matica.foolinux.mooo.com> (raw)
In-Reply-To: <20180204140328.lvky4vmwmu36c4ih@solfire>
On 2018-02-04 15:03, tuxic@posteo.de wrote:
> I still have the problem of failed builds due to an
> 'undefined reference to `__alloca''. I recompiled
> gcc/glibc and I am using linux-4.15.1 (from kernel.org)
> with linux-headers 4.15. .
>
> Affected are (at least) cdrdao and kbuild.
[...]
> I am using gcc (Gentoo 7.3.0 p1.0) 7.3.0. I recompiled glibc.
> I did https://wiki.gentoo.org/wiki/Upgrading_GCC
>
> What can cause this problem and how can I fix it?
To make progress against this, you'll have to look at the build logs, or
let others look at them.
Before doing that, I would try to build the affected packages outside of
portage, saving the output of "configure" and "make". If you also see
the problem that way, try with the stable gcc and compare logs.
BTW alloca() is a very peculiar way of allocating memory and only a few
packages use it, fortunately.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.
next prev parent reply other threads:[~2018-02-04 19:29 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 ` Ian Zimmerman [this message]
2018-02-09 21:02 ` Andreas K. Huettel
2018-02-10 2:39 ` tuxic
2018-02-10 22:07 ` Andreas K. Huettel
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=20180204192910.s3nrs6ezj6zeobim@matica.foolinux.mooo.com \
--to=itz@very.loosely.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