similar to: CentOS-announce Digest, Vol 110, Issue 2

CentOS Errata and Security Advisory 2014:0348 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0348.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4791c5a062d2fafdbc3281552de6770ffcfb2e678913af78a76e8160e7398343 xalan-j2-2.7.0-9.9.el6_5.noarch.rpm

CentOS Errata and Security Advisory 2014:0348 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0348.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0a93cd521aa9197ef5e08abbc130eddae7b0d7d7bdc8de2e3e417e0ceb72789b xalan-j2-2.7.0-6jpp.2.i386.rpm

Hello, I have some problems running some tools of java in CentOS. Anyone know where is the problem for this? > [jv at localhost ~]$ java org.apache.xalan.xslt.Process > Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.xalan.xslt.Process > at gnu.java.lang.MainThread.run(libgcj.so.7rh) > Caused by: java.lang.ClassNotFoundException:

Is anyone running tomcat5 from jpackage 1.6 on cento4 w/ java-1.4.2- sun-1.4.2.08-1jpp ? I'm getting weird dependencies which don't make sense, notably: Error: Missing Dependency: jdk = 2000:1.5.0_02-fcs is needed by package java-1.5.0-sun-compat I want to use 1.4.2 not 1.5 and it doesn't make sense to have jdk = 2000:1.5.0_02-fcs, unless I'm missing something? I do have

Is there any documentation telling you whether tomcat5 was compiled against the 1.4.2 tree or the 1.5? You could try downloading the srpm, patching it to use the 1.4.2 java and then re-create your own rpm. Just a thought, might be an easier way though; will wait for the experts response. -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On

On Tue, Nov 12, 2013 at 2:08 PM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Tue, Nov 12, 2013 at 1:01 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> Hi Manman, >> >> Thanks for sending this summary and progress plans - it's great to see >> the impact your changes have had and ideas for future direction. >> >>

On Tue, Nov 12, 2013 at 1:01 PM, David Blaikie <dblaikie at gmail.com> wrote: > Hi Manman, > > Thanks for sending this summary and progress plans - it's great to see the > impact your changes have had and ideas for future direction. > > Type uniquing for C++ is in. Some data for Xalan with -flto -g: >> 9.9MB raw dwarf size, peak memory usage at 2.8GB >> The

Dale, > Works for me on x86-64 Darwin, fwiw. That looks pretty strange. Ok, it can work for small testcases, but will surely fail when you try to use for something more real. Currently it at least lacks information about frame moves. So, every invoke, which needs to restore call-clobbered registers during unwinding will be broken. Does Shootout-C++/except work for you? And stuff from llvm

On Feb 9, 2008, at 11:20 AM, Anton Korobeynikov wrote: > Dale, > >> Works for me on x86-64 Darwin, fwiw. > That looks pretty strange. Ok, it can work for small testcases, but > will > surely fail when you try to use for something more real. Currently > it at > least lacks information about frame moves. So, every invoke, which > needs > to restore

strugging with things here... tried tracking the info on the Wiki (which apparently is now in need of a maintainer)... http://wiki.centos.org/HowTos/JavaOnCentOS My primary interest is using Xalan/Saxon/xslt/xsl-fo docbook generation. I was thinking that all I really need is jre but downloaded both jre and jdk just in case. can anyone tell me what I'm doing wrong? (after removing both jdk

Hi Manman, Thanks for sending this summary and progress plans - it's great to see the impact your changes have had and ideas for future direction. Type uniquing for C++ is in. Some data for Xalan with -flto -g: > 9.9MB raw dwarf size, peak memory usage at 2.8GB > The raw dwarf size was 58MB, memory usage was 7GB back in May, 2013. > Other efforts at size reduction helped, and type

Hi All, Type uniquing for C++ is in. Some data for Xalan with -flto -g: 9.9MB raw dwarf size, peak memory usage at 2.8GB The raw dwarf size was 58MB, memory usage was 7GB back in May, 2013. Other efforts at size reduction helped, and type uniquing improved on top of those. Data on building clang with "-flto -g" after type uniquing: 3.4GB MDNodes after parsing all bc files, 7GB

Hi, Sorry if this is to wrong mailing list. In that case, please point me to correct mailing list. Please also excuse rather long mail - I am not sure what piece of information would be useful for anybody who could help me. Couple of days back I had put a query about box-plots using GUI. I got some excellent suggestions. One of them was to use JGR/Deducer. It worked quite well for my needs.

Hi All, In LTO, we load in the source modules and link the source modules into a destination module. Lots of MDNodes are only used by the source modules, for example Xalan used 649MB for MDNodes after loading and linking, but the actual destination module only has 393MB of MDNodes. There are 649-393MB (40% of 649MB) not used. MDNodes belong to the Context, deleting modules will not release the

On Tue, Nov 12, 2013 at 4:29 PM, Manman Ren <manman.ren at gmail.com> wrote: > Hi All, > > In LTO, we load in the source modules and link the source modules into a > destination module. > Lots of MDNodes are only used by the source modules, for example Xalan > used 649MB for MDNodes after loading and linking, but the actual > destination module only has 393MB of

On Wed, Oct 16, 2013 at 9:10 PM, Manman Ren <manman.ren at gmail.com> wrote: > > > > On Wed, Oct 16, 2013 at 1:58 PM, David Blaikie <dblaikie at gmail.com> wrote: > >> >> >> >> On Wed, Oct 16, 2013 at 1:21 PM, Manman Ren <manman.ren at gmail.com> wrote: >> >>> >>> There are a few places where we break the assumption:

On Wed, Oct 16, 2013 at 1:58 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Wed, Oct 16, 2013 at 1:21 PM, Manman Ren <manman.ren at gmail.com> wrote: > >> >> There are a few places where we break the assumption: >> 1> formal_parameter constructed in DwarfDebug when adding attribute type >> we call SPCU->addType(Arg, ATy),

On Wed, Oct 16, 2013 at 1:21 PM, Manman Ren <manman.ren at gmail.com> wrote: > > There are a few places where we break the assumption: > 1> formal_parameter constructed in DwarfDebug when adding attribute type > we call SPCU->addType(Arg, ATy), where Arg does not belong to SPCU. > 2> inlined_subroutine constructed in DwarfDebug when adding attribute >

On Wed, Oct 16, 2013 at 10:32 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Wed, Oct 16, 2013 at 9:10 PM, Manman Ren <manman.ren at gmail.com> wrote: > >> >> >> >> On Wed, Oct 16, 2013 at 1:58 PM, David Blaikie <dblaikie at gmail.com>wrote: >> >>> >>> >>> >>> On Wed, Oct 16, 2013 at

On Tue, Nov 12, 2013 at 4:38 PM, Chandler Carruth <chandlerc at google.com>wrote: > > On Tue, Nov 12, 2013 at 4:29 PM, Manman Ren <manman.ren at gmail.com> wrote: > >> Hi All, >> >> In LTO, we load in the source modules and link the source modules into a >> destination module. >> Lots of MDNodes are only used by the source modules, for example