Re: [dbast0s@yahoo.com.br: undefined reference getopt_long]

Re: [dbast0s@yahoo.com.br: undefined reference getopt_long]

[Glenn Morris]

Richard Stallman wrote:

> From: "Daniel C. Bastos" <dbast0s@yahoo.com.br>
> Subject: undefined reference getopt_long
> To: bug-gnu-emacs@gnu.org
> Date: Mon, 27 Aug 2007 11:39:01 -0400
[...]
> 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'


Shouldn't it pick up the definition of getopt_long from getopt1.c in
this case? Or does etags.c need to include "getopt.h" in this case,
rather than <getopt.h>?

Re: [dbast0s@yahoo.com.br: undefined reference getopt_long]

[Richard Stallman]

    Shouldn't it pick up the definition of getopt_long from getopt1.c in
    this case? Or does etags.c need to include "getopt.h" in this case,
    rather than <getopt.h>?

I see that the file getopt.h is no longe rin the source.
Instead, the sources include getopt_.h.

Perhaps something failed to create getopt.h as it was supposed to.

Re: [dbast0s@yahoo.com.br: undefined reference getopt_long]

[Glenn Morris]

Richard Stallman wrote:

> I see that the file getopt.h is no longe rin the source.
> Instead, the sources include getopt_.h.
>
> Perhaps something failed to create getopt.h as it was supposed to.

Cannot do anything more on this without more input from the OP (have
asked twice, mails seem to bounce), or anyone else who has this
problem.