Bug 38191 - sun java sdk incompatible with textutils
sun java sdk incompatible with textutils
Product: Red Hat Linux
Classification: Retired
Component: textutils (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-04-28 06:15 EDT by Tim Grant
Modified: 2007-04-18 12:32 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-04-28 06:15:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Grant 2001-04-28 06:15:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i686)

The Sun Java sdk is incompatible with the version of textutils shipped in
rh7.1 due to cut being moved from /usr/bincut to /bin/cut.  This can be
fixed with "ln -s /bin/cut /usr/bin/cut" however the jvm will still not
work (reason unknown).  The compiler does now work however.

Reproducible: Always
Steps to Reproduce:
1.java <class file>

Actual Results:  starts three java threads and hangs

Expected Results:  successful program execution
Comment 1 Bernhard Rosenkraenzer 2001-04-30 12:52:15 EDT
Since they refuse to release the source code, there's nothing whatsoever we 
can do to fix their bugs. For cut, they should search $PATH - neither FHS nor 
LSB guarantee you'll find a version of cut in /usr/bin. I've added a symlink 
in textutils though, since some other apps are stupid enough to hardcode 
/usr/bin/cut, as well.

The segmentation fault is releated to their (again stupid and not standards 
compliant) insistence on the stack being fixed-size and 2 MB, neither of which 
is the case in the i686 build of glibc. Check the release notes for more 
details and the workaround for terribly broken applications like jdk.

Note You need to log in before you can comment on or make changes to this bug.