unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: "Daniel C. Bastos" <dbast0s@yahoo.com.br>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: undefined reference getopt_long
Date: Sat, 01 Sep 2007 16:21:17 -0400	[thread overview]
Message-ID: <hfr6lirvb6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <18130.61461.588478.572113@blade3.toledo.com> (Daniel C. Bastos's message of "Mon, 27 Aug 2007 11:39:01 -0400")

"Daniel C. Bastos" wrote:

> gcc -I/usr/X11R6/include -I/usr/local/include -L/usr/local/lib    -DHAVE_CONFIG_H    -I. -I../src -I/home/dbastos/tmp/emacs/lib-src -I/home/dbastos/tmp/emacs/lib-src/../src -Wl,-znocombreloc -L/usr/X11R6/lib -I/usr/X11R6/include -I/usr/local/include -L/usr/local/lib -g -O2 -DEMACS_NAME="\"GNU Emacs"\" -DVERSION="\"22.1.50\"" /home/dbastos/tmp/emacs/lib-src/etags.c getopt.o getopt1.o regex.o -lutil    -lc -o etags
> /tmp/cc86z2lb.o: In function `main':
> /home/dbastos/tmp/emacs/lib-src/etags.c(.text+0x71f): undefined reference to `getopt_long'


I don't know much about this, so I might not help much. lib-src/
contains some getopt* files that ought to provide a definition of
getopt_long if your system does not have one. Can you figure out why
they are not working for you?

getopt1.c contains a definition of getopt_long, and your command-line
above shows getopt1.o being included in the compile command.

Did the file getopt.h in your lib-src directory get generated? Is
etags.c finding it when it gets compiled?

What are the values of GETOPT_H and GETOPTDEPS in your
lib-src/Makefile?

  reply	other threads:[~2007-09-01 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27 15:39 undefined reference getopt_long Daniel C. Bastos
2007-09-01 20:21 ` Glenn Morris [this message]
2007-09-12  0:45   ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=hfr6lirvb6.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=dbast0s@yahoo.com.br \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).