From: "m mariga" <ma_ariga@yahoo.co.jp>
To: "John Dallaway" <john@dallaway.org.uk>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: h8300 cannot find libgcc.a
Date: Tue, 28 Jul 2009 14:40:00 -0000 [thread overview]
Message-ID: <E6A66DCA0038483BAC5493029EF4A913@masahiro> (raw)
In-Reply-To: <4A6971F2.1030100@dallaway.org.uk>
[-- Attachment #1: Type: text/plain, Size: 4145 bytes --]
Hello,John,and everybody,
I am sorry to inform you that I could not succeed to configure GCC4.4.0 to
install h8300 toolchain.
I omitted TARGET_MODE define sentence,and converted GCC4.4.0 source as I
previously said.
I succeeded binutils configure.
But when I configured gcc, next error happened.
--- error begin
/tmp/build/build_gcc/./gcc/xgcc -B/tmp/build/build_gcc/./gcc/ -nostdinc -B/tmp/build/build_gcc/h8300-elf/newlib/
-isyste
m /tmp/build/build_gcc/h8300-elf/newlib/targ-include -isystem
/src/gcc-4.4.0/newlib/libc/include -B/gnutools/h8300-elf/b
in/ -B/gnutools/h8300-elf/lib/ -isystem /gnutools/h8300-elf/include -isystem
/gnutools/h8300-elf/sys-include -g -O2 -mh
-O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -Wca
st-qual -Wold-style-definition -isystem
./include -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I.
-
I../../.././gcc -I/src/gcc-4.4.0/libgcc -I/src/gcc-4.4.0/libgcc/. -I/src/gcc-4.4.0/libgcc/../gcc
-I/src/gcc-4.4.0/libgcc
/../include -DHAVE_CC_TLS -o _bswapsi2.o -MT _bswapsi2.o -MD -MP -MF
_bswapsi2.dep -DL_bswapsi2 -c /src/gcc-4.4.0/libgc
c/../gcc/libgcc2.c \
/tmp/build/build_gcc/./gcc/xgcc -B/tmp/build/build_gcc/./gcc/ -nostdinc -B/tmp/build/build_gcc/h8300-elf/newlib/
-isyste
m /tmp/build/build_gcc/h8300-elf/newlib/targ-include -isystem
/src/gcc-4.4.0/newlib/libc/include -B/gnutools/h8300-elf/b
in/ -B/gnutools/h8300-elf/lib/ -isystem /gnutools/h8300-elf/include -isystem
/gnutools/h8300-elf/sys-include -g -O2 -mh
-O2 -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -Wca
st-qual -Wold-style-definition -isystem
./include -g -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I.
-
I../../.././gcc -I/src/gcc-4.4.0/libgcc -I/src/gcc-4.4.0/libgcc/. -I/src/gcc-4.4.0/libgcc/../gcc
-I/src/gcc-4.4.0/libgcc
/../include -DHAVE_CC_TLS -o _bswapdi2.o -MT _bswapdi2.o -MD -MP -MF
_bswapdi2.dep -DL_bswapdi2 -c /src/gcc-4.4.0/libgc
c/../gcc/libgcc2.c \
/src/gcc-4.4.0/libgcc/../gcc/libgcc2.c:503: error: expected '=', ',', ';',
'asm' or '__attribute__' before '__bswapdi2'
/src/gcc-4.4.0/libgcc/../gcc/libgcc2.c:505:19: warning: integer constant is
too large for its type
/src/gcc-4.4.0/libgcc/../gcc/libgcc2.c:506:14: warning: integer constant is
too large for its type
/src/gcc-4.4.0/libgcc/../gcc/libgcc2.c:507:14: warning: integer constant is
too large for its type
/src/gcc-4.4.0/libgcc/../gcc/libgcc2.c:508:14: warning: integer constant is
too large for its type
make[4]: *** [_bswapdi2.o] Error 1
make[4]: Leaving directory `/tmp/build/build_gcc/h8300-elf/h8300h/libgcc'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/tmp/build/build_gcc/h8300-elf/libgcc'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/tmp/build/build_gcc/h8300-elf/libgcc'
make[1]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory `/tmp/build/build_gcc'
make: *** [all] Error 2
make: Leaving directory `/tmp/build/build_gcc'
--- error end
Here are 501-503 lines of libgcc2.c.
#ifdef L_bswapdi2
DItype
__bswapdi2 (DItype u)
Error is caused by not understanding DItype.
Since when I retrieved original gcc4.4.0 sources then not occurred above
error,
so I am sure I wrongly converted gcc4.4.0 four files.
I am very sorry to bother you,but I do not understand.
I append original and after-converted four files in compressed form.
I appended gcc3.3.2 original h8300.h,t-h8300.
patch-sources/gcc3.3.2-before-patch-sources/h8300.h,t-h8300
And after-patch-applied gcc3.3.2 four files.
patch-sources/gcc3.3.2-after-patch-sources/h8300.h,t-h8300,extfloatlib.c,float-h8300.h
And gcc4.4.0 original h8300.h,t-h8300.
patch-sources\gcc4.4.0-original-sources/h8300.h,t-h8300
And after-converted gcc4.4.0 four files according to patch.
patch-sources/gcc4.4.0-patch-converted-sources/h8300.h,t-h8300,extfloatlib.c,float-h8300.h
I beseech you to look up wrongfully converted codes in after-converted
gcc4.4.0 four files.
Would you please let me know the error-causing codes.
I am very much obliged.
m mariga
[-- Attachment #2: patch-sources.tar.bz2 --]
[-- Type: application/octet-stream, Size: 27613 bytes --]
[-- Attachment #3: Type: text/plain, Size: 148 bytes --]
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-07-28 14:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 14:08 [ECOS] " m mariga
2009-07-21 15:04 ` [ECOS] " John Dallaway
2009-07-22 12:28 ` m mariga
2009-07-22 13:58 ` John Dallaway
2009-07-23 21:32 ` m mariga
2009-07-24 8:34 ` John Dallaway
2009-07-28 14:40 ` m mariga [this message]
2009-08-09 23:11 ` m mariga
2009-08-17 7:42 ` John Dallaway
2009-09-04 5:54 ` [ECOS] How to set GDB Stub Options in order to run insight ? m mariga
2009-09-04 9:38 ` [ECOS] " John Dallaway
2009-09-04 18:33 ` m mariga
2009-09-07 9:40 ` m mariga
2009-09-07 11:31 ` John Dallaway
2009-09-07 16:10 ` [ECOS] cyg_scheduler_lock and DSR's Jim Bradleigh
2009-09-11 20:37 ` Bart Veer
2009-09-08 10:15 ` [ECOS] Re: How to set GDB Stub Options in order to run insight ? m mariga
2009-09-28 9:54 ` [ECOS] About h8000 eCos GDB-Stub m mariga
2009-09-30 10:06 ` m mariga
2009-10-16 14:34 ` [ECOS] How to connect RedBoot via Telnet running application m mariga
2009-10-16 14:42 ` Gary Thomas
[not found] ` <6FC88324D6C144EFB39FFE3CBF0E5B8D@masahiro>
2009-10-16 15:40 ` Gary Thomas
2009-10-16 16:11 ` m mariga
2009-10-16 16:43 ` m mariga
2009-10-16 16:54 ` Gary Thomas
2009-09-19 1:51 ` [ECOS] Re: How to set GDB Stub Options in order to run insight ? m mariga
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=E6A66DCA0038483BAC5493029EF4A913@masahiro \
--to=ma_ariga@yahoo.co.jp \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).