public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Shinkan <shinkan@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Cross emerging to a given root.
Date: Thu, 3 Dec 2009 19:17:26 +0100	[thread overview]
Message-ID: <166af1cf0912031017w6ac9cfb8sa17f48c15d6f7cc9@mail.gmail.com> (raw)
In-Reply-To: <4B17ECB7.4000800@wildgooses.com>

[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]

2009/12/3 Ed W <lists@wildgooses.com>

> Shinkan wrote:
>
>>
>> I tested it and emerge failed on some ports because installing them use
>> binaries that complain about not finding required versions of "CXXABI" or so
>> in libstdc++.
>> What could I do to fix that ?
>>
>
>
> Are you sure emerge failed or that the binary failed to run on the new
> system?
>
> In the later case it's because certain lib files are part of GCC and hence
> won't be installed on your target - I find this on a few packages and I just
> copy across the relevant libs from the host system
>

lzma failed to run because of something it didn't like in libstdc++ from
/usr/lib/gcc/my-other-gcc-version/ or something like that.

It seems that retrying a gcc-config + env-update + source /etc/profile made
it pass.
I'm not exactly on the TinyGentoo case because I would prefer host to serves
as a build env instead of untaring another stage3.
As I have many various targets to build and maintain, it would be hard to
also maintain their respective build chroots.

Playing with different compilers on the host seems to do the trick.
For now I play with gcc-config on host every time I work with a target which
needs a different gcc, but that's much pain (what if I forget to gcc-config
back to my actual host gcc version ??! I'll lscrew my host I guess.)
I would really like if there was an option on make.conf to specify default
compiler. As each of my targets have its own make.conf and profile link, it
would be very comfortable if I could tell emerge to use the compiler
specified in make.conf, so that each time I'd cross-emerge, the good
compiler for my target would be selected.

Thanks a lot for your directions, TinyGentoo wiki page is really useful.

-- 
Pierre.
"Sometimes when I'm talking, my words can't keep up with my thoughts. I
wonder why we think faster than we speak. Probably so we can think twice." -
Bill Watterson

[-- Attachment #2: Type: text/html, Size: 2518 bytes --]

  reply	other threads:[~2009-12-03 20:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 17:46 [gentoo-embedded] Cross emerging to a given root Shinkan
2009-12-02 20:04 ` Peter Stuge
2009-12-03 14:21   ` Shinkan
2009-12-03 16:52     ` Ed W
2009-12-03 18:17       ` Shinkan [this message]
2009-12-03 23:23         ` Peter Stuge
2009-12-04  9:55         ` Ed W
2009-12-04 10:25           ` Peter Stuge
2009-12-03 23:19     ` Peter Stuge
2009-12-02 20:09 ` Ryan Tandy
2009-12-03 16:50   ` Ed W

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=166af1cf0912031017w6ac9cfb8sa17f48c15d6f7cc9@mail.gmail.com \
    --to=shinkan@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