From: Eli Zaretskii <eliz@gnu.org>
To: Fei Ding <fdingiit@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Problem about getopt.c
Date: Fri, 20 Mar 2015 10:54:00 -0000 [thread overview]
Message-ID: <83619wvt0a.fsf@gnu.org> (raw)
In-Reply-To: <CAGmPkfJow2J2J_80Dk4FHwVX4-mYCgPVzsAiPeb2VHDnGENaFQ@mail.gmail.com>
> Date: Fri, 20 Mar 2015 16:05:39 +0800
> From: Fei Ding <fdingiit@gmail.com>
>
> /////////////////////////////////////////
> getopt.o:
>
> getopt1.o:
>
> getpwd.o:
> U __errno_location
> 0000000000000008 b failure_errno.3486
> U free
> U getcwd
> U getenv
> 0000000000000000 T getpwd
> 0000000000000000 b pwd.3485
> U stat
> U xmalloc
> /////////////////////////////////////////
>
> Nothing there in getopt.o and getopt1.o, it is so strange to me.
> What's more, I write a printf() in the beginning of
> _getopt_internal(), and make clean && make && make install, but there
> is no printing message.
>
> Did I miss something?
My crystal ball says that on your system the conditions for defining
ELIDE_CODE in getopt.c are fulfilled, and so libiberty's getopt is not
used.
prev parent reply other threads:[~2015-03-20 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 8:05 Fei Ding
2015-03-20 8:20 ` Fwd: " Fei Ding
2015-03-20 10:54 ` Eli Zaretskii [this message]
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=83619wvt0a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=fdingiit@gmail.com \
--cc=gdb@sourceware.org \
/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).