From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] omniorb: limit to glibc toolchains
Date: Tue, 16 Sep 2014 08:34:43 +0200 [thread overview]
Message-ID: <20140916083443.4264046e@free-electrons.com> (raw)
In-Reply-To: <CANQCQpYNfJ0Kk8iNdF_Uncsuse-UBtu_TZtkoNVR7y8J8m-j1Q@mail.gmail.com>
Dear Matthew Weber,
On Mon, 15 Sep 2014 20:07:47 -0500, Matthew Weber wrote:
> > Thank you for that clarification, that makes a bit more sense on why this
> > issue didn't come up as often in the autobuilds. I would assume that
> > updating this path to a needs MMU instead is the correct approach.
>
> I retested with a "depends on BR2_USE_MMU", which excluded that package
> from the bfin build.
Did you test whether the package builds with Blackfin FDPIC ?
Looking at the build error, it doesn't seem to be MMU or noMMU related.
> I had another question. Over the last couple weeks, I've created a couple
> patches that can be discarded. How do those get removed from patchworks?
Either the patch submitter does it (everyone can create an account on
patchwork and then manage his own patches), or some patchwork
administrator does it (I think Peter, Yann, Thomas DS, me, and maybe a
few other core developers are patchwork admins).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-09-16 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 14:17 [Buildroot] [PATCH 1/1] omniorb: limit to glibc toolchains Matt Weber
2014-09-15 18:06 ` Thomas Petazzoni
2014-09-15 18:30 ` Matthew Weber
2014-09-16 1:07 ` Matthew Weber
2014-09-16 6:34 ` Thomas Petazzoni [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=20140916083443.4264046e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox