Re: lintian goes wild?

["Christian T. Steigies" <cts@debian.org>]

On Sun, Sep 09, 2001 at 01:32:27AM -0400, Matt Zimmerman wrote:
> On Sat, Sep 08, 2001 at 09:45:09PM -0700, Sean 'Shaleh' Perry wrote:
> 
> > > Unquoted string "supported" may clash with future reserved word at (eval 112)
> > > line 1.
> > > Operator or semicolon missing before &supported at (eval 112) line 1.
> > > Ambiguous use of & resolved as operator & at (eval 112) line 1.
> > > Unquoted string "supported" may clash with future reserved word at (eval 115)
> > > line 1.
> > > Operator or semicolon missing before &supported at (eval 115) line 1.
> > > Ambiguous use of & resolved as operator & at (eval 115) line 1.
> > 
> > I can not find the word 'supported' anywhere in the source.  Colour me
> > confused.
> 
> If you can reproduce this running under the Perl debugger, it should be
> possible to find out what is being evaluated when this warning is printed.
> It's likely part of some Perl module.

main::(/usr/lib/perl/5.6.1/asm/unistd.ph:114):
114:        eval 'sub __NR_iopl () { &not  &supported;}' unless defined(&__NR_iopl);
  DB<2> 
Unquoted string "supported" may clash with future reserved word at (eval 122)[/usr/lib/perl/5.6.1/asm/unistd.ph:114] line 1.
Operator or semicolon missing before &supported at (eval 122)[/usr/lib/perl/5.6.1/asm/unistd.ph:114] line 1.
Ambiguous use of & resolved as operator & at (eval 122)[/usr/lib/perl/5.6.1/asm/unistd.ph:114] line 1.
main::(/usr/lib/perl/5.6.1/asm/unistd.ph:115):
115:        eval 'sub __NR_vhangup () {111;}' unless defined(&__NR_vhangup);
  DB<2> 


grep supported /usr/lib/perl/5.6.1/asm/unistd.ph  
    eval 'sub __NR_iopl () { &not  &supported;}' unless defined(&__NR_iopl);
    eval 'sub __NR_vm86 () { &not  &supported;}' unless defined(&__NR_vm86);

Hmm? Minja nje garwaju perl.

Christian