[gentoo-user] Pre-merge checks

[gentoo-user] Pre-merge checks

[Francisco Ares]

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

Hi, All.

I would like to see all pre-merge checks prior to build a new kernel, just
to make sure all kernel configurations needed até satisfied.

I thought on issuing an "emerge -e world" then interrupting the process at
the beguinning of the first package build.  But this looks a weird way of
doing things.

Is there any other way?

Thanks!
Francisco

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

RE: [gentoo-user] Pre-merge checks

[Raffaele BELARDI]

> From: Francisco Ares <frares@gmail.com> 
> I would like to see all pre-merge checks prior to build a new kernel, just to make sure all kernel configurations needed até satisfied.

Does it really do pre-merge checks? I thought it only unpacked the kernel source.

raffaele

Re: [gentoo-user] Pre-merge checks

[Neil Bothwick]

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

On 24 January 2020 13:48:23 GMT, Francisco Ares <frares@gmail.com> wrote:
>Hi, All.
>
>I would like to see all pre-merge checks prior to build a new kernel,
>just
>to make sure all kernel configurations needed até satisfied.
>
>I thought on issuing an "emerge -e world" then interrupting the process
>at
>the beguinning of the first package build.  But this looks a weird way
>of
>doing things.
>
>Is there any other way?
>
>Thanks!
>Francisco

If you use make oldconfig, this shouldn't be necessary as all the checks have already been made. 
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [gentoo-user] Pre-merge checks

[Francisco Ares]

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

Em sex, 24 de jan de 2020 13:21, Neil Bothwick <neil@stfw.net> escreveu:

> On 24 January 2020 13:48:23 GMT, Francisco Ares <frares@gmail.com> wrote:
>>
>> Hi, All.
>>
>> I would like to see all pre-merge checks prior to build a new kernel,
>> just to make sure all kernel configurations needed até satisfied.
>>
>> I thought on issuing an "emerge -e world" then interrupting the process
>> at the beguinning of the first package build.  But this looks a weird way
>> of doing things.
>>
>> Is there any other way?
>>
>> Thanks!
>> Francisco
>>
>>
> If you use make oldconfig, this shouldn't be necessary as all the checks
> have already been made.
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>

This system has quite an old Gentoo instalation, and some packages show
complaints about kernel features.  So I thought on doing an overall check.

Thanks!

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

Re: [gentoo-user] Pre-merge checks

[Dale]

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

Francisco Ares wrote:
>
>
> Em sex, 24 de jan de 2020 13:21, Neil Bothwick <neil@stfw.net
> <mailto:neil@stfw.net>> escreveu:
>
>     On 24 January 2020 13:48:23 GMT, Francisco Ares <frares@gmail.com
>     <mailto:frares@gmail.com>> wrote:
>
>         Hi, All.
>
>         I would like to see all pre-merge checks prior to build a new
>         kernel, just to make sure all kernel configurations needed até
>         satisfied.
>
>         I thought on issuing an "emerge -e world" then interrupting
>         the process at the beguinning of the first package build.  But
>         this looks a weird way of doing things.
>
>         Is there any other way?
>
>         Thanks!
>         Francisco
>
>
>     If you use make oldconfig, this shouldn't be necessary as all the
>     checks have already been made.
>     -- 
>     Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
>
> This system has quite an old Gentoo instalation, and some packages
> show complaints about kernel features.  So I thought on doing an
> overall check.
>
> Thanks!

I've noticed in the past that some packages do that during the configure
stage.  The only way I know to do those is to emerge the package and
check the configure stage in the log.  Keep in mind, some options won't
cause a fail.  It may continue to build without certain options but not
be able to perform whatever those options add capabilities for.  One
that I used to get a error from is the nvidia drivers package.  On rare
occasions it wanted certain options enabled.  I don't know if it still
does that but would be surprised if it complained when certain drivers
are not enabled. 

There may be a way to use elogviewer to do this, or at least some way to
"scan"/grep the log files there.  I suspect you could view those logs,
figure out a common set of words/phrases and then get a tool to find
them for you.  My grep, xargs and friends abilities are not only
limited, they almost don't exist compared to what I've seen some post on
here.  Maybe that idea will allow someone who is good at them to come up
with ways to accomplish that or give you ideas if you have those skills. 

Hope that helps.

Dale

:-)  :-) 

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

Re: [gentoo-user] Pre-merge checks

[Adam Carter]

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

On Sat, Jan 25, 2020 at 12:48 AM Francisco Ares <frares@gmail.com> wrote:

> Hi, All.
>
> I would like to see all pre-merge checks prior to build a new kernel, just
> to make sure all kernel configurations needed até satisfied.
>
> I thought on issuing an "emerge -e world" then interrupting the process at
> the beguinning of the first package build.  But this looks a weird way of
> doing things.
>
> Is there any other way?
>
>
The command looks through the ebuilds of installed packages and dumps a
list of of the kernel options that the ebuilds are looking for, so its a
start. You'll then need to check this against your .config file.

If you're not using the new $PORTDIR of /var/db/repos/gentoo you'll need to
change that of course.

for pak in $(qlist -ICv | sed
's/\(.*\)\(\/.*\)\(-[0-9].*\)/\1\2\2\3.ebuild/g' ); do grep -s -H
'CONFIG_CHECK="' /var/db/repos/gentoo/$pak ; done

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

Re: [gentoo-user] Pre-merge checks

[Francisco Ares]

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

Em sáb, 25 de jan de 2020 21:34, Adam Carter <adamcarter3@gmail.com>
escreveu:

> On Sat, Jan 25, 2020 at 12:48 AM Francisco Ares <frares@gmail.com> wrote:
>
>> Hi, All.
>>
>> I would like to see all pre-merge checks prior to build a new kernel,
>> just to make sure all kernel configurations needed até satisfied.
>>
>> I thought on issuing an "emerge -e world" then interrupting the process
>> at the beguinning of the first package build.  But this looks a weird way
>> of doing things.
>>
>> Is there any other way?
>>
>>
> The command looks through the ebuilds of installed packages and dumps a
> list of of the kernel options that the ebuilds are looking for, so its a
> start. You'll then need to check this against your .config file.
>
> If you're not using the new $PORTDIR of /var/db/repos/gentoo you'll need
> to change that of course.
>
> for pak in $(qlist -ICv | sed
> 's/\(.*\)\(\/.*\)\(-[0-9].*\)/\1\2\2\3.ebuild/g' ); do grep -s -H
> 'CONFIG_CHECK="' /var/db/repos/gentoo/$pak ; done
>
>
>
> This is awesome!

Thank you!

To check out what the developer think it is really important, there's the
ERROR_ string to grep for.

Best Regards,
Francisco

>
>

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