[980425] makeinfo errors

[Andreas Schwab]

B James Phillippe <bryan@terran.org> writes:

|> No, that wasn't it.  However, I did find the problem.  I happen to be one
|> of those very rare people who lives with the environment variable
|> POSIXLY_CORRECT set. :)  getopt (et al) act differently with this variable
|> set, and programs which use command-line arguments in a non-POSIXly
|> conformant fashion will probably break.  When I unset this variable, the
|> problem vanishes.  I will look at it closer this evening to determine
|> exactly what is happening.  My guess is that argument processing is
|> stopping early.

POSIX does not allow options to occur after non-options.  If you put
POSIXLY_CORRECT into the environment then getopt follows POSIX.

-- 
Andreas Schwab                                      "And now for something
schwab@issan.informatik.uni-dortmund.de              completely different"
schwab@gnu.org