From: Nicole <nicole@cats-muvva.net>
To: buildroot@busybox.net
Subject: [Buildroot] pppd patch
Date: Fri, 15 Jun 2012 10:38:48 +0100 [thread overview]
Message-ID: <4FDB02A8.1010509@cats-muvva.net> (raw)
Hi Thomas (I decided you weren't Italian after all),
The patch I had is obviated by building the resolv stub for uClib. If
you don't build these stubs, then libresolv is not available which halts
the build, even though all the symbols that the developer expected to be
resolved by that library have been resolved elsewhere by uClibc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2332 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120615/45166482/attachment.p7s>
reply other threads:[~2012-06-15 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FDB02A8.1010509@cats-muvva.net \
--to=nicole@cats-muvva.net \
--cc=buildroot@busybox.net \
/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