Re: port-i386/50183: Executing #!-less script causes compat_freebsd errors

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

The following reply was made to PR port-i386/50183; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%NetBSD.org@localhost, port-i386-maintainer%netbsd.org@localhost, 
	gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, 
	gson%gson.org@localhost (Andreas Gustafsson)
Cc: 
Subject: Re: port-i386/50183: Executing #!-less script causes compat_freebsd errors
Date: Mon, 31 Aug 2015 06:29:59 -0400

 On Aug 31, 10:20am, jdbaker%mylinuxisp.com@localhost ("John D. Baker") wrote:
 -- Subject: Re: port-i386/50183: Executing #!-less script causes compat_freeb
 
 | The following reply was made to PR port-i386/50183; it has been noted by GNATS.
 | 
 | From: "John D. Baker" <jdbaker%mylinuxisp.com@localhost>
 | To: gnats-bugs%NetBSD.org@localhost
 | Cc: 
 | Subject: Re: port-i386/50183: Executing #!-less script causes compat_freebsd
 |  errors
 | Date: Mon, 31 Aug 2015 05:15:34 -0500 (CDT)
 | 
 |  I would guess the issue with the actual subject of this PR is related to
 |  the default ellision of COMPAT_FREEBSD from i386 GENERIC kernels some time
 |  ago.
 |  
 |  I've seen similar errors but on my sparc systems and so far as I can
 |  tell only during boot (right after root file system type determination).
 |  I think there are other situations which trigger these messages during
 |  normal operation, but I don't recall now what they are.  I don't notice
 |  any loss of function on the system as a result, however.
 |  
 |  It only happens with my custom kernels from which I've removed all
 |  COMPAT_* options (as I don't need them for my usage).  In my case, the
 |  messages are as follows:
 |  
 |  [...]
 |  kobj_checksyms, 882: [compat]: linker error: symbol `esigcode' not found
 |  kobj_checksyms, 882: [compat]: linker error: symbol `sigcode' not found
 |  WARNING: module error: unable to affix module `compat', error 8
 |  kobj_checksyms, 882: [compat]: linker error: symbol `esigcode' not found
 |  kobj_checksyms, 882: [compat]: linker error: symbol `sigcode' not found
 |  WARNING: module error: unable to affix module `compat', error 8
 |  kobj_checksyms, 882: [compat]: linker error: symbol `esigcode' not found
 |  kobj_checksyms, 882: [compat]: linker error: symbol `sigcode' not found
 |  WARNING: module error: unable to affix module `compat', error 8
 |  kobj_checksyms, 882: [compat]: linker error: symbol `esigcode' not found
 |  kobj_checksyms, 882: [compat]: linker error: symbol `sigcode' not found
 |  WARNING: module error: unable to affix module `compat', error 8
 |  [...]
 
 This means that the the module is missing required symbols. You can
 repeat this ad-nauseum manually by running 'modload compat' or the name
 of the module that is failing. The fix is to add the missing symbols, files,
 dependencies etc. to the module.
 
 christos