From: David Michel <dmichel76@googlemail.com>
To: Andrew Haley <aph@redhat.com>
Cc: java@gcc.gnu.org
Subject: Re: Using the newest Classapth with gcj ?
Date: Tue, 31 Mar 2009 16:55:00 -0000 [thread overview]
Message-ID: <b5bf7a380903310955v4320bd6fubd00d91786c9b20e@mail.gmail.com> (raw)
In-Reply-To: <49D2325A.5060904@redhat.com>
well it is there at line 54-55
/* Number of bits in a `char'. */
# define CHAR_BIT 8
David
2009/3/31 Andrew Haley <aph@redhat.com>:
> David Michel wrote:
>> Yes of course, flex wasn't installed when I first run configure. Now
>> it passes this point ok, but still fails later on with this:
>>
>> gcc -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings
>> -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual
>> -Wold-style-definition -Wc++-compat -Wmissing-format-attribute
>> -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
>> -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -o build/genrecog \
>> build/genrecog.o build/rtl.o build/read-rtl.o build/ggc-none.o
>> build/vec.o build/min-insn-modes.o build/gensupport.o
>> build/print-rtl.o build/errors.o
>> ../build-i686-pc-linux-gnu/libiberty/libiberty.a
>> build/genrecog /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/config/i386/i386.md
>> \
>> insn-conditions.md > tmp-recog.c
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/config/i386/i386.md:19820:
>> warning: operand 1 missing mode?
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/config/i386/i386.md:19861:
>> warning: operand 1 missing mode?
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/config/i386/i386.md:19878:
>> warning: operand 1 missing mode?
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/config/i386/sse.md:11556:
>> warning: operand 1 missing mode?
>> /bin/bash /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../move-if-change
>> tmp-recog.c insn-recog.c
>> echo timestamp > s-recog
>> lsf=""; for f in $lsf; do \
>> echo "#include \"$f\""; \
>> done | sed 's|/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/||'
>>> tmp-specs.h
>> /bin/bash /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../move-if-change
>> tmp-specs.h specs.h
>> echo timestamp > s-specs
>> gcc -c -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings
>> -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual
>> -Wold-style-definition -Wc++-compat -Wmissing-format-attribute
>> -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
>> -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/build
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../include
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../libcpp/include
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../libdecnumber
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../libdecnumber/bid
>> -I../libdecnumber -o build/gcov-iov.o
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/gcov-iov.c
>> gcc -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings
>> -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual
>> -Wold-style-definition -Wc++-compat -Wmissing-format-attribute
>> -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
>> -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE build/gcov-iov.o -o
>> build/gcov-iov
>> build/gcov-iov '4.4.0' 'prerelease' \
>> > tmp-gcov-iov.h
>> /bin/bash /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../move-if-change
>> tmp-gcov-iov.h gcov-iov.h
>> echo timestamp > s-iov
>> gcc -c -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings
>> -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual
>> -Wold-style-definition -Wc++-compat -Wmissing-format-attribute
>> -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
>> -fno-common -DHAVE_CONFIG_H -I. -I.
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/.
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../include
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../libcpp/include
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../libdecnumber
>> -I/home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../libdecnumber/bid
>> -I../libdecnumber
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/c-lang.c
>> -o c-lang.o
>> In file included from
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/input.h:25,
>> from
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/tree.h:27,
>> from
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/c-lang.c:27:
>> /home/micd/gcc-4_4-branch/obj-x86_64-unknown-linux-gnu/../gcc/../libcpp/include/line-map.h:66:
>> error: ‘CHAR_BIT’ undeclared here (not in a function)
>
> CHAR_BIT should be in /usr/include/limits.h.
>
> Andrew.
>
next prev parent reply other threads:[~2009-03-31 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 12:54 David Michel
2009-03-30 18:32 ` Andrew Haley
2009-03-31 11:23 ` David Michel
2009-03-31 14:33 ` Andrew Haley
2009-03-31 14:55 ` David Michel
2009-03-31 15:10 ` Andrew Haley
2009-03-31 16:55 ` David Michel [this message]
2009-03-31 17:11 ` Andrew Haley
[not found] ` <b5bf7a380903311137i12ffbfadq814dd16da3bc372c@mail.gmail.com>
2009-03-31 18:38 ` Fwd: " David Michel
[not found] ` <49D26B07.7000909@redhat.com>
[not found] ` <b5bf7a380903311330w4cfb10d2o506d0f08195cfd82@mail.gmail.com>
2009-03-31 20:30 ` David Michel
2009-03-31 20:40 ` David Daney
2009-03-31 20:44 ` David Michel
[not found] ` <49D32A91.3050202@redhat.com>
[not found] ` <b5bf7a380904020943l335e0f75kd6c5071af739441@mail.gmail.com>
2009-04-02 16:45 ` David Michel
2009-04-02 16:50 ` Andrew Haley
2009-04-03 8:45 ` David Michel
2009-04-03 9:21 ` David Michel
2009-04-03 9:35 ` Andrew Haley
2009-04-03 9:41 ` David Michel
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=b5bf7a380903310955v4320bd6fubd00d91786c9b20e@mail.gmail.com \
--to=dmichel76@googlemail.com \
--cc=aph@redhat.com \
--cc=java@gcc.gnu.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 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).