Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<200309182008.h8IK8EWa018786@bolt.sonic.net>
From:	Bryan Higgins <bryan AT motet DOT com>
Reply-To:	bryan AT motet DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: getopt: ugly linker messages
In-reply-to:	Your message of Thu, 18 Sep 2003 15:56:07 EDT
Date:	Thu, 18 Sep 2003 13:08:14 -0700

On Thu, 18 Sep 2003 15:56:07 -0400, Christopher Faylor wrote:

>On Thu, Sep 18, 2003 at 12:53:22PM -0700, Bryan Higgins wrote:
>>How can I suppress the linker messages
>>
>>Info: resolving _opterr by linking to __imp__opterr (auto-import)
>>Info: resolving _optarg by linking to __imp__optarg (auto-import)
>>Info: resolving _optopt by linking to __imp__optopt (auto-import)
>>Info: resolving _optind by linking to __imp__optind (auto-import)
>>
>>which now appear?
>
>#include <getopt.h>
>
>and don't define any of the getopt variables yourself.

Since POSIX getopt is handled in unistd.h, shouldn't the magic appear there?

>there is no getopt(3)

Maybe there needs to be to document the need for getopt.h?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -