I'm still confused. You are saying the executables to compile the
libraries such as libmv? If that is the case, the executable should
have rpath set just like the compiler? Otherwise, you are not doing
the right boot sequence (cross/boot/reboot). What am I missing?
Sun
On Fri, Oct 22, 2010 at 5:12
It should work ok for the "main" case since this function is used for
both cases. In practice, the compiler executables do not reference
the libraries; the executables are built first and then used to
compile the libraries.
For testing, I built the patched compiler with BUILD_COMPILER=GNU and
the
so only main of the compiler should have RPATH set, not the .so's.
Now, how does your fix deal with the case when the build is "main"?
Sun
On Thu, Oct 21, 2010 at 8:43 PM, David Coakley wrote:
> The run_build flag is set by the '--run-build' command-line option and
> allows the compiler to run fr
The run_build flag is set by the '--run-build' command-line option and
allows the compiler to run from the build directory. It's used during
the compiler build so that the libraries can be built before the
compiler is installed.
See osprey/linux/gcommondefs for the use of the option and the
top-l
can you give some detail how run_build is set? I agree with you on
principle the fix.
Sun
On Thu, Oct 21, 2010 at 7:49 PM, David Coakley wrote:
> In the Open64 driver, there is code to add a linker '-rpath' option
> for libraries that are included with the compiler (see
> postprocess_ld_args() in
In the Open64 driver, there is code to add a linker '-rpath' option
for libraries that are included with the compiler (see
postprocess_ld_args() in the driver). The intended effect of this
code is that programs compiled by Open64 can be run without setting
LD_LIBRARY_PATH as long as the compiler i
