[gentoo-user] emerge --info

[gentoo-user] emerge --info

[Willie Wong]

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/vanilla

Why doesn't it say gcc-4.1.1?

Thanks, 

Willie
-- 
"`...and the Universe,' continued the waiter, determined 
not to be deflected on his home stretch, `will explode 
later for your pleasure.'
Ford's head swivelled slowly towards him. He spoke with 
feeling.
`Wow,' he said, `What sort of drinks do you serve in this 
place?'
The waiter laughed a polite little waiter's laugh.
`Ah,' he said, `I think sir has perhaps misunderstood me.'
`Oh, I hope not,' breathed Ford."

- Ford in paradise. 
Sortir en Pantoufles: up 24 days, 13:37
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --info

[Mauro Faccenda]

On Mon, 18 Sep 2006 16:08:53 -0400
Willie Wong <wwong@Princeton.EDU> 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 did emerge --info and saw:
> 
> Portage 2.1.2_pre1 (default-linux/x86/2006.0, gcc-3.4.6/vanilla
> 
> Why doesn't it say gcc-4.1.1?

had you defined that you want to use gcc-4 with gcc-config?

[]'s
	.m
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --info

[Willie Wong]

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 *
   is the selected compiler).
2) fix_lib_tools.sh 3.4.6
3) emerge -e system

at this point emerge --info shows what I posted originally:

Portage 2.1.2_pre1 (default-linux/x86/2006.0, gcc-3.4.6/vanilla

W

-- 
"`I think you ought to know that I'm feeling very 
depressed.'"
"`Life, don't talk to me about life.'"
"`Here I am, brain the size of a planet and they ask me to 
take you down to the bridge. Call that "job satisfaction"? 
'Cos I don't.'"
"`I've got this terrible pain in all the diodes down my 
left side.'"

- Guess who. 
Sortir en Pantoufles: up 24 days, 14:07
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --info

[Richard Fish]

On 9/18/06, Willie Wong <wwong@princeton.edu> 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-config -l shows that
>    [6] i686-pc-linux-gnu-4.1.1 *
>    is the selected compiler).

You really should follow the gcc upgrade guide [1], which tells you to:

source /etc/profile

at this point.

-Richard

[1] http://www.gentoo.org/doc/en/gcc-upgrading.xml
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --info

[Willie Wong]

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 have a .bash_history
to back me up ;p

I did a bit of experimentation, actually, and found that the behaviour
is different on my laptop and on my desktop. On my laptop where this
problem originates (default-linux profile and ~x86 keyword):

1) no matter what I do with gcc-config (and sourcing /etc/profile
afterwards of course), the emerge --info gives the same compiler. 

2) To actually affect the emerge --info I need to use 'eselect
compiler set', i.e. now that I issued 'eselect compiler set 6', my
emerge --info reads correctly
Portage 2.1.2_pre1 (default-linux/x86/2006.0, gcc-4.1.1/vanilla

But on my desktop (which is on a hardened profile with x86 keyword)

3) gcc-config would successfully change the output of emerge --info

4) and 'eselect compiler' returns
"!!! Error: Can't load module compiler"
which is natural, since eselect-compiler is keyworded ~x86. 

Are those the intended behaviour? Or is something seriously wacked up?

W
-- 
Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd 
be sitting around in darkened rooms munching pills and listening to repetitive
music.
Sortir en Pantoufles: up 24 days, 14:43
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --info

[Richard Fish]

On 9/18/06, Willie Wong <wwong@princeton.edu> 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_ put in your email.  ;-]

> I did a bit of experimentation, actually, and found that the behaviour
> is different on my laptop and on my desktop. On my laptop where this
> problem originates (default-linux profile and ~x86 keyword):
>
> 1) no matter what I do with gcc-config (and sourcing /etc/profile
> afterwards of course), the emerge --info gives the same compiler.
>
> 2) To actually affect the emerge --info I need to use 'eselect
> compiler set', i.e. now that I issued 'eselect compiler set 6', my
> emerge --info reads correctly
> Portage 2.1.2_pre1 (default-linux/x86/2006.0, gcc-4.1.1/vanilla

eselect compiler should not work *anywhere* as eselect-compiler is
currently package masked for everybody [1].

-Richard

[1] http://bugs.gentoo.org/show_bug.cgi?id=143697
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --info

[Willie Wong]

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 unmerged eselect-compiler and all is good. 

Thanks, 

W
-- 
"And if I could just strech my arm like a cartoon character, I could show you 
what r does."  ~DeathMech, S. Sondhi. P-town PHY 205
Sortir en Pantoufles: up 24 days, 19:39
-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] emerge --info

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 221 bytes --]

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...

[-- Attachment #2: Type: text/html, Size: 306 bytes --]

Re: [gentoo-user] emerge --info

[Michael Orlitzky]

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 everything, reads your make.conf, applies the
profile variables, etc. in the order that they would be used for any
other "emerge ..." action, and then it dumps everything to the screen.
So it's "what will be used for the next build, if nothing changes
between now and then."

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.

Re: [gentoo-user] emerge --info

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 295 bytes --]

> 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?

[-- Attachment #2: Type: text/html, Size: 584 bytes --]

Re: [gentoo-user] emerge --info

[Dale]

[-- Attachment #1: Type: text/plain, Size: 542 bytes --]

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 --info
>
> What is the logic of that?


Can you see if this helps get you what you want?

emerge --info firefox 

At the bottom, it has info specific to firefox but don't know if it will
be what you are looking for or not. 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 1531 bytes --]

Re: [gentoo-user] emerge --info

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

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
forced off?

[-- Attachment #2: Type: text/html, Size: 663 bytes --]

[gentoo-user] Re: emerge --info

[Martin Vaeth]

Adam Carter <adamcarter3@gmail.com> wrote:
> so why have it if you force it off?

One thing is the ebuild and the other is the profile:
It might be different in a different profile.

Re: [gentoo-user] emerge --info

[Alan McKinnon]

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 currently right now in make.conf with zero
consideration to last, future, next or previous builds.

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] emerge --info

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 556 bytes --]

On Thu, Dec 7, 2017 at 2:36 AM, Alan McKinnon <alan.mckinnon@gmail.com>
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=custom-cflags does not work on firefox...
>
> It reflects what is currently right now in make.conf with zero
> consideration to last, future, next or previous builds.


Thanks. That's what I was trying, but failing, to say with #1,

[-- Attachment #2: Type: text/html, Size: 974 bytes --]

Re: [gentoo-user] Re: emerge --info

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 330 bytes --]

On Wed, Dec 6, 2017 at 11:42 PM, Martin Vaeth <martin@mvath.de> wrote:

> Adam Carter <adamcarter3@gmail.com> wrote:
> > so why have it if you force it off?
>
> One thing is the ebuild and the other is the profile:
> It might be different in a different profile


Ok ill have a look though the profiles to see what they're doing.

[-- Attachment #2: Type: text/html, Size: 730 bytes --]