mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Stefan Reinauer <stepan@coresystems.de>
Cc: barebox@lists.infradead.org
Subject: Re: barebox on x86
Date: Tue, 31 Aug 2010 19:08:14 +0200	[thread overview]
Message-ID: <20100831170814.GC22790@game.jcrosoft.org> (raw)
In-Reply-To: <4C7D26FF.2030706@coresystems.de>

On 17:59 Tue 31 Aug     , Stefan Reinauer wrote:
>  Hi Jean-Christophe,
> 
> On 8/31/10 5:18 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 15:50 Tue 31 Aug     , Stefan Reinauer wrote:
> >>  Hi Jean-Christophe,
> >>
> >> On 8/31/10 3:18 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >>> why do you touch it?
> >> Sorry, touch _what_ in particular?
> >>
> >>> barebox is self content so I do not understand why you do such modificaton
> >>> specially uf we are supposed to do crosscompile
> >>>
> >> Unfortunately that assumption is wrong, at least for the x86 target.
> >> Almost all my patch does is trying to fix exactly that (along with
> >> dropping the requirement to use Linux on the host side)
> >>
> >> And, yes, I am using an i386-elf- cross compiler.
> > you need a linux toolchains and it's build correctly
> 
> So, barebox needs glibc and a Linux kernel to build? Hm. Then consider
> my patch fixing that problem. Almost. With my patch it's self-content.
> But the linking problems are still open. Do you have any hint on those,
> too, maybe?
> 
> > I build it on MacOS too
> >
> How did you overcome the programs in scripts/ using Linux system headers
> that are not there with HOSTCC (even with a Linux cross toolchain)?
the tool chain provive it and it's the same for compiling the kernel on MacOS

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2010-08-31 17:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 10:25 Stefan Reinauer
2010-08-31 13:18 ` Jean-Christophe PLAGNIOL-VILLARD
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 [this message]
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=20100831170814.GC22790@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=stepan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox