This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/54663] microblaze-linux genchecksum failure: opening microblaze-c.o: No such file or directory
- From: "amylaar at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 23 Oct 2012 15:46:32 +0000
- Subject: [Bug target/54663] microblaze-linux genchecksum failure: opening microblaze-c.o: No such file or directory
- Auto-submitted: auto-generated
- References: <bug-54663-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54663
--- Comment #2 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2012-10-23 15:46:32 UTC ---
(In reply to comment #1)
> Not able to reproduce. GCC HEAD builds for microblaze without known problem.
Actually, using a freshly bootstrapped gcc, I run into PR55035.
I had to use a slighty older host compiler to get any farther.
Note, both microblaze-elf and microblaze-linux are affected by PR55035.
PR54663 affects microblaze-linux, but nor microblaze-elf.
> Not enough info in report to reproduce or identify problem.
>
> If there was a problem compiling microblaze-c.o, it would be logged before the
> ar to create libbackend.a.
This is with r192703. I am (or rather the contrib/config-list.mk makefile is)
trying to build a i686-pc-linux-gnu X microblaze-linux cross.
configured by ../../gcc/configure, generated by GNU Autoconf 2.64,
with options \" '--target=microblaze-linux' '--enable-werror-always'
'target_alias=microblaze-linux'
'--enable-languages=c,ada,c++,fortran,go,lto,objc'\"
The make target is "all-gcc" .
This is not so much a problem with compiling microblaze-c.o as rather the
lack of any attempt to do so.