From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Guan Xuetao <gxt@mprc.pku.edu.cn>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [Suggestion] unicore32: About toolchain issues and source code.
Date: Wed, 30 Apr 2014 09:14:42 +0800 [thread overview]
Message-ID: <53604E82.1040407@gmail.com> (raw)
Hello Maintainers:
Excuse me, I did not find our unicore32 toolchains source code (I got
binary to cross-compile Linux kernel), could you provide more related
information for it, thanks.
And I find 2 unicore32 toolchains issues, please help check.
- Gas issue:
AS firmware/keyspan/usa18x.fw.gen.o
firmware/keyspan/usa18x.fw.gen.S: Assembler messages:
firmware/keyspan/usa18x.fw.gen.S:11: Error: junk at end of line, first unrecognized character is `,'
make[1]: *** [firmware/keyspan/usa18x.fw.gen.o] Error 1
make: *** [firmware] Error 2
it is about statement ".section .builtin_fw,"a",@progbits".
- The statement is correct and standard.
- Use "aM" instead of "a", can pass compiling, but shouldn't do it.
- Remove "@progbits", can pass compiling, but shouldn't do it.
- Compiler issue:
CC [M] drivers/media/dvb-frontends/tda10048.o
drivers/media/dvb-frontends/tda10048.c: In function ‘tda10048_set_wref’:
drivers/media/dvb-frontends/tda10048.c:367: internal compiler error: in simplify_const_unary_operation, at simplify-rtx.c:1278
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[3]: *** [drivers/media/dvb-frontends/tda10048.o] Error 1
make[2]: *** [drivers/media/dvb-frontends] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2
- Toolchain information:
root@gchen:/upstream/toolchain/binutils/gas# /upstream/toolchain/unicore32/pi3dian14-beyondmind/prebuilt/linux-x86/toolchain/uc4-1.0-beta-hard-RHELAS4/bin/unicore32-linux-gcc -v
Using built-in specs.
Target: unicore32-linux
Configured with: /home/ghb/trunk/gcc-4.4.2/configure --target=unicore32-linux --prefix=/usr/unicore/gnu-toolchain-unicore/uc4-1.0-beta-hard-RHELAS4 --enable-clocale=gnu --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-languages=c,c++,fortran --disable-multilib --disable-libstdcxx-pch --with-headers=/usr/unicore/gnu-toolchain-unicore/uc4-1.0-beta-hard-RHELAS4/unicore32-linux/include --with-pkgversion=UC4_1.0-beta_20100415
Thread model: posix
gcc version 4.4.2 (UC4_1.0-beta_20100415)
root@gchen:/upstream/toolchain/binutils/gas# /upstream/toolchain/unicore32/pi3dian14-beyondmind/prebuilt/linux-x86/toolchain/uc4-1.0-beta-hard-RHELAS4/bin/unicore32-linux-as -v
GNU assembler version 2.19.1 (unicore32-linux) using BFD version (GNU Binutils) 2.19.1
Next, I shall continue for unicore32 allmodconfig (hope I can finish
within 2014-05-31). And we may find other toolchain issues during cross
compiling (I shall report and try to solve them, after get source code).
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next reply other threads:[~2014-04-30 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 1:14 Chen Gang [this message]
2014-04-30 18:48 ` [Suggestion] unicore32: About toolchain issues and source code Guenter Roeck
2014-05-01 4:05 ` Chen Gang
2014-05-07 9:45 ` 管雪涛
2014-05-08 1:05 ` Chen Gang
2014-05-01 12:31 ` GUAN, Xuetao
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=53604E82.1040407@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.