From: "Yann E. MORIN" <yann.morin.1998@orange.fr>
To: crossgcc@sourceware.org
Cc: Ralf Jahr <ralf.jahr@informatik.uni-augsburg.de>
Subject: Re: Crash compiling binutils for alpha
Date: Wed, 04 Jan 2012 10:57:00 -0000 [thread overview]
Message-ID: <201201041156.52220.yann.morin.1998@orange.fr> (raw)
In-Reply-To: <4F042A7F.7080303@informatik.uni-augsburg.de>
Ralf, All,
On Wednesday 04 January 2012 11:31:27 Ralf Jahr wrote:
> The process stops when after starting with the binutils (see end of this
> email). I uploaded my config file and the log file here:
> http//88.80.200.38/cross.tar.gz
>
> I was not able to find something plausible from the log file. Changing
> the binutils version and GCC version did not help. I also checked the
> "known issues" but was not able to find something helping.
>
> What could I do to get things running?
>
> Thanks for any help,
>
> Ralf
>
>
> ralf@debian:~/gem5sim/tc$ ct-ng build
> [INFO ] Performing some trivial sanity checks
> [INFO ] Build started 20120104.105034
> [INFO ] Building environment variables
> [INFO ] =================================================================
> [...]
> =================================================================
> [INFO ] Installing CLooG/ppl
> [INFO ] Installing CLooG/ppl: done in 36.00s (at 18:51)
> [INFO ] =================================================================
> [INFO ] Installing binutils
> [ERROR] make[2]: *** [configure-ld] Error 1
> [ERROR] make[1]: *** [all] Error 2
> [ERROR]
> [ERROR] >>
> [ERROR] >> Error happened in: main[scripts/crosstool-NG.sh]
> [ERROR] >>
> [ERROR] >> For more info on this error, look at the file: 'build.log'
> [ERROR] >> There is a list of known issues, some with workarounds, in:
> [ERROR] >>
> '/home/ralf/gem5sim/crosstool-ng/bin//share/doc/ct-ng-1.13.2/B - Known
> issues.txt'
> [ERROR]
> [ERROR] Build failed in step 'Extracting and patching toolchain
> components'
> [ERROR]
> [ERROR] (elapsed: 19:59.62)
> [20:01] / make: *** [build] Fehler 2
I've seen this in the logs:
[ALL ] *** ld does not support target alphaev5-unknown-elf
[ALL ] *** see ld/configure.tgt for supported targets
[ERROR] make[2]: *** [configure-ld] Error 1
I am not sure it is possible to build a bare-metal compiler for Alpha...
Someone more knowledgeable than I in Alpha could probably help you more...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ |
| --==< O_o >==-- '------------.-------: X AGAINST | /e\ There is no |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. |
'------------------------------'-------'------------------'--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-01-04 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 10:31 Ralf Jahr
2012-01-04 10:57 ` Yann E. MORIN [this message]
2012-01-04 15:41 ` Ralf Jahr
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=201201041156.52220.yann.morin.1998@orange.fr \
--to=yann.morin.1998@orange.fr \
--cc=crossgcc@sourceware.org \
--cc=ralf.jahr@informatik.uni-augsburg.de \
/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).