Re: warnings

[David Bateman]

Daniel J Sebald wrote:
> John W. Eaton wrote:
>> On  2-Mar-2007, Daniel J Sebald wrote:
>>
>> | I rebuilt the CVS version to verify that I'm now getting what seems
>> like 200-300 warnings such as:
>> | | [snip]
>> | warning: autoload: not replacing existing entry for chol2inv =>
>> /usr/local/libexec/octave/2.9.9+/oct/i686-pc-linux-gnu/chol.oct
>> | warning: autoload: not replacing existing entry for cholinv =>
>> /usr/local/libexec/octave/2.9.9+/oct/i686-pc-linux-gnu/chol.oct
>> | warning: autoload: not replacing existing entry for csymamd =>
>> /usr/local/libexec/octave/2.9.9+/oct/i686-pc-linux-gnu/ccolamd.oct
>> | warning: autoload: not replacing existing entry for etree =>
>> /usr/local/libexec/octave/2.9.9+/oct/i686-pc-linux-gnu/colamd.oct
>> | warning: autoload: not replacing existing entry for symamd =>
>> /usr/local/libexec/octave/2.9.9+/oct/i686-pc-linux-gnu/colamd.oct
>> | [snip]
>> | | when launching octave.  This makes little sense to me.  Is
>> autoload attempting to replace a file with a file of a different name?
>>
>> It means you have multiple autoloads for the same function name,
>> probably in separate PKG_ADD files.
> 
> Oh, I see.  I take it this is a newly added warning simply to identify
> redundancy?
> 
>  Maybe it should say "ignoring
>> duplicate" instead of "not replacing existing".  Can you suggest a
>> better message?
> 
> How about
> warning: autoload: duplicate function name chol2inv, ignoring entry inside
>         /usr/local/libexec/octave/2.9.9+/oct/i686-pc-linux-gnu/chol.oct
> 
> ?
> 


Remove the octave-forge miscellaneous package.. There is a PKG_ADD in
the one you have that overloads the dispatch_help and builtin functions,
when it shouldn't as these are part of octave

D.