The attached patch is a fix for bug 779, a common build problem for new users of Open64. Here is the proposed commit message:
Fix bug 779: build in source directory does not work. In the osprey-gcc-4.2.0 build always use a known subdirectory for $(host_subdir) instead of making the choice depending on where configure was run, so that we always know where to find the build artifacts. Also in the osprey-gcc 4.2.0 build use a path relative to $(build_objdir) to find libgspin42.a. In the build of the cygnus/ld subdirectory, use the "new-ld" target instead of "all". The "all" target causes unwanted modifications to checked-in files when the build is being done in the source directory. For Open64, we only need the new-ld (ipa_link) executable. Note: I still recommend that you build in a separate directory and that we leave the build instructions as-is. Because we don't have the proper svn:ignore directives set up, doing a build in the source directory creates a lot of files with unknown svn status. Could a gatekeeper please review? Thanks, -David Coakley / AMD Open Source Compiler Engineering
build_in_srcdir.diff
Description: Binary data
------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________ Open64-devel mailing list Open64-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open64-devel
