From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Stefan Reinauer <stefan.reinauer@coresystems.de>
Cc: barebox@lists.infradead.org
Subject: Re: barebox on x86
Date: Tue, 31 Aug 2010 15:18:17 +0200 [thread overview]
Message-ID: <20100831131817.GA1883@game.jcrosoft.org> (raw)
In-Reply-To: <4C7CD898.9040902@coresystems.de>
On 12:25 Tue 31 Aug , Stefan Reinauer wrote:
> Hi,
>
> here's some initial work on getting barebox working on x86 (again?).
>
> The patch is very ugly, and it makes some assumptions on me using
> Darwin/Mac OS X to compile barebox.
> What kind of becomes clear though, is that there is no clear distinction
> between which set of headers are used for the user space utilities and
> which set of headers are used for the barebox binary. I think that's the
> reason why barebox features an include/linux directory which seems to
> duplicate about half of what Linux usually has in there, but more than
> barebox uses (or should use, ftm).
>
> With the attached patch I get as far as the linking stage.
why do you touch it?
barebox is self content so I do not understand why you do such modificaton
specially uf we are supposed to do crosscompile
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-08-31 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 10:25 barebox on x86 Stefan Reinauer
2010-08-31 13:18 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-08-31 13:50 ` Stefan Reinauer
2010-08-31 15:18 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-31 15:59 ` Stefan Reinauer
2010-08-31 16:23 ` Juergen Beisert
2010-08-31 17:08 ` Jean-Christophe PLAGNIOL-VILLARD
2010-08-31 19:06 ` Stefan Reinauer
2010-08-31 15:45 ` Juergen Beisert
2010-08-31 19:09 ` Stefan Reinauer
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=20100831131817.GA1883@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=stefan.reinauer@coresystems.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 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.