From: David Michel <dmichel76@googlemail.com>
To: java@gcc.gnu.org
Subject: Fwd: Using the newest Classapth with gcj ?
Date: Tue, 31 Mar 2009 18:38:00 -0000 [thread overview]
Message-ID: <b5bf7a380903311138n21543514nae311b27df4ac761@mail.gmail.com> (raw)
In-Reply-To: <b5bf7a380903311137i12ffbfadq814dd16da3bc372c@mail.gmail.com>
---------- Forwarded message ----------
From: David Michel <dmichel76@googlemail.com>
Date: 2009/3/31
Subject: Re: Using the newest Classapth with gcj ?
To: Andrew Haley <aph@redhat.com>
well line 54-55 of /usr/include/limits.h obviously
2009/3/31 Andrew Haley <aph@redhat.com>:
> David Michel wrote:
>> well it is there at line 54-55
>>
>> /* Number of bits in a `char'. */
>> # define CHAR_BIT 8
>>
>
> Line 54-55 of what? As I said, CHAR_BIT should be defined in
> /usr/include/limits.h.
>
> If it isn't there is something seriously wrong with the system you're
> trying to build on.
>
> Andrew.
>
next prev parent reply other threads:[~2009-03-31 18:38 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
2009-03-31 17:11 ` Andrew Haley
[not found] ` <b5bf7a380903311137i12ffbfadq814dd16da3bc372c@mail.gmail.com>
2009-03-31 18:38 ` David Michel [this message]
[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=b5bf7a380903311138n21543514nae311b27df4ac761@mail.gmail.com \
--to=dmichel76@googlemail.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).