FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 12-03-2011, 02:37 PM
Indi
 
Default Emerge ignoring make.conf entries

On Sat, Dec 03, 2011 at 03:40:01PM +0100, Hinnerk van Bruinehsen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> that is not the verbose flag, but silent-build.

Hmm, I always thought the "-v" was the verbose switch, and that it should
work properly regardless of what's in make.conf. It *used* to work
properly here, I've been using "emerge -vauND world" to update for ages...

> If you want the old
> behaviour back, you can add
>
> EMERGE_DEFAULT_OPTS="--quiet-build=n"
>
> to your make.conf
>

Thanks for the suggestion, but there is no change here from trying it.
I expected that, as nothing was changed in make.conf in the first place.
I see on planet.gentoo.org they implemented this change (eselect never
informed me of it, BTW, which is extremely poor practice) last month --
apparently it broke something here.

Unfortunately about five days passed before I had occasion to notice it,
so now I don't have a clean backup that doesn't share the problem. :

Even including this in make.conf, I still get "quiet-build mode":

EMERGE_DEFAULT_OPTS="--quiet-build=n"
EMERGE_DEFAULT_OPTS="--verbose"

The only thing that works is manually using "--quiet-build=n" on the
command line, so it seems the real problem here is "emerge ignoring
EMERGE_DEFAULT_OPTS entries in make.conf". Sunject line has been
appropriately updated..

On an entirely other subject, I see the mail2news gateway still breaks
threads -- what, a year after I first pointed it out? *sigh*
Ok, my apologies for using it, but really I just cannot justify the ratio
of 24k recieved emails to one sent, so I really have to use the usenet
group to read and reply. As long as it's broken, my posts will break
threads -- sorry! Got too much else to do to fiddle about with that.

indi


> On 03.12.2011 15:23, Indi wrote:
> > Howdy y'all,
> >
> > About a month or so ago I did an update which seems to have caused
> > portage to lose the ability to work verbosely. Ever since it looks
> > like this: <paste> idd@gh:[~]9:07:23 $ sudo emerge -vauND
> > adobe-flash
> >
> > These are the packages that would be merged, in order:
> >
> > Calculating dependencies... done! [ebuild U ]
> > sys-libs/glibc-2.14.1-r1 [2.14.1] USE="nls -debug -gd -glibc-omitfp
> > (-hardened) (-multilib) -profile (-selinux) -vanilla" 150 kB
> > [ebuild R ] sys-devel/binutils-2.22 USE="nls zlib%*
> > -multislot -multitarget -static-libs -test -vanilla" 0 kB [ebuild
> > U ] dev-libs/openssl-1.0.0e-r1 [1.0.0e] USE="bindist kerberos sse2
> > zlib -gmp -rfc3779 -static-libs% -test" 3,950 kB [ebuild U ]
> > net-misc/curl-7.23.1 [7.22.0] USE="ipv6 ssl threads -ares -gnutls
> > -idn -kerberos -ldap -nss -ssh% -static-libs -test (-libssh2%)"
> > 2,321 kB [ebuild U ] dev-libs/cyrus-sasl-2.1.25 [2.1.23-r6]
> > USE="berkdb openldap ssl -authdaemond -gdbm -java -kerberos
> > -ldapdb% -mysql -pam -postgres -sample -sqlite% -srp -static-libs%
> > -urandom (-crypt%*) (-ntlm_unsupported_patch%)" 5,088 kB [ebuild
> > U ] dev-vcs/git-1.7.8 [1.7.8_rc4] USE="blksha1 cgi curl cvs iconv
> > perl python subversion threads webdav -doc -emacs -gtk (-ppcsha1)
> > -tk -xinetd" 3,941 kB
> >
> > Total: 6 packages (5 upgrades, 1 reinstall), Size of downloads:
> > 15,448 kB
> >
> > Would you like to merge these packages? [Yes/No] y
> >>>> Verifying ebuild manifests Starting parallel fetch Emerging
> >>>> (1 of 6) sys-libs/glibc-2.14.1-r1 Jobs: 0 of 6 complete, 1
> >>>> running Load avg: 2.16, 1.66, 1.10
> >
> > </paste>
> >
> > Remerged python, verified the right python via eselect, remerge
> > portage, etc etc etc etc I just can't seem to get proper output
> > from emerge anymore no matter what. Other than that everything is
> > working fine, but I do need to see actual output.
> >
> > Anyone know what to do to fix this?
> >
> > TIA!
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.18 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJO2jJSAAoJEJwwOFaNFkYchdcIAMctrVsjKm pbLlCXDUNsFL20
> /ruew4FRY8IWPe7HagAwkWbenHKXpTIomPF2LKb4U7HjHc9vS/mIggwbnLuIS8QU
> f2DXMhVws1m6H3c0o8fRL/d99kQUcRhtIl6uk7GJVlh13KLsDd5NxxDHXpcEqWtA
> Ch9GIQOQo+phs4pNysAkUpTfRyuEkoe99nLL8+vxc31vFZ2/czRac8zhyzywSk5l
> N4dlHgknOLVD4w/D4Sw4rTVBJgupO5Y6VxHV5iq2m4jdUWVUmQsrwSMXVFVOU5SJ
> +XZiv7qa6jlf2YUvpxEfombzUgd14Y+lhAjprLOq/BzbUfrH1btYMmhaTByDcAM=
> =2TOV
> -----END PGP SIGNATURE-----
 
Old 12-03-2011, 03:09 PM
Neil Bothwick
 
Default Emerge ignoring make.conf entries

On Sat, 3 Dec 2011 10:37:51 -0500, Indi wrote:

