public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
To: "B. James Phillippe" <bryan@terran.org>
Cc: Jim Wilson <wilson@cygnus.com>, egcs Mailing List <egcs@cygnus.com>
Subject: Re: [980425] makeinfo errors
Date: Thu, 30 Apr 1998 01:40:00 -0000	[thread overview]
Message-ID: <vyz67jr3dp3.fsf@issan.informatik.uni-dortmund.de> (raw)
In-Reply-To: <Pine.LNX.3.96.980429151345.23091A-100000@earth.terran.org>

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

  reply	other threads:[~1998-04-30  1:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-28 22:14 B. James Phillippe
1998-04-29 15:13 ` Jim Wilson
1998-04-29 18:36   ` B. James Phillippe
1998-04-30  1:40     ` Andreas Schwab [this message]
1998-04-30 20:03     ` Jim Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vyz67jr3dp3.fsf@issan.informatik.uni-dortmund.de \
    --to=schwab@issan.informatik.uni-dortmund.de \
    --cc=bryan@terran.org \
    --cc=egcs@cygnus.com \
    --cc=wilson@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).