Re: CVS commit: src/sys/conf

[christos%astron.com@localhost (Christos Zoulas)]

In article <CADbF7edbi1NG5O2LZqoh42zoAMvdEYoMF3bLyr=Pynu0PZx9=Q%mail.gmail.com@localhost>,
Masao Uebayashi  <uebayasi%gmail.com@localhost> wrote:
>On Thu, Nov 13, 2014 at 11:54 PM, Christos Zoulas <christos%zoulas.com@localhost> wrote:
>> Any solution that involves hard-coding the currently used linksets by
>> name is no solution for me. Please come up with a complete solution,
>> and present it for discussion. Yes, the current script is a hack, but
>> it is a hack we've been using for a while successfully.
>
>I would not call it "hard-coding"; link-sets are well-known.  All the
>used link-sets are known before building.
>
>I'd detect unknown link-set sections and make that build fail.  This
>is more strict.
>
>I'd also provide a way to declare extra link-set for 3rd party modules.

Can you please explain what you are trying to do and what are your goals?
I am not sure if I agree that the list of link_sets is "well known". If
you ask anyone to enumerate them they will probably resort to nm the
kernel...

christos