From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] cris
Date: Mon, 23 Jun 2008 10:50:32 +0200 [thread overview]
Message-ID: <485F63D8.2050809@cetrtapot.si> (raw)
In-Reply-To: <485F507D.5070801@cetrtapot.si>
Hinko Kocevar wrote:
> Bernhard Fischer wrote:
>> [I'm changing the subject to something more suitable]
>> On Fri, Jun 20, 2008 at 03:26:16PM +0200, Hinko Kocevar wrote:
>>> Bernhard Fischer wrote:
>>>> On Fri, Jun 20, 2008 at 10:40:22AM +0200, Hinko Kocevar wrote:
>>>>
>>>>> With gcc 4.3.1 gcc internal errors went away, so I'm really glad I found the GIT tree!
>>>> I have improved (i hope) the cris support, configuration-wise, please
>>>> pull and let me know if it suits your needs.
>>>>
>>> 1. Compilation of uClibc always fails with:
>>>
>>> make[1]: Entering directory `/work/stage/git.br/toolchain_build_cris/uClibc-0.9.29'
>>> make[2]: `conf' is up to date.
>>> /usr/bin/make locale_headers
>>> make[3]: `conf' is up to date.
>>> CC ldso/ldso/ldso.oS
>>> AS ldso/ldso/cris/resolve.oS
>>> CC ldso/libdl/libdl.oS
>>> CC libcrypt/crypt.os
>>> CC libcrypt/des.os
>>> In file included from ./include/sys/param.h:22,
>>> from libcrypt/des.c:62:
>>> ./include/limits.h:124:26: error: limits.h: No such file or directory
>>> make[1]: *** [libcrypt/des.os] Error 1
>>> make[1]: *** Waiting for unfinished jobs....
>>> make[1]: Leaving directory `/work/stage/git.br/toolchain_build_cris/uClibc-0.9.29'
>>> make: *** [/home/hinkok/work/stage/git.br/toolchain_build_cris/uClibc-0.9.29/lib/libc.a] Error 2
>> 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.
But using gcc 4.2.3 instead of 4.3.1 does not generate the error!
--
?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
next prev parent reply other threads:[~2008-06-23 8:50 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 [this message]
2008-06-23 13:06 ` Bernhard Fischer
2008-06-23 14:48 ` Hinko Kocevar
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=485F63D8.2050809@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