From: Peter Dyballa <Peter_Dyballa@Freenet.DE>
To: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.50; Undefined symbol: _res_9_init
Date: Sat, 20 Oct 2007 00:51:27 +0200 [thread overview]
Message-ID: <786A49C2-4433-47BA-97F3-1C35A0C3ADEF@Freenet.DE> (raw)
In-Reply-To: <A3002BE9-CBDD-4D29-8C5B-7CEA45845017@Freenet.DE>
Am 19.10.2007 um 17:38 schrieb Peter Dyballa:
> /sw/lib/odcctools/bin/ld: Undefined symbols:
> _res_9_init
Compiling src/process.c with -E -dD I get in the output:
#define HAVE_GETADDRINFO 1
...
#define HAVE_RES_INIT 1
...
#define res_init res_9_init /* from resolv.h */
...
int res_9_init (void); /* from resolv.h */
...
res_9_init (); /* line #3094 src/process.c in
"make_network_process" */
/* could also happen on line #3144 when HAVE_GETADDRINFO is 0 */
Nm tells about libc:
/usr/lib/libc.dylib(res_init.o):
9004561c T _res_init
so it's obviously a mistake to re-define res_init as res_9_init. This
re-definition happens in resolv.h in:
#ifndef __BIND_NOSTATIC
...
#define res_init res_9_init
...
__BEGIN_DECLS
...
int res_init __P((void));
...
__END_DECLS
#endif
In the Fink project for compilation of netcat 0.6.1 CFLAGS is set to
-D__BIND_NOSTATIC
Re-configuring with this among the CPPFLAGS used allows to create
temacs. /usr/include/resolv.h is the only file that uses
__BIND_NOSTATIC, src/process.c is the only file that includes
resolv.h (found by compiling with -H), so on (some ?) Mac OS X src/
process.c should be compiled with an extra CPPFLAG or CFLAG -
D__BIND_NOSTATIC when HAVE_RES_INIT is 1.
--
Greetings
Pete
The future will be much better tomorrow.
-- George W. Bush
next prev parent reply other threads:[~2007-10-19 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 15:38 23.0.50; Undefined symbol: _res_9_init Peter Dyballa
2007-10-19 22:51 ` Peter Dyballa [this message]
2007-10-21 6:45 ` Stephen J. Turnbull
2007-10-21 10:21 ` Peter Dyballa
2007-10-21 15:39 ` Peter Dyballa
2007-10-21 15:36 ` Peter Dyballa
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=786A49C2-4433-47BA-97F3-1C35A0C3ADEF@Freenet.DE \
--to=peter_dyballa@freenet.de \
--cc=emacs-pretest-bug@gnu.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.
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).