Hi everyone

I've tried setting --quiet-build=n and --quiet=n but to no avail
because I have --jobs set to higher than 1. I've checked
/var/log/emerge.log but that's only the emerge output not the make
output that I'm looking for. What am I missing here?

Thank you
--
Dex

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEE2ISlnG4xsFQ7Mswex1Y9SzFDEmcFAmJZqckACgkQx1Y9SzFD EmecNw//b/c2GSsqXUZSIYh1ZToA0e2csUYThyuFpb9zTdjDB9nRxQZhvxxuznKB GuFr0H3+6ug9s7WAJKrtXNu55sYLBO4LVrUKgbCz84w0XrKKk2bvFyEmN++rCWa3 2FMbx2WTqkjkdhV6IU9g+1icnDUTg3TcnMtnFxPqhI8vPtX1eMo+aTU5vILQmEro Tey+DmoxeOyZf7Lt1eQYB06wEmRWmcj3qIymA4bAUhQ1RAa8jfIiZ3JsD5G6kJpA pUTfGb3eNOfnOE6GUgPU5A3XlY9XKPtKI1PcUjnSedylILLhkiQ08s30lCEIgYDa glUwRp6BFseMpUChBowX+6cBzLwXpNbAcm7RKfMfKrgs0cnsLS9XTU7PbOeiwz7X vePuxWXwmZ6wvVAETWZMuUM+WBTGNAk/rMvXn6p+JHwouK14wSNAP6rI8sAN//RG O0cSRQr/merOYTptV1kjKJ/3liLO9lKyB5XWkytKiynydmOaLYUky41tOGFr484P waH5qeqNU0jhmEOam8XHYvQyfFMdX5+NlH+2Y6DGOozEiZ3FGrY2oUOIjZ3fZoyy 2t2fIPUMG1T6gR0E32Ow6WSFCg4W0gPpxLnhezE2l9p/ytlW2iKQ7CXJt8GyeeDJ P9RK2JOnvQU+P2Xm78lRvTWrjEKHWmn8tvLql69xEWYsO1xEMfg=
=ixiQ
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 15 Apr 2022 20:35:49 +0200, Arve Barsnes wrote:

I've tried setting --quiet-build=n and --quiet=n but to no avail
because I have --jobs set to higher than 1. I've checked /var/log/emerge.log but that's only the emerge output not the make
output that I'm looking for. What am I missing here?

You're missing that the make log is in a separate place for each
package. Usually in /var/tmp/portage somewhere. As you noticed, setting --jobs higher than 1 automatically sets --quiet-build, and makes it
unable to activate.

It will tell you after portage is finished about any failed packages,
and where that log is, but if you want to see all that output while it's compiling you'd need to script a way to automatically check for new
build.log files in /var/tmp/portage as new package compile jobs starts
and monitor them.

Basically, my advice is to use --jobs=1 if you want to see the output.

Or set

PORTAGE_ELOG_CLASSES="log warn error"
PORTAGE_ELOG_SYSTEM="save"

in make.conf to have the build logs saved to /var/log/portage/elog.


--
Neil Bothwick

Windows Error #09: Mouse not found. Press mouse button to continue.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmJZvRYACgkQ92eFu0QS MJh04A//RLJ4R8a4wP01gf6kFjHaVZg+HxLO8JrorrWHfrFJQG1W2MbA9FACy2x7 nD5LeedPdZb8dCCNCkzu58OYIHko7/7O8aGDQaj9TguEi6DS4DpaNz26zDUQ9kGW 5CCvmbqTZvxDDdXGv8oAWAVEUwWgMfnM8Mznie617sysjqdYobHOLAzy3bywIIz1 iaUOurb+d6fGzBIeG6VInX/8AlO1kDLemXeMpjvWuLR2260yMNHaVdOoOgrz70rd 1o+nN8m1lje7tetFGOVXj+pr/w7SziZh9YmRkWyQ1jtwY2dmuQS44LW/xQZ/dQeD 0JQnr5xrDEcBHZ14XNq7TU76fjP8C1lBeVO0jG2g3KstUfkTV2UIx9ORcAqZaHsk K1UQfcwguGtLmv80TvjQEe2H8AWNV3C4obITjZAonUEfinQnqxENXPscbAWaREPr t0Z5tQArlw8UkpErxaH2urqCr50dhI1ryMDwTq57EjQoebCwCumsPfNDG0Aquqxc ML+UQ64nbfOTrZ3MCL02EDC/VQGD14XuBprHexw+ESHhifVOjO62r6BQIuM1mgdT ST2f83GWTnQh1DkRFI9/jOQeV2K4focBwnAX6VGGUeSdv3ZQKMraG6yOofJ0Larf 2XzkL/L764gsOObtVfioP1z6wJdAfbL0/fghXEJU2ku7IvoIEPg=
=degC
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, 15 Apr 2022 at 19:23, Dex Conner <cantcuckthis@danwin1210.de> wrote:

Hi everyone

I've tried setting --quiet-build=n and --quiet=n but to no avail
because I have --jobs set to higher than 1. I've checked
/var/log/emerge.log but that's only the emerge output not the make
output that I'm looking for. What am I missing here?

You're missing that the make log is in a separate place for each package. Usually in /var/tmp/portage somewhere. As you noticed, setting --jobs
higher than 1 automatically sets --quiet-build, and makes it unable to activate.

It will tell you after portage is finished about any failed packages, and
where that log is, but if you want to see all that output while it's
compiling you'd need to script a way to automatically check for new
build.log files in /var/tmp/portage as new package compile jobs starts and monitor them.

Basically, my advice is to use --jobs=1 if you want to see the output.

Regards,
Arve

<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 15 Apr 2022 at 19:23, Dex Conner &lt;<a href="mailto:cantcuckthis@danwin1210.de">cantcuckthis@danwin1210.de</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi everyone<br>

I&#39;ve tried setting --quiet-build=n and --quiet=n but to no avail<br> because I have --jobs set to higher than 1. I&#39;ve checked<br> /var/log/emerge.log but that&#39;s only the emerge output not the make<br> output that I&#39;m looking for. What am I missing here?<br> <br></blockquote><div><br></div><div>You&#39;re missing that the make log is in a separate place for each package. Usually in /var/tmp/portage somewhere. As you noticed, setting --jobs higher than 1 automatically sets --quiet-build, and makes it unable
to activate.</div><div><br></div><div>It will tell you after portage is finished about any failed packages, and where that log is, but if you want to see all that output while it&#39;s compiling you&#39;d need to script a way to automatically check for
new build.log files in /var/tmp/portage as new package compile jobs starts and monitor them.</div><div><br></div><div>Basically, my advice is to use --jobs=1 if you want to see the output.</div><div><br></div><div>Regards,</div><div>Arve<br></div></div></


--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)