1 |
On 09/12/2017 11:37, Adam Carter wrote: |
2 |
> On Sat, Dec 9, 2017 at 8:10 PM, Alan McKinnon <alan.mckinnon@×××××.com |
3 |
> <mailto:alan.mckinnon@×××××.com>> wrote: |
4 |
> |
5 |
> On 09/12/2017 11:10, Adam Carter wrote: |
6 |
> > # grep -ic flags yasm-1.3.0.ebuild |
7 |
> > 0 |
8 |
> > |
9 |
> > However, emerge --info yasm shows me that only -march -O2 -pipe |
10 |
> make it |
11 |
> > through. Where is the code that strips the others? |
12 |
> > |
13 |
> |
14 |
> Have you checked yasm's Makefile? |
15 |
> |
16 |
> |
17 |
> There's mentions of CFLAGS in there but I don't have the knowledge to |
18 |
> understand it. Is there a way I can tweak what the makefiles have done? |
19 |
> I tried adding; |
20 |
> |
21 |
> append-flags <flag> |
22 |
> |
23 |
> in the src_configure() section, but <flag> doesnt get added, according |
24 |
> to emerge --info |
25 |
|
26 |
|
27 |
I would strongly advise against that, just on principle. |
28 |
|
29 |
yasm is an assembler, and as such it's right at the bottom of the stack. |
30 |
It's not unreasonable for such a package to use different FLAGS etc as |
31 |
it's not a userland app. It's an app that builds things you use to build |
32 |
a userland. |
33 |
|
34 |
I would recommend you touch base with the package maintainer for answers. |
35 |
|
36 |
btw, why is this situation a problem? Is something wrong with the yasm |
37 |
portage builds you? |
38 |
|
39 |
-- |
40 |
Alan McKinnon |
41 |
alan.mckinnon@×××××.com |