From: Per Jessen <per@computer.org>
To: "Darío Mariani" <mariani.dario@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: building libc
Date: Thu, 13 Dec 2007 08:31:58 +0100 [thread overview]
Message-ID: <4760DFEE.70903@computer.org> (raw)
In-Reply-To: <84bd26ef0712121743p77080df0t48a2e68443611337@mail.gmail.com>
Darío Mariani wrote:
> http://www.itworld.com/AppDev/1006/UIR000929interposers/pfindex.html.
>
Yeah, this is exactly what I intend to try. My problem is in
getaddrinfo() which has been misbehaving (for quite some time). The
glibc code was fixed by Ian Jackson in glibc 2.6.1 for ubuntu, so I
figured I'd just borrow that and stick the getaddrinfo() object-code
into a shared library which I'd preload with LD_PRELOAD. Sounds simple,
doesn't it?
Well, building the glibc code was no big deal, but as for "just borrow
that", it's not easy. If I build getaddrinfo.c outside the glibc build
structure, it throws about a million errors. Option #1 is to attempt to
fix that, but with getaddrinfo.c being about 2000 lines, I'm a little
hesitant about that approach.
Option #2 (I think) is to use the object-code from the built glibc, but
when I try to use the shared library (containing just getaddrinfo.o), it
complains about unresolved symbols - e.g. __inet_ntoa.
/Per Jessen
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-12-13 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 14:41 building libc Per Jessen
2007-12-12 20:15 ` Per Jessen
[not found] ` <84bd26ef0712121743p77080df0t48a2e68443611337@mail.gmail.com>
2007-12-13 1:44 ` Darío Mariani
2007-12-13 7:31 ` Per Jessen [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=4760DFEE.70903@computer.org \
--to=per@computer.org \
--cc=linux-c-programming@vger.kernel.org \
--cc=mariani.dario@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.