From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Available for test: gcc-3.1.1-3, gcc2-2.95.3-9, gcc-mingw-3_1-20020516-2
Date: Mon, 15 Jul 2002 23:05:00 -0000 [thread overview]
Message-ID: <20020716000536.GA31329@redhat.com> (raw)
In-Reply-To: <20020715220013.80671.qmail@web21003.mail.yahoo.com>
On Mon, Jul 15, 2002 at 03:00:13PM -0700, Nicholas Wourms wrote:
>Did you try the suggestions I made in:
>
>http://cygwin.com/ml/cygwin-apps/2002-07/msg00384.html
>
>to get libiconv working? Just curious to see if it helped.
No. If this isn't working then I wasn't looking for a workaround.
As it turns out, apparently only some parts of java used this. Those
are correctly linked with -liconv. The rest of the tool chain doesn't use
-lintl, though, since there are specific tests to invalidate this under
cross compilation.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-07-16 0:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 15:56 Christopher Faylor
2002-07-15 18:00 ` Nicholas Wourms
2002-07-15 23:05 ` Christopher Faylor [this message]
2002-07-16 1:47 ` Dylan Cuthbert
2002-07-17 3:51 ` Dylan Cuthbert
2002-07-17 7:08 ` Christopher Faylor
2002-07-17 7:55 ` Dylan Cuthbert
2002-07-17 10:12 ` Nicholas Wourms
2002-07-16 5:29 ` Pavel Tsekov
2002-07-16 6:57 ` Nicholas Wourms
2002-07-16 16:29 ` Christopher Faylor
2002-07-17 7:16 Billinghurst, David (CRTS)
2002-07-17 7:31 ` Robert Collins
2002-07-18 18:49 ` Christopher Faylor
2002-07-19 15:12 Available for test: gcc-3.1.1-3, gcc2-2.95.3-9, gcc-mingw-3_1 -20020516-2 Heribert Dahms
2002-07-20 1:10 ` Available for test: gcc-3.1.1-3, gcc2-2.95.3-9, gcc-mingw-3_1-20020516-2 Robert Collins
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=20020716000536.GA31329@redhat.com \
--to=cgf@redhat.com \
--cc=cygwin@cygwin.com \
/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).