From: Thorsten Glaser <tg@66h.42h.de>
Cc: gcc@gcc.gnu.org
Subject: Re: libjava/3.4.4 problem
Date: Sat, 30 Apr 2005 13:46:00 -0000 [thread overview]
Message-ID: <Pine.BSO.4.61L.0504301236440.13069@thor.66h.42h.de> (raw)
In-Reply-To: <fd1a4af45fd22f8eb8ebfbafd0dbc9b0@physics.uc.edu>
Andrew Pinski dixit:
>> Does anyone have an idea where to look?
>
> This is a bug in your config, you forgot to define NO_IMPLICIT_EXTERN_C.
Thanks a lot, I will try that after I updated to 20050429.
bye,
//mirabile
next prev parent reply other threads:[~2005-04-30 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 19:33 GCC 3.4.4 Status (2005-04-29) Mark Mitchell
2005-04-29 21:39 ` libjava/3.4.4 problem (was Re: GCC 3.4.4 Status (2005-04-29)) Thorsten Glaser
2005-04-29 22:24 ` Andrew Pinski
2005-04-30 13:46 ` Thorsten Glaser [this message]
2005-05-01 22:29 ` libjava/3.4.4 problem (SOLVED) Thorsten Glaser
2005-05-02 21:43 ` Tom Tromey
2005-04-29 21:40 ` GCC 3.4.4 Status (2005-04-29) Joseph S. Myers
2005-04-29 21:41 ` Mark Mitchell
2005-05-02 9:46 ` Richard Guenther
2005-05-02 14:26 ` Mark Mitchell
2005-05-02 14:46 ` Gabriel Dos Reis
2005-04-30 9:47 ` Gabriel Dos Reis
2005-05-06 3:11 ` Gary Funck
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=Pine.BSO.4.61L.0504301236440.13069@thor.66h.42h.de \
--to=tg@66h.42h.de \
--cc=gcc@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).