* Re: [gentoo-user] CFLAGs change but no filter/strip/replace in ebuild
2017-12-09 9:10 [gentoo-user] CFLAGs change but no filter/strip/replace in ebuild Adam Carter
@ 2017-12-09 9:10 ` Alan McKinnon
2017-12-09 9:37 ` Adam Carter
0 siblings, 1 reply; 5+ messages in thread
From: Alan McKinnon @ 2017-12-09 9:10 UTC (permalink / raw
To: gentoo-user
On 09/12/2017 11:10, Adam Carter wrote:
> # grep -ic flags yasm-1.3.0.ebuild
> 0
>
> However, emerge --info yasm shows me that only -march -O2 -pipe make it
> through. Where is the code that strips the others?
>
Have you checked yasm's Makefile?
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* [gentoo-user] CFLAGs change but no filter/strip/replace in ebuild
@ 2017-12-09 9:10 Adam Carter
2017-12-09 9:10 ` Alan McKinnon
0 siblings, 1 reply; 5+ messages in thread
From: Adam Carter @ 2017-12-09 9:10 UTC (permalink / raw
To: gentoo-user@lists.gentoo.org
[-- Attachment #1: Type: text/plain, Size: 161 bytes --]
# grep -ic flags yasm-1.3.0.ebuild
0
However, emerge --info yasm shows me that only -march -O2 -pipe make it
through. Where is the code that strips the others?
[-- Attachment #2: Type: text/html, Size: 222 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] CFLAGs change but no filter/strip/replace in ebuild
2017-12-09 9:10 ` Alan McKinnon
@ 2017-12-09 9:37 ` Adam Carter
2017-12-09 10:21 ` Alan McKinnon
0 siblings, 1 reply; 5+ messages in thread
From: Adam Carter @ 2017-12-09 9:37 UTC (permalink / raw
To: gentoo-user@lists.gentoo.org
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
On Sat, Dec 9, 2017 at 8:10 PM, Alan McKinnon <alan.mckinnon@gmail.com>
wrote:
> On 09/12/2017 11:10, Adam Carter wrote:
> > # grep -ic flags yasm-1.3.0.ebuild
> > 0
> >
> > However, emerge --info yasm shows me that only -march -O2 -pipe make it
> > through. Where is the code that strips the others?
> >
>
> Have you checked yasm's Makefile?
>
There's mentions of CFLAGS in there but I don't have the knowledge to
understand it. Is there a way I can tweak what the makefiles have done? I
tried adding;
append-flags <flag>
in the src_configure() section, but <flag> doesnt get added, according to
emerge --info
[-- Attachment #2: Type: text/html, Size: 1252 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] CFLAGs change but no filter/strip/replace in ebuild
2017-12-09 9:37 ` Adam Carter
@ 2017-12-09 10:21 ` Alan McKinnon
2017-12-09 11:45 ` Adam Carter
0 siblings, 1 reply; 5+ messages in thread
From: Alan McKinnon @ 2017-12-09 10:21 UTC (permalink / raw
To: gentoo-user
On 09/12/2017 11:37, Adam Carter wrote:
> On Sat, Dec 9, 2017 at 8:10 PM, Alan McKinnon <alan.mckinnon@gmail.com
> <mailto:alan.mckinnon@gmail.com>> wrote:
>
> On 09/12/2017 11:10, Adam Carter wrote:
> > # grep -ic flags yasm-1.3.0.ebuild
> > 0
> >
> > However, emerge --info yasm shows me that only -march -O2 -pipe
> make it
> > through. Where is the code that strips the others?
> >
>
> Have you checked yasm's Makefile?
>
>
> There's mentions of CFLAGS in there but I don't have the knowledge to
> understand it. Is there a way I can tweak what the makefiles have done?
> I tried adding;
>
> append-flags <flag>
>
> in the src_configure() section, but <flag> doesnt get added, according
> to emerge --info
I would strongly advise against that, just on principle.
yasm is an assembler, and as such it's right at the bottom of the stack.
It's not unreasonable for such a package to use different FLAGS etc as
it's not a userland app. It's an app that builds things you use to build
a userland.
I would recommend you touch base with the package maintainer for answers.
btw, why is this situation a problem? Is something wrong with the yasm
portage builds you?
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] CFLAGs change but no filter/strip/replace in ebuild
2017-12-09 10:21 ` Alan McKinnon
@ 2017-12-09 11:45 ` Adam Carter
0 siblings, 0 replies; 5+ messages in thread
From: Adam Carter @ 2017-12-09 11:45 UTC (permalink / raw
To: gentoo-user@lists.gentoo.org
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
>
> I would strongly advise against that, just on principle.
>
> yasm is an assembler, and as such it's right at the bottom of the stack.
> It's not unreasonable for such a package to use different FLAGS etc as
> it's not a userland app. It's an app that builds things you use to build
> a userland.
>
> I would recommend you touch base with the package maintainer for answers.
>
> btw, why is this situation a problem? Is something wrong with the yasm
> portage builds you?
>
I'm trying to avoid a reinstall. With profile 17, i found many packages
required -fPIC to build (probably due to some mucking around i've done with
hardened, and/or gentoo devs earlier force on of PIE in gcc that they later
backed out.). yasm build is failing and saying try -fPIC.
[-- Attachment #2: Type: text/html, Size: 1151 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-12-09 11:46 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-09 9:10 [gentoo-user] CFLAGs change but no filter/strip/replace in ebuild Adam Carter
2017-12-09 9:10 ` Alan McKinnon
2017-12-09 9:37 ` Adam Carter
2017-12-09 10:21 ` Alan McKinnon
2017-12-09 11:45 ` Adam Carter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox