It seems odd to be supporting ways to build that we don't want to encourage and
won't test regularly, but the changes themselves seem fine, so I'm okay with it.
From: Sun Chan [mailto:sun.c...@gmail.com]
Sent: Wednesday, May 02, 2012 5:00 PM
To: David Coakley
Cc: open64-devel; Mike Murphy
Subject: Re: [Open64-devel] code review request for bug 779 [BUILD]
I am ok with it, otoh, I defer to Mike for the call.
Sun
On Wed, May 2, 2012 at 3:16 PM, David Coakley
<dcoak...@gmail.com<mailto:dcoak...@gmail.com>> wrote:
Yes, because people expect that projects that use configure (autoconf)
will support building in the source directory. We can either disallow
it or make the change to fix the known problems, which is what I
proposed. It is still ok (and preferred) to build in a separate
directory.
On Mon, Apr 30, 2012 at 11:29 PM, Sun Chan
<sun.c...@gmail.com<mailto:sun.c...@gmail.com>> wrote:
> we never intended open64 binary being built in the source directory. You are
> saying this change allows that?
> Sun
>
> On Tue, May 1, 2012 at 11:59 AM, David Coakley
> <dcoak...@gmail.com<mailto:dcoak...@gmail.com>> wrote:
>>
>> I did not receive any feedback on this patch. Can one of the
>> gatekeepers take a look? Thanks.
>>
>> On Sun, Apr 15, 2012 at 8:16 PM, David Coakley
>> <dcoak...@gmail.com<mailto:dcoak...@gmail.com>> wrote:
>> > 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
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Open64-devel mailing list
>> Open64-devel@lists.sourceforge.net<mailto:Open64-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/open64-devel
>
>
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may
contain
confidential information. Any unauthorized review, use, disclosure or
distribution
is prohibited. If you are not the intended recipient, please contact the
sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel
