On 2014-03-01 00:24, Omair Majid wrote:
* Phil Race [2014-02-28 16:46]:
The moving of most of these files will cause me some significant pain.
Oh. Sorry :(
Is there anything I (or possibly the jigsaw folks) can do to minimize
it?
I am not convinced why its necessary.
Basically, there is on
On 2014-03-17 05:13, David Holmes wrote:
On 15/03/2014 7:11 AM, Alexander Smundak wrote:
Ping.
My position hasn't changed. I don't think this needs to be, or should
be, a distinct architecture.
I've added build-dev to cc list to see what our build experts think.
I'm not sure I've complete
Hi Magnus,
The change keeps target cpu and target cpu arch as is. The C-code uses
-DLITTLE_ENDIAN to distinguish implementation differences.
As I understand, we discuss the setting of BUILDARCH in the makefiles.
Indirectly it is set from uname, which returns ppc64le on these machines.
This affe
Hi,
having said what I wanted to say about the build output directory path,
I'm fine with both solutions. In the end it affects only a few line
in shared make files.
Best regards,
Goetz
-Original Message-
From: hotspot-dev [mailto:hotspot-dev-boun...@openjdk.java.net] On Behalf Of
D
- Original Message -
> On 3/3/14 2:49 PM, Omair Majid wrote:
> > * David Holmes [2014-02-28 18:48]:
> >> There are three pieces to all of this:
> >>
> >> 1. Generating debug symbols in the binaries (via gcc -g or whatever)
> >> 2. Generating debuginfo files (zipped or not) (FDS)
> >> 3. St
On 3/17/14 6:36 AM, Lindenmaier, Goetz wrote:
Hi Magnus,
The change keeps target cpu and target cpu arch as is. The C-code uses
-DLITTLE_ENDIAN to distinguish implementation differences.
As I understand, we discuss the setting of BUILDARCH in the makefiles.
Indirectly it is set from uname, whi
