On Thu, Dec 7, 2017 at 2:36 AM, Alan McKinnon
wrote:
> On 06/12/2017 04:31, Adam Carter wrote:
> > Does the output reflect;
> > 1. What will be used for the next build
> > 2. What was used on the last successful build
> > 3. What was used on the last build attempt
> >
> > If its 1 or 3, then USE=
On 06/12/2017 04:31, Adam Carter wrote:
> Does the output reflect;
> 1. What will be used for the next build
> 2. What was used on the last successful build
> 3. What was used on the last build attempt
>
> If its 1 or 3, then USE=custom-cflags does not work on firefox...
It reflects what is curre
Can you see if this helps get you what you want?
>
> emerge --info firefox
>
>
Yeah that's what i'm talking about. The custom-cflags is forced unset on
the second (filtered) output of USE, so why have it if you force it off?
Perhaps there's other factors that affect if it gets allowed through or
f
Adam Carter wrote:
>
> Firefox is very finicky about CFLAGS. That's the only reason we have
> USE=custom-cflags in the first place; otherwise, we always try to
> respect them.
>
>
> custom-cflags is currently filtered out according to the before and
> after USE definition from emerge --
> Firefox is very finicky about CFLAGS. That's the only reason we have
> USE=custom-cflags in the first place; otherwise, we always try to
> respect them.
>
>
custom-cflags is currently filtered out according to the before and after
USE definition from emerge --info
What is the logic of that?
On 12/05/2017 09:31 PM, Adam Carter wrote:
> Does the output reflect;
> 1. What will be used for the next build
> 2. What was used on the last successful build
> 3. What was used on the last build attempt
>
> If its 1 or 3, then USE=custom-cflags does not work on firefox...
Portage initializes ev
Does the output reflect;
1. What will be used for the next build
2. What was used on the last successful build
3. What was used on the last build attempt
If its 1 or 3, then USE=custom-cflags does not work on firefox...
On Mon, Sep 18, 2006 at 03:57:34PM -0700, Penguin Lover Richard Fish squawked:
> eselect compiler should not work *anywhere* as eselect-compiler is
> currently package masked for everybody [1].
>
Ah, I got it on my system before the pmask, and never did realize that
it was masked. Now I've unmerg
On 9/18/06, Willie Wong <[EMAIL PROTECTED]> wrote:
I did follow the guide and did source /etc/profile. I just forgot to
type that step in in composing the e-mail. And I have a .bash_history
to back me up ;p
Sorry, although we aren't psychic, so we can only base responses on
what you _actually_
On Mon, Sep 18, 2006 at 01:43:31PM -0700, Penguin Lover Richard Fish squawked:
> You really should follow the gcc upgrade guide [1], which tells you to:
>
> source /etc/profile
>
I did follow the guide and did source /etc/profile. I just forgot to
type that step in in composing the e-mail. And I
On 9/18/06, Willie Wong <[EMAIL PROTECTED]> wrote:
On Mon, Sep 18, 2006 at 05:18:09PM -0300, Penguin Lover Mauro Faccenda squawked:
> > Why doesn't it say gcc-4.1.1?
>
> had you defined that you want to use gcc-4 with gcc-config?
of course. That is what I did:
1) gcc-config 6 (after which gcc-c
On Mon, Sep 18, 2006 at 05:18:09PM -0300, Penguin Lover Mauro Faccenda squawked:
> > Why doesn't it say gcc-4.1.1?
>
> had you defined that you want to use gcc-4 with gcc-config?
of course. That is what I did:
1) gcc-config 6 (after which gcc-config -l shows that
[6] i686-pc-linux-gnu-4.1.1
On Mon, 18 Sep 2006 16:08:53 -0400
Willie Wong <[EMAIL PROTECTED]> wrote:
> Where does emerge --info retrieve compiler information?
>
> I am in the middle of trying to upgrade to gcc-4.1.1, and wanted to
> file a bug report on some packages that is failing (which worked with
> gcc-3.4.6), and I d
Where does emerge --info retrieve compiler information?
I am in the middle of trying to upgrade to gcc-4.1.1, and wanted to
file a bug report on some packages that is failing (which worked with
gcc-3.4.6), and I did emerge --info and saw:
Portage 2.1.2_pre1 (default-linux/x86/2006.0, gcc-3.4.6/va
14 matches
Mail list logo
