Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: avahi dmalloc libdaemon mpatrol netplug
Date: Wed, 13 Dec 2006 05:15:03 -0700	[thread overview]
Message-ID: <20061213121503.GA32467@codepoet.org> (raw)
In-Reply-To: <20061213101700.GA13288@aon.at>

On Wed Dec 13, 2006 at 11:17:00AM +0100, Bernhard Fischer wrote:
> btw.. from the looks, i'll need to build the initial binutils with
> sysroot support to be able to build a libgmp to be used for the DIR2
> gcc (for 4.2 fortran that i want to play with) and 4.3. Mind if i
> make this change or should this be done differently?

Can't see why that would be a problem.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

      reply	other threads:[~2006-12-13 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13  9:04 [Buildroot] svn commit: trunk/buildroot/package: avahi dmalloc libdaemon mpatrol netplug aldot at uclibc.org
2006-12-13  9:23 ` Erik Andersen
2006-12-13 10:17   ` Bernhard Fischer
2006-12-13 12:15     ` Erik Andersen [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=20061213121503.GA32467@codepoet.org \
    --to=andersen@codepoet.org \
    --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