From: Paolo Supino <vrkid@yahoo.com>
To: gcc-help@gcc.gnu.org
Subject: building gcc 3.2.3 on FreeBSD 4.10
Date: Wed, 01 Dec 2004 14:56:00 -0000 [thread overview]
Message-ID: <20041201145614.46707.qmail@web60609.mail.yahoo.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 863 bytes --]
Hi
I've been given the asignment of building GCC 3.2.3 on FreeBSD 4.10.
It should have been a straight through process (I used --prefix=/port
--enable-shared --enable-thread=posix), but I've run into a problem
that GCC is built without WCHAR support (and it is required). I've read
the FAQ and read the thread it points out. I tried to do the manual
steps mentioned in the thread, but than GCC fails to build. I tried to
adapt the patch mentioned there as well, but the patch fails at a
certain point and I didn't find a way to make it work (didn't finish
writing the email with the full description of what I did).
Anyone has any suggestions on what I need to do to successfully build
GCC with WCHAR support?
Paolo
__________________________________
Do you Yahoo!?
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com
reply other threads:[~2004-12-01 14:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041201145614.46707.qmail@web60609.mail.yahoo.com \
--to=vrkid@yahoo.com \
--cc=gcc-help@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).