public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sergey Mironov <ierton@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] one cross-toolchain, many filesystem trees.
Date: Sun, 27 Mar 2011 12:47:12 +0400	[thread overview]
Message-ID: <AANLkTimnRFjyHC0Tk5xxwmG_VNGP8WSG3HyG3wBShBNk@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinr_zr9DakkL7z6Ez2TCdWv5+HcTqOVLX6vrSv8@mail.gmail.com>

2011/3/23 Mike Frysinger <vapier@gentoo.org>:
> On Wed, Mar 23, 2011 at 8:50 AM, Sergey Mironov wrote:
>> Hi. I'm planning to build 3 ARM filesystem trees. Since they differs
>> only in softfloat and mach flags in their /etc/make.conf, I don't want
>> to maintain 3 equal cross-build environments. Thats why I'm thinking
>> about building only one and than making 2 additional emerge wrappers,
>> which will set right SYSROOT and call original emerge wrapper. Is it
>> generally sufficient to make things work?
>
> "only" !?  the two pieces you speak of are core to the code generated.
>  you'll need sep trees for each FPU target, and for each CPU class.
> you could pick the lowest common denominator across the targets march
> wise and build for that, but that's no fun.
> -mike
>

I'm sorry, looks like I mentioned wrong 2 pieces. By softfloat I mean gcc flag
-msoftfp and there should be -mcpu, not -mach. Basically, my 3 systems are based
on
1) arm1136
2) arm1176jzf with CFLAGS+=-softfp
3) arm1176jzf without using FPU
I think they could be built with same cross-toolchain.

Sergey



      reply	other threads:[~2011-03-27  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23 12:50 [gentoo-embedded] one cross-toolchain, many filesystem trees Sergey Mironov
2011-03-23 14:50 ` Mike Frysinger
2011-03-27  8:47   ` Sergey Mironov [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=AANLkTimnRFjyHC0Tk5xxwmG_VNGP8WSG3HyG3wBShBNk@mail.gmail.com \
    --to=ierton@gmail.com \
    --cc=gentoo-embedded@lists.gentoo.org \
    /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