-
Bug
-
Resolution: Not an Issue
-
P3
-
None
-
1.4.1
-
x86
-
linux
Name: rl43681 Date: 01/28/2003
FULL PRODUCT VERSION :
java version "1.4.1-internal"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.4.1-internal-tt-1043352843)
Java HotSpot(TM) Client VM (build 1.4.1-internal-tt-1043352843, mixed mode)
FULL OPERATING SYSTEM VERSION :
Linux From Scratch 4.0
* gcc-3.2.1
* glibc-2.3.1
* linux-2.4.20
A DESCRIPTION OF THE PROBLEM :
When compiling, the build relies on having the binaries in
fixed location (e.g. /usr/bin) instead of picking them from
the user's path. This causes problems when the developer
needs to check compilation with different versions.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Download J2SDK and compile as per the instructions.
EXPECTED VERSUS ACTUAL BEHAVIOR :
The build should honor the user's PATH settings.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
The build fails with "command not found" if the command is not in the directory
where the build expects it to be, even though the command is in the user's PATH.
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER WORKAROUND :
The patch is avaliable at
<http://www.linuxfromscratch.org/~tushar/hints/files/JavaFromScratch/j2sdk-1.4.1-remove-fixed-paths.patch.bz2>.
(Review ID: 180442)
======================================================================
- relates to
-
JDK-4811946 build documents should explain the intent of not letting PATH affect build
-
- Resolved
-