From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] bf537-stamp board compilation problem
Date: Fri, 23 Apr 2010 15:33:57 -0400 [thread overview]
Message-ID: <201004231533.58136.vapier@gentoo.org> (raw)
In-Reply-To: <20100423193009.36A7819F60@gemini.denx.de>
On Friday 23 April 2010 15:30:09 Wolfgang Denk wrote:
> Mike Frysinger wrote:
> > because the post/ dir has historically been ppc-only (literally sprinkled
> > with code that would not compile for any other arch), we were filtering
> > post/ out in the top level Makefile for Blackfin targets.
> > ifneq ($(ARCH),blackfin)
> > LIBS += post/libpost.a
> > endif
>
> I'd rather have seen fixes for any such problems.
like i already said, we had plans to de-suckify post/, but never got around to
it. what you're asking for isnt trivial, nor were we seeing the demand for
it. i could just as easily say "i'd rather the code didnt assume powerpc
everywhere", but it isnt like that gets us from point a to point b.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100423/78a210e1/attachment.pgp
next prev parent reply other threads:[~2010-04-23 19:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 14:10 [U-Boot] bf537-stamp board compilation problem Michael Zaidman
2010-04-23 14:56 ` Mike Frysinger
2010-04-23 15:21 ` Michael Zaidman
2010-04-23 15:37 ` Mike Frysinger
2010-04-23 16:31 ` Michael Zaidman
2010-04-23 16:45 ` Mike Frysinger
2010-04-23 19:30 ` Wolfgang Denk
2010-04-23 19:33 ` Mike Frysinger [this message]
2010-04-23 19:44 ` Wolfgang Denk
2010-04-24 17:53 ` Michael Zaidman
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=201004231533.58136.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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