Changeset: 23032c78b2d1
Author:katleman
Date: 2012-08-09 18:02 -0700
URL: http://hg.openjdk.java.net/jdk8/build/langtools/rev/23032c78b2d1
Added tag jdk8-b51 for changeset c4cd4cab2220
! .hgtags
Changeset: cddc2c894cc6
Author:mcimadamore
Date: 2012-08-02 18:22 +0100
URL:
Changeset: b3b0d75cb117
Author:katleman
Date: 2012-08-09 18:02 -0700
URL: http://hg.openjdk.java.net/jdk8/build/jdk/rev/b3b0d75cb117
Added tag jdk8-b51 for changeset e865efbc7105
! .hgtags
Changeset: 21c590fdc8cb
Author:mullan
Date: 2012-08-01 11:06 -0400
URL: http:
Changeset: f62bc618122e
Author:katleman
Date: 2012-08-09 18:01 -0700
URL: http://hg.openjdk.java.net/jdk8/build/jaxws/rev/f62bc618122e
Added tag jdk8-b51 for changeset 1a70b6333ebe
! .hgtags
Changeset: bd3c00d57614
Author:katleman
Date: 2012-08-09 18:01 -0700
URL: http://hg.openjdk.java.net/jdk8/build/jaxp/rev/bd3c00d57614
Added tag jdk8-b51 for changeset dc1ea77ed9d9
! .hgtags
Changeset: abc951e44e1b
Author:katleman
Date: 2012-08-09 18:00 -0700
URL: http://hg.openjdk.java.net/jdk8/build/hotspot/rev/abc951e44e1b
Added tag jdk8-b51 for changeset 663fc23da8d5
! .hgtags
Changeset: ef437ea56651
Author:amurillo
Date: 2012-08-03 13:24 -0700
URL:
Changeset: 8d24def5ceb3
Author:katleman
Date: 2012-08-09 18:00 -0700
URL: http://hg.openjdk.java.net/jdk8/build/rev/8d24def5ceb3
Added tag jdk8-b51 for changeset 57c0aee73090
! .hgtags
Changeset: 80689ff9cb49
Author:katleman
Date: 2012-08-09 18:00 -0700
URL: http://hg.openjdk.java.net/jdk8/build/corba/rev/80689ff9cb49
Added tag jdk8-b51 for changeset 9b0f841ca9f7
! .hgtags
I would expect the necessary classes to be in
build/$PLATFORM-$ARCH/classes, so you might want to try using that path
instead of the proposed condition.
-- Jon
On 08/15/2012 11:30 AM, Joel Borggrén-Franck wrote:
Well that didn't work, patch inline:
diff -r 38263aa28324 src/macosx/native/jo
Ive filed a bug: 7191703 for this.
Kumar
I would't say I'm working on it.
But from the department of "works for me (^(TM))" here is a patch that sort of
works for me. It might be breaking other stuff (like full forest builds), and it might
not be what we want to do ...
cheers
/Joel
On 1
Well that didn't work, patch inline:
diff -r 38263aa28324 src/macosx/native/jobjc/build.xml
--- a/src/macosx/native/jobjc/build.xml Mon Jul 30 22:32:59 2012 +0100
+++ b/src/macosx/native/jobjc/build.xml Wed Aug 15 20:09:08 2012 +0200
@@ -73,6 +73,10 @@
+
+
+
+
@@ -115
I would't say I'm working on it.
But from the department of "works for me (™)" here is a patch that sort of
works for me. It might be breaking other stuff (like full forest builds), and
it might not be what we want to do ...
cheers
/Joel
On 10 aug 2012, at 07:39, Erik Joelsson wrote:
> It
2012/8/15 4:52 -0700, [email protected]:
> Unfortunately, it is not that simple to just replace everything with x86.
Sad, but true.
> ...
>
> 2) Changing names on files or directories (unfortunately) makes version
> control
> harder. If files are to be moved around all over the plac
amd64 was very company specific and as far as I knew, we were favoring x64, but
I have no objection to x86_64.
But in some places, like the jre/lib/ARCH name, we are kind of stuck with
amd64, but now that I think about it,
I'm not exactly sure why we would be stuck with any directory name like th
On Aug 15, 2012, at 10:38 AM, Dmitry Samersoff wrote:
> Hi Everyone,
>
> Currently we uses i386, i486 and i586 within x86 build.
Yeah, historic stuff. This is a more difficult problem than it seems, as
Magnus says.
>
> Do we have a plan to cleanup it and replace to just "x86"?
Where we ca
On 2012-08-15 14:15, Dmitry Samersoff wrote:
Magnus,
Thank you for the background.
I understand that big architecture names cleanup contains lots of
underwater stones.
It's why I'm asking just for one piece of this mess - I would like
to have {i386,i486,i586} changed to the single name.
The
Magnus,
Thank you for the background.
I understand that big architecture names cleanup contains lots of
underwater stones.
It's why I'm asking just for one piece of this mess - I would like
to have {i386,i486,i586} changed to the single name.
-Dmitry
On 2012-08-15 15:52, Magnus Ihse Bursie w
On 2012-08-15 10:38, Dmitry Samersoff wrote:
Hi Everyone,
Currently we uses i386, i486 and i586 within x86 build.
Not only the 32-bit Intel architecture, but the 64-bit as well has
naming confusions.
Unfortunately, it is not that simple to just replace everything with x86.
1) Some things hav
Hi Everyone,
Currently we uses i386, i486 and i586 within x86 build.
Do we have a plan to cleanup it and replace to just "x86"?
-Dmitry
--
Dmitry Samersoff
Java Hotspot development team, SPB04
* There will come soft rains ...
18 matches
Mail list logo