R12:
Relink error for MSC modules
Cause
The following packages are not part of the Oracle Linux 5* distribution media and must be downloaded separately and installed manually:
For Update 1 or 2:
binutils-2.17.50.0.6-6.0.1.x86_642
For Update 3:
binutils-2.17.50.0.6-9.0.1.x86_642
For Update 4 (5.4) or higher, there is workaround for failures while relinking the Advanced Supply Chain Planning (ASCP) executables MSO, MSC, MSR and FEM.
Solution
To fix this problem, users are required to replace the following line under the Linux section of file " $AD_TOP/bin/adrelinknew.sh":
From:
CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'
TO:
CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec'
After making this change, run adadmin utility to relink MSC product.
Explanation
--noinhibit-exec
Retain the executable output file whenever it is still usable. Normally, the linker will not produce an output file if it encounters errors during the
link process; it exits without writing an output file when it issues any error whatsoever.
Binutils developers apparently have a very relaxed definition of usable,
because this option can lead to binaries that are very unusable without
advanced hackery.
The following packages are not part of the Oracle Linux 5* distribution media and must be downloaded separately and installed manually:
For Update 1 or 2:
binutils-2.17.50.0.6-6.0.1.x86_642
For Update 3:
binutils-2.17.50.0.6-9.0.1.x86_642
For Update 4 (5.4) or higher, there is workaround for failures while relinking the Advanced Supply Chain Planning (ASCP) executables MSO, MSC, MSR and FEM.
Solution
To fix this problem, users are required to replace the following line under the Linux section of file " $AD_TOP/bin/adrelinknew.sh":
From:
CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'
TO:
CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec'
After making this change, run adadmin utility to relink MSC product.
Explanation
--noinhibit-exec
Retain the executable output file whenever it is still usable. Normally, the linker will not produce an output file if it encounters errors during the
link process; it exits without writing an output file when it issues any error whatsoever.
Binutils developers apparently have a very relaxed definition of usable,
because this option can lead to binaries that are very unusable without
advanced hackery.
0 comments:
Post a Comment