From: "Kevin B. Hendricks" <kevin.hendricks@sympatico.ca>
To: Joe Buck <Joe.Buck@synopsys.com>
Cc: shebs@apple.com, gcc@gcc.gnu.org
Subject: Re: Apple gcc 3.1 and OpenOffice.org
Date: Sat, 12 Oct 2002 09:19:00 -0000 [thread overview]
Message-ID: <200210111959.15538.kevin.hendricks@sympatico.ca> (raw)
In-Reply-To: <200210112331.QAA00321@atrus.synopsys.com>
Hi,
Unfortunately I am the co-lead of the OpenOffice.org porting project. I
was looking for help from someone familiar with gcc and specifically
Apple's gcc to help work around toolchain issues we are running into doing
the OpenOffice.org port and hopefully a tip as to where to look (what
list) for kernel bug reports as well).
Kevin
On October 11, 2002 07:31, Joe Buck wrote:
> > B. We seem to have run into two issues with OOo and gcc 3.1 in OSX
> > 10.2.
>
> You might have better luck asking around on one of OOo's mailing lists.
prev parent reply other threads:[~2002-10-12 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-11 12:05 Kevin B. Hendricks
2002-10-11 21:23 ` Joe Buck
2002-10-12 9:19 ` Kevin B. Hendricks [this message]
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=200210111959.15538.kevin.hendricks@sympatico.ca \
--to=kevin.hendricks@sympatico.ca \
--cc=Joe.Buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=shebs@apple.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).