Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] cris
Date: Mon, 23 Jun 2008 16:48:39 +0200	[thread overview]
Message-ID: <485FB7C7.2090908@cetrtapot.si> (raw)
In-Reply-To: <20080623130657.GC8920@mx.loc>

Bernhard Fischer wrote:
> On Mon, Jun 23, 2008 at 10:50:32AM +0200, Hinko Kocevar wrote:
>> Hinko Kocevar wrote:
>>> Bernhard Fischer wrote:
>>>> [I'm changing the subject to something more suitable]
> 
>>>> I don't see this. Is that uClibc-trunk or something else?
>>> Me too, will rebuild with and wo sysroot as I suspect to meka a difference..
>> No difference. In other words, I can't install binutils 2.18 wo using sysroot.
> 
> Ah right, i don't do non-sysroot (there is simply no point in it)
> anymore. It's better to just have a properly relocatable cross-compiler
> anyway.
> 
>> But using gcc 4.2.3 instead of 4.3.1 does not generate the error!
> 
> You would have to look if these old gcc versions are treated separately
> and adjust the new accordingly (in gcc-uclibc-3.x.mk, i.e. the
> non-sysroot makefile; but you really don't want these).
> 

I've misread the sysroot comment in the buildroot (I thought it was optionally to use it), but without it the buildroot tries to put resulting cross compiled binutils into /usr, which is not what I want.

Maybe finding the 'latest' known working compiler for cris would be the starting point and the move on to the newer versions. Axis has originally ported cris architecture to gcc 3.2.1 and I'm not aware if they are even trying to keep up with the gcc/glibc/uClibc/binutils mainstream changes in order to provide latest tools..

Thanks.

-- 
?ETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar at cetrtapot.si
Http: www.cetrtapot.si

  reply	other threads:[~2008-06-23 14:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 10:23 [Buildroot] GIT or SVN Hinko Kocevar
2008-06-19 10:53 ` Hinko Kocevar
2008-06-19 11:13   ` Bernhard Fischer
2008-06-19 11:54     ` Hinko Kocevar
2008-06-19 12:03       ` Bernhard Fischer
2008-06-19 12:20         ` Hinko Kocevar
2008-06-19 13:25         ` Hinko Kocevar
2008-06-19 19:09 ` Peter Korsgaard
2008-06-20  8:36   ` Bernhard Fischer
2008-06-20  8:40     ` Hinko Kocevar
2008-06-20 12:57       ` Bernhard Fischer
2008-06-20 13:15         ` Hinko Kocevar
2008-06-20 13:24           ` Bernhard Fischer
2008-06-23 10:10             ` Hinko Kocevar
2008-06-20 13:26         ` Hinko Kocevar
2008-06-20 14:11           ` [Buildroot] cris Bernhard Fischer
2008-06-20 14:30             ` Peter Korsgaard
2008-06-20 15:03               ` Bernhard Fischer
2008-06-23  7:27             ` Hinko Kocevar
2008-06-23  8:50               ` Hinko Kocevar
2008-06-23 13:06                 ` Bernhard Fischer
2008-06-23 14:48                   ` Hinko Kocevar [this message]
2008-06-23 13:03               ` Bernhard Fischer
2008-06-23 14:41                 ` Hinko Kocevar
2008-06-23 14:46                   ` Bernhard Fischer
2008-06-23 14:54                     ` Hinko Kocevar
2008-06-23 15:01                       ` Bernhard Fischer
2008-07-30  2:39                       ` Ralph Siemsen
2008-06-20 13:18       ` [Buildroot] GIT or SVN Peter Korsgaard
2008-07-30  8:20         ` Hinko Kocevar

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=485FB7C7.2090908@cetrtapot.si \
    --to=hinko.kocevar@cetrtapot.si \
    --cc=buildroot@busybox.net \
    /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