On 27/03/2013 11:26 PM, David Chase wrote:
It's not "my" version, it's whatever someone else installed on one of the
ghostboxes (terminus).
I was perhaps misled into using a 5.11 box by
(1) seeing it listed as a box for our use;
(2) my success building with Solaris 11 on Intel;
(3) the fact tha
I'm not sure which is what but I'd like to see:
ifeq ($(INCLUDE_SA), true)
...
used.
Thanks,
David
On 28/03/2013 12:05 AM, Roman Kennke wrote:
Am Mittwoch, den 27.03.2013, 09:42 -0400 schrieb Omair Majid:
Hi,
On 03/27/2013 04:55 AM, Erik Joelsson wrote:
Work on this was already initiated
On 27/03/2013 10:58 PM, Erik Joelsson wrote:
On 2013-03-27 13:20, David Holmes wrote:
On 27/03/2013 8:59 PM, Erik Joelsson wrote:
I found the problem and fixed it:
http://cr.openjdk.java.net/~erikj/8010908/webrev.jdk.01/
I don't understand - how did this:
`$(FIND) $(JDK_OUTPUTDIR)/bin -type
There was a bug in the gobjcopy in Solaris 11.0 that was fixed in 11.1.
Check with Dan
-kto
On Mar 26, 2013, at 7:40 PM, David Holmes wrote:
> On 27/03/2013 2:33 AM, David Chase wrote:
>> I think I'm doing a vanilla new-build, but obviously I'm not, because it
>> fails.
>> What should I be lo
Changeset: 6782f2c46bca
Author:wetmore
Date: 2013-03-21 16:31 -0700
URL: http://hg.openjdk.java.net/jdk8/build/jdk/rev/6782f2c46bca
8009517: new code changes causing errors in old build (-Werror) environment
Reviewed-by: mduigou
! make/com/sun/org/apache/xml/Makefile
! make/javax/o
This may be releated to the fact that on SLES 10 the default linker
only supports anonymous version tags. As far as I know Oracle Java 7
libraries have named version tags (of the form `SUNWprivate_1.1') but
are compiled on RedHat which doesn't has this problem.
I don't have a link at hand but you
Getting to new build on Solaris11-sparc (not necessary for Solaris11-x86).
Here's a recipe that works. It is biased towards modern releases of software.
Note the use of undocumented flag-seting to configure and make at various steps,
and the two out-of-band adjustments to binutils.
1) configure+
Hi Mark,
the next time you post to an OpenJDK mailing list please provide links
which are visible from outside Oracle as well:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7152237
Thank you,
Volker
On Wed, Mar 27, 2013 at 8:24 PM, Mark Susko wrote:
> Hi all,
>
> http://monaco.sfbay.sun
Hi all,
http://monaco.sfbay.sun.com/detail.jsp?cr=7152237
I have a customer who is asking about the above bug. It seems they too
have run into it.
I explained about the public comment regarding fPIC that was in there
and asked them to test different SLES builds.
Their response is:
It works on
I'm pretty sure this wouldn't have happened with "Open Solaris 11" :)
On Wed, Mar 27, 2013 at 6:17 PM, David Chase wrote:
> On 2013-03-27, at 1:08 PM, Volker Simonis
> wrote:
>
> > Hi David,
> >
> > I found a Solaris 11 box today and it seems that this is really a
> problem of binutils 2.19 on
On 2013-03-27, at 1:08 PM, Volker Simonis wrote:
> Hi David,
>
> I found a Solaris 11 box today and it seems that this is really a problem of
> binutils 2.19 on Solaris 11.
And vice-versa -- 10 minutes ago I tried gobjcopy 2.15 on the command line (on
Solaris 11, with the same libjvm.so) and
Hi David,
I found a Solaris 11 box today and it seems that this is really a problem
of binutils 2.19 on Solaris 11.
Initially there was no gobjcopy on my Solaris machine at all so I did the
following:
- downloaded gnu-binutils.p5i from
http://pkg.oracle.com/solaris/release/en/index.shtml
- insta
I've generated a couple of webrevs using your updated version. It's definitely
an improvement.
When I made my updates I didn't change the version number "23.18" but instead
just added "+jbs". I do think we should decide what to do regarding versioning
especially since webrev writes it's version
It led to an ugly failure (see below).
I took it off my path, cleaned, configured, and the build (so far) went better.
I checked the version it was picking up, and it was 3.16.
So configure might want to check for this.
(Why is this crap on my path? I no longer remember, it has been there for
alm
On 03/27/13 09:21, David Chase wrote:
PATH=/java/devtools/sparc/bin:/java/devtools/sparc/SUNWspro/SS12u1/bin/:/usr/sfw/bin:/usr/ccs/bin:/home/drchase/bin:/pkg/gnu/bin:/pkg/isv/bin:/pkg/usrdist/bin:/pkg/local/bin:/lab/tools/bin:/lab/east/bin:/usr/bin:/bin
uname -a = SunOS dr-evil 5.10 Generic_1429
I still need a review for both of these changes.
Mike
On Mar 18 2013, at 22:48 , Mike Duigou wrote:
> A two small changes to review:
>
> If approved I will commit to TL (or someone else can commit to build for me)
>
> Mike
>
> JDK-8010267 : Add test-clean for cleaning of testoutput directory
PATH=/java/devtools/sparc/bin:/java/devtools/sparc/SUNWspro/SS12u1/bin/:/usr/sfw/bin:/usr/ccs/bin:/home/drchase/bin:/pkg/gnu/bin:/pkg/isv/bin:/pkg/usrdist/bin:/pkg/local/bin:/lab/tools/bin:/lab/east/bin:/usr/bin:/bin
uname -a = SunOS dr-evil 5.10 Generic_142900-03 sun4v sparc SUNW,Sun-Fire-T1000
m
Hi Erik:
I found the problem and fixed it:
http://cr.openjdk.java.net/~erikj/8010908/webrev.jdk.01/
Looks good.
/Erik
On 2013-03-27 11:12, Erik Joelsson wrote:
I just tried this and the failure reproduces for me. Will investigate.
/Erik
On 2013-03-27 01:56, Bharadwaj Yadavalli wrote:
Am Mittwoch, den 27.03.2013, 09:55 +0100 schrieb Erik Joelsson:
> Work on this was already initiated in this thread:
>
> http://mail.openjdk.java.net/pipermail/build-infra-dev/2013-February/003059.html
>
> Would be good if these efforts could be synchronized.
>
> I like that you define and trans
Am Mittwoch, den 27.03.2013, 09:42 -0400 schrieb Omair Majid:
> Hi,
>
> On 03/27/2013 04:55 AM, Erik Joelsson wrote:
> > Work on this was already initiated in this thread:
> >
> > http://mail.openjdk.java.net/pipermail/build-infra-dev/2013-February/003059.html
> >
>
> Whoops. I was not aware of
On 3/27/2013 6:59 AM, Erik Joelsson wrote:
I found the problem and fixed it:
http://cr.openjdk.java.net/~erikj/8010908/webrev.jdk.01/
Thanks for your quick response! Your proposed change worked for me.
Bharadwaj
Hi,
On 03/27/2013 04:55 AM, Erik Joelsson wrote:
> Work on this was already initiated in this thread:
>
> http://mail.openjdk.java.net/pipermail/build-infra-dev/2013-February/003059.html
>
Whoops. I was not aware of this. Thanks for pointing this out.
> Would be good if these efforts could be
It's not "my" version, it's whatever someone else installed on one of the
ghostboxes (terminus).
I was perhaps misled into using a 5.11 box by
(1) seeing it listed as a box for our use;
(2) my success building with Solaris 11 on Intel;
(3) the fact that the exact OS version is not mentioned in th
On 2013-03-27 13:20, David Holmes wrote:
On 27/03/2013 8:59 PM, Erik Joelsson wrote:
I found the problem and fixed it:
http://cr.openjdk.java.net/~erikj/8010908/webrev.jdk.01/
I don't understand - how did this:
`$(FIND) $(JDK_OUTPUTDIR)/bin -type f -name \*$(EXE_SUFFIX)`
match .debuginfo fi
On 27/03/2013 8:59 PM, Erik Joelsson wrote:
I found the problem and fixed it:
http://cr.openjdk.java.net/~erikj/8010908/webrev.jdk.01/
I don't understand - how did this:
`$(FIND) $(JDK_OUTPUTDIR)/bin -type f -name \*$(EXE_SUFFIX)`
match .debuginfo files but not .diz files (EXE_SUFFIX is empt
I found the problem and fixed it:
http://cr.openjdk.java.net/~erikj/8010908/webrev.jdk.01/
/Erik
On 2013-03-27 11:12, Erik Joelsson wrote:
I just tried this and the failure reproduces for me. Will investigate.
/Erik
On 2013-03-27 01:56, Bharadwaj Yadavalli wrote:
Hi David,
Thanks for the
I just tried this and the failure reproduces for me. Will investigate.
/Erik
On 2013-03-27 01:56, Bharadwaj Yadavalli wrote:
Hi David,
Thanks for the suggestion.
On 3/7/2013 7:54 PM, David Holmes wrote:
I think this is a bug in Images.gmk:
ifneq ($(OPENJDK_TARGET_OS),windows)
ALL_BIN_L
On 2013-03-27 10:26, Roman Kennke wrote:
Am Mittwoch, den 27.03.2013, 09:55 +0100 schrieb Erik Joelsson:
Work on this was already initiated in this thread:
http://mail.openjdk.java.net/pipermail/build-infra-dev/2013-February/003059.html
Would be good if these efforts could be synchronized.
On 27/03/2013 9:43 AM, Omair Majid wrote:
Hi,
I tried using the new build system to build zero and ran into a bunch of
problems. The following webrev allows me to build zero successfully.
http://cr.openjdk.java.net/~omajid/webrevs/zero-newbuild/00/
Any thoughts, comments or suggestions?
The
On 2013-03-27 01:13, Martin Buchholz wrote:
Sorry, false alarm.
The build proceeded so quietly and quickly, (and my modified code worked
the first time!) that I assumed it must have not been built at all, but I
was wrong. Congratulations to the build team! But a bit more verbosity to
reassure
Work on this was already initiated in this thread:
http://mail.openjdk.java.net/pipermail/build-infra-dev/2013-February/003059.html
Would be good if these efforts could be synchronized.
I like that you define and translate these hotspot specific variables in
hotspot-spec.gmk. I don't think we
31 matches
Mail list logo
