On Wed, Dec 20, 2000 at 09:55:10PM +0900, Jun-ichiro itojun Hagino wrote:
> 	when we "make include" under lib/libcom_err, we build compile_et binary
> 	under lib/libcom_err.  this has bad sideeffect to upgrades - if we have
> 	certain changes in libc (like assert -> __assert13 change), we fail
> 	to build compile_et since include files are now out of sync with
> 	libc.
> 
> 	what is the right way to address this problem?  actually similar thing
> 	may happen with rpcgen and *.x.

How do you get out of the mess once it happens? Just tried building and
installing a new /usr/bin/compile_et just in case, but still see

hash.lo: In function `hashtabnew':
hash.lo(.text+0x1d): undefined reference to `__assert13'

etc in libasn1 (will try new libcom_err next)

Cheers,

Patrick