> > that is not the verbose flag, but silent-build.
>
> Hmm, I always thought the "-v" was the verbose switch, and that it
> should work properly regardless of what's in make.conf. It *used* to
> work properly here, I've been using "emerge -vauND world" to update for
> ages...

-v affects the verbosity of emerge, not of gcc, the output of which is
still hidden. Thisis a useful distinction, I prefer to see everything that
portage has to tell me without spamming my screen with gcc output.

> > If you want the old
> > behaviour back, you can add
> >
> > EMERGE_DEFAULT_OPTS="--quiet-build=n"
> >
> > to your make.conf

> Even including this in make.conf, I still get "quiet-build mode":
>
> EMERGE_DEFAULT_OPTS="--quiet-build=n"
> EMERGE_DEFAULT_OPTS="--verbose"
>
> The only thing that works is manually using "--quiet-build=n" on the
> command line, so it seems the real problem here is "emerge ignoring
> EMERGE_DEFAULT_OPTS entries in make.conf".

Is it that your second setting overrides the first? Try putting all the
settings in one variable assignation.


--
Neil Bothwick

Top Oxymorons Number 38: Government organization
 
Old 12-03-2011, 03:31 PM
Hinnerk van Bruinehsen
 
Default Emerge ignoring make.conf entries

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03.12.2011 17:09, Neil Bothwick wrote:
> On Sat, 3 Dec 2011 10:37:51 -0500, Indi wrote:
>
>>> that is not the verbose flag, but silent-build.
>>
>> Hmm, I always thought the "-v" was the verbose switch, and that
>> it should work properly regardless of what's in make.conf. It
>> *used* to work properly here, I've been using "emerge -vauND
>> world" to update for ages...
>
> -v affects the verbosity of emerge, not of gcc, the output of which
> is still hidden. Thisis a useful distinction, I prefer to see
> everything that portage has to tell me without spamming my screen
> with gcc output.
>
>>> If you want the old behaviour back, you can add
>>>
>>> EMERGE_DEFAULT_OPTS="--quiet-build=n"
>>>
>>> to your make.conf
>
>> Even including this in make.conf, I still get "quiet-build
>> mode":
>>
>> EMERGE_DEFAULT_OPTS="--quiet-build=n"
>> EMERGE_DEFAULT_OPTS="--verbose"
>>
>> The only thing that works is manually using "--quiet-build=n" on
>> the command line, so it seems the real problem here is "emerge
>> ignoring EMERGE_DEFAULT_OPTS entries in make.conf".
>
> Is it that your second setting overrides the first? Try putting all
> the settings in one variable assignation.
>
>
EMERGE_DEFAULT_OPTS="--quiet-build=n --keep-going"

works for me. I think if you want one option per line something like:

EMERGE_DEFAULT_OPTS="--quiet-build=n"
EMERGE_DEFAULT_OPTS="$EMERGE_DEFAULT_OPTS --verbose"

would be appropriate. Otherwise you override the first assignment with
the second as Neil already stated.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJO2k7bAAoJEJwwOFaNFkYcAYYIALsdrs+Ui9 IxP5OU66oYEthK
4uK9vMsn523Dtvaze05ypiZgMxd+TJekMW27pP2U7BRYrE3pzO mDr6id35I3yMUM
i5q18Id13MH/t2c880X9ek2TpWL/+mGTqkWcTM7n/9GuTmguO1kdzqmlyLZ5s4l5
etic2ObLv4l4Kwmh50YMn1NEeu2GrG8UDCJFAkIX4debWuOiWH 17ShQ4aP722vsA
frP6Bhsv+IfbI8Y00JrBP4S5HYmXfMb4lwjINEeBJohfWoKmvE 1SzR4CdC7NEPQS
Kc1hiBuM9rJMzFUBypuwhJ+iTFBMKoKzhXC6TaCGnaMbqfC4P6 JwOzNNjrpQPXM=
=AWIf
-----END PGP SIGNATURE-----
 
Old 12-03-2011, 03:39 PM
Indi
 
Default Emerge ignoring make.conf entries

On Sat, Dec 03, 2011 at 05:20:01PM +0100, Neil Bothwick wrote:
> On Sat, 3 Dec 2011 10:37:51 -0500, Indi wrote:
>
> > > that is not the verbose flag, but silent-build.
> >
> > Hmm, I always thought the "-v" was the verbose switch, and that it
> > should work properly regardless of what's in make.conf. It *used* to
> > work properly here, I've been using "emerge -vauND world" to update for
> > ages...
>
> -v affects the verbosity of emerge, not of gcc, the output of which is
> still hidden. Thisis a useful distinction, I prefer to see everything that
> portage has to tell me without spamming my screen with gcc output.
>
> > > If you want the old
> > > behaviour back, you can add
> > >
> > > EMERGE_DEFAULT_OPTS="--quiet-build=n"
> > >
> > > to your make.conf
>
> > Even including this in make.conf, I still get "quiet-build mode":
> >
> > EMERGE_DEFAULT_OPTS="--quiet-build=n"
> > EMERGE_DEFAULT_OPTS="--verbose"
> >
> > The only thing that works is manually using "--quiet-build=n" on the
> > command line, so it seems the real problem here is "emerge ignoring
> > EMERGE_DEFAULT_OPTS entries in make.conf".
>
> Is it that your second setting overrides the first? Try putting all the
> settings in one variable assignation.
>

Thanks Neil, that was exactly it.
You wouldn't believe some of the serious, major problems I've overcome on
my own -- but whenever I do have to ask for help, it seems it's usually for
something obvious and stupid.

Oh well, if I never made mistakes I'd just be harder to live with....

--
caveat utilitor
♫ ❤ ♫ ❤ ♫ ❤ ♫ ❤
 

Thread Tools




All times are GMT. The time now is 08:51 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org