All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Somerville <bill.3@classdesign.com>
To: buildroot@busybox.net
Subject: [Buildroot] glibc vs. uclibc
Date: Mon, 28 Aug 2006 18:51:22 +0100	[thread overview]
Message-ID: <1156787482.30424.16.camel@wallace.classdesign.local> (raw)

Hi

I am forced to use glibc by a closed source package from Intel (IPP) so
I am having to use a rather dated patch from the crosstool project to
hack with the buildroot package. This is very unsatisfactory as the
patch only applies cleanly to a very old revision of buildroot.

Is there fresher way of using buildroot with glibc?

--
Bill Somerville

             reply	other threads:[~2006-08-28 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 17:51 Bill Somerville [this message]
2006-08-30 16:55 ` [Buildroot] glibc vs. uclibc Rob Landley

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=1156787482.30424.16.camel@wallace.classdesign.local \
    --to=bill.3@classdesign.com \
    --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 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.