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
********************************************************
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
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/
From: Kevin B. Hendricks <hidden> Date: 2000-08-10 19:43:04
Hi,
There is a mutex bug in the glibc 15d rpms that Blackdown found and sent to
the libc-alpha list. It prevented linuxthread 15c and 15d rpms from
working correctly. Please try with Franz's glibc-2.1.3-5a rpms, they work
fine for the jdk. I will pass the patch along to Franz and hopefully there
will be a 15e rpm set out that should work fine for you (it does for the
JDK anyway).
I have attached the patch which you can use to make your own 15e rpm until
Franz gets a chance.
Hope this helps.
Kevin
RCS file: /cvs/glibc/libc/linuxthreads/mutex.c,v
retrieving revision 1.9.2.4
diff -u -r1.9.2.4 mutex.c
From: Kevin B. Hendricks <hidden> Date: 2000-08-10 19:51:28
Hi,
In case you were wondering, that patch has now (just today) been officially
added to the glibc 2.1 branch of the official glibc cvs tree. The patch in
question prevents a race in setting the onwer to null on a mutex that
resulting in tests in condvar.c to fail about the owner of the mutex not
being the same as the caller of the thread (when it actually was).
With this in place, the JDK native threads now seem to work well.
Please let me know if this sodesn't fix your problems (I am always
interested in the linuxthreads library when tracking down jdk failures).
Thanks,
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Kevin,
Thanks for the update...
However, my Thread Problem is not related to the recent fixes
discussed on the LinuxPPC List. The Thread Problem I am having
is that when a Child Process attempts to create a Thread, the
Thread is created and executes, but the Child Process hangs in
the "pthread_create" (NOTE: Only the Child Process is creating
threads, not the Main Application Parent). I don't really like
how this Application Package functions, but I don't have much
choice, since it is a 3rd Party Application Package that we
are using, that I am porting from AIX to LinuxPPC. I have
modified this first Application executable to be
a single process with multiple threads - Everything works.
But, there are several other executables that have the
same Child Process with Threads Architecture, which I
just don't have the Project time to change (since the
changes ripple through other Package areas). Thus,
I am turning to the updates and fixes to GLIB, which are
suppose to correct this issue, as well as, other issues.
Can I infer from your statement about the committal of your
changes to the GLIBC CVS Tree that GNU GLIBC 2.1.91 Version
should be PowerPC compatible ? I must admit, I have not
kept up to date on the current Processors that the GNU
GCC and GLIBs are said to fully support. Looking through
some of the archived mailings on this List, there would
seem to be some contention to GCC and GLIB full support,
or GNU Org's willingness to work on support, of PowerPC.
Jeff
"Kevin B. Hendricks" wrote:
Hi,
In case you were wondering, that patch has now (just today) been officially
added to the glibc 2.1 branch of the official glibc cvs tree. The patch in
question prevents a race in setting the onwer to null on a mutex that
resulting in tests in condvar.c to fail about the owner of the mutex not
being the same as the caller of the thread (when it actually was).
With this in place, the JDK native threads now seem to work well.
Please let me know if this sodesn't fix your problems (I am always
interested in the linuxthreads library when tracking down jdk failures).
Thanks,
Kevin
--
********************************************************
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/