From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Make failed to compile: symbol __alloca not found...
Date: Mon, 11 Dec 2017 18:55:44 +0100 [thread overview]
Message-ID: <20171211175544.sil3s2kpazltzbnp@solfire> (raw)
In-Reply-To: <6f2bf4e3-9399-3d50-284f-0454ccf23ac8@st.com>
On 12/11 06:38, Raffaele Belardi wrote:
> tuxic@posteo.de wrote:
> > On 12/11 10:12, Raffaele Belardi wrote:
> >> tuxic@posteo.de wrote:
> >>>
> >>> sys-devel/make-4.2.1-r1 failed to compile with this:
> >>>
> >>> How can I recompile make -- it is still non-PIE and one of those
> >>> application which I cant convince to be friendly to gcc :)
> >>>
> >>> How serious is this alloca-thingy at all?
> >>>
> >>
> >> Is there anything special about your environment? For example, I notice '--as-needed' in
> >> your linker flags: that affects how the linker works which in turn may cause your problem,
> >> was it your choice or a default option?
> >>
> >
> > My root-environment look like this:
> >
>
> What's the output of:
>
> $ grep CFLAGS /etc/portage/make.conf
> $ grep USE /etc/portage/make.conf
>
> Are you defining per-package USE or CFLAGS?
>
> raffaele
>
I am not defining per package CFLAGS an alike.
CFLAGS="-march=native -O2 -pipe"
USE="nvidia X lua sdl mp3 flac jack alsa gtk cairo sndfile qt3support kpathsea gif tga jpeg png jpeg2k mad dvb dvdr encode lzo bzip2 ogg sox v4l v4l2 vorbis x264 x265 zsh-completion -hal -lirc"
USE_PYTHON=3.5
Meino
next prev parent reply other threads:[~2017-12-11 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 6:28 [gentoo-user] Make failed to compile: symbol __alloca not found tuxic
2017-12-11 9:12 ` Raffaele Belardi
2017-12-11 17:27 ` tuxic
2017-12-11 17:38 ` Raffaele Belardi
2017-12-11 17:55 ` tuxic [this message]
2017-12-11 16:13 ` David Haller
2017-12-11 17:23 ` tuxic
2017-12-11 20:07 ` David Haller
2017-12-12 2:07 ` tuxic
2017-12-12 6:26 ` Raffaele Belardi
2017-12-12 11:09 ` Joerg Schilling
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=20171211175544.sil3s2kpazltzbnp@solfire \
--to=tuxic@posteo.de \
--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