From: Jeffrey Hawkins <Jeffrey.F.Hawkins@motorola.com>
To: Jeffrey Hawkins <Jeffrey_Hawkins-CJH016@email.mot.com>
Cc: Franz.Sirl-kernel@lauterbach.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: PPC Versions of Glibc and GCC Status
Date: Thu, 10 Aug 2000 13:24:00 -0500 [thread overview]
Message-ID: <3992F340.F9F6314B@motorola.com> (raw)
In-Reply-To: 3992EAE6.27CF4490@motorola.com
Franz,
I noticed after sending you the e-mail, that I addressed
you as Frank, rather than Franz. My apologies, I guess
I have Frank on the brain, since I work closely with a
Frank...
Jeff
Jeffrey Hawkins wrote:
>
> Frank,
>
> I am currently utilizing your current versions of GCC
> 2.95.3-2c and GLIB2.1.3-15d for my development. Thanks
> for all the hard work....
>
> I am experiencing a few issues with LinuxThreads, which upon
> querying the GNU developers/lists, I have found the issues
> may have been fixed in the 2.1.9x and 2.2-beta versions.
> The required fixes are in the LinuxThreads Library, as well
> as, in other Libraries.
>
> Are you currently integrating/migrating your
> 2.1.3 versions with 2.1.9x or 2.2.x ? If you are not
> planning on doing this, have the changes you have made,
> or the changes by other LinuxPPC Developers, both to the
> GCC and GLIBs, been submitted and incorporated in the GNU
> running changes ?
>
> I am just starting the process of going through the Source
> for 2.1.91 and checking the differences with the 2.1.3-15d.
> I am querying you on your efforts, and others, so that I don't
> waste time duplicating what has already been done. I was
> hoping to use GLIB 2.1.91 off the shelf, but I know this
> will probably not be the case.
>
> Any feedback, or tips on things to look out for (such as
> Libraries/Modules you had to make extensive updates to, #ifdefs
> and #defines that need to be added for PowerPC), would be
> appreciated. I will be making the Source Tarballs and RPMs
> available once I have completed this task.
>
> Jeff
>
> --
> ********************************************************
>
> Jeffrey Hawkins
>
> Senior Staff Software Engineer
> Motorola Wireless Data Solutions Engineering
>
> Address: DEPT: DQ525
> MS: IL-02-1055A
> 1301 East Algonquin Road
> Schaumburg, IL 60196
>
> Phone: (847)576-7463
> FAX: (847)576-7737
>
> ********************************************************
>
--
********************************************************
Jeffrey Hawkins
Senior Staff Software Engineer
Motorola Wireless Data Solutions Engineering
Address: DEPT: DQ525
MS: IL-02-1055A
1301 East Algonquin Road
Schaumburg, IL 60196
Phone: (847)576-7463
FAX: (847)576-7737
********************************************************
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-10 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-10 17:48 PPC Versions of Glibc and GCC Status Jeffrey Hawkins
2000-08-10 18:24 ` Jeffrey Hawkins [this message]
2000-08-10 19:51 ` Kevin B. Hendricks
2000-08-10 20:58 ` Jeffrey Hawkins
[not found] ` <v03110700b5b8cf9c9c55@[216.209.101.72]>
[not found] ` <39933FA2.F37E7897@motorola.com>
2000-08-11 1:57 ` Jeffrey Hawkins
2000-08-10 19:43 ` Kevin B. Hendricks
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=3992F340.F9F6314B@motorola.com \
--to=jeffrey.f.hawkins@motorola.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=Jeffrey_Hawkins-CJH016@email.mot.com \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).