From: Filipp Andjelo <Filipp.Andjelo@tomtom.com>
To: Carsten Schoenert <c.schoenert@gmail.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Relocatable toolchain
Date: Mon, 17 Jun 2013 21:02:00 -0000 [thread overview]
Message-ID: <51BF79A9.5070108@tomtom.com> (raw)
In-Reply-To: <51BF5508.20605@googlemail.com>
Hello Carsten,
On 17.06.2013 20:27, Carsten Schoenert wrote:
> Hello Filipp,
>
> Am 17.06.2013 20:15, schrieb Filipp Andjelo:
>> Hi Thomas,
>>
>> I didn't set anything special, I think. I think, there has to be some
>> setting I'm missing. Which settings do you have according sysroot?
>> And if you call cross-gcc with --print-sysroot, do you get relative or
>> absolute path? I get absolute path to the location I've used to
>> build the toolchain....
> It would be easier if you can show us your crosstool-ng config. :)
>
> And please, don't do top-posting.
>
> Regards
> Carsten
first, sorry for the top-posting, didn't realize this rule here. I've
just taken one of the sample configurations and rebuild my toolchain
from it. Now it seems to work properly, I mean it is relocatable now. I
have to diff the two configs now to understand the problem. First
important difference is gcc 4.5.2 vs 4.4.7 and binutils 2.21a vs 2.22.
Everything else shouldn't make difference... but I'll look more closely
tomorrow...
Cheers,
Filipp
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2013-06-17 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 14:40 Filipp Andjelo
2013-06-17 14:53 ` Thomas Petazzoni
2013-06-17 18:15 ` Filipp Andjelo
2013-06-17 18:27 ` Carsten Schoenert
2013-06-17 21:02 ` Filipp Andjelo [this message]
2013-06-17 22:36 ` Yann E. MORIN
2013-06-19 8:14 ` Filipp Andjelo
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=51BF79A9.5070108@tomtom.com \
--to=filipp.andjelo@tomtom.com \
--cc=c.schoenert@gmail.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).