Hi Kai,
>From the dates I believe it is...
One way to tell is to compile something, such as hw.c:
xlc_r -qsource hw.c
That should get you a listing which should have the compiler version in it
at the top of the listing file (either in hw.lst or output to stdout).
Regards,
David A. Cargill
XML Parser Development
IBM Toronto Lab
(905) 413-2371, tie 969
[EMAIL PROTECTED]
"Kai Hackemesser"
<[EMAIL PROTECTED]>
To
04/26/2005 11:28 "cargilld (JIRA)"
AM <[email protected]>
cc
Please respond to Subject
c-dev Re: [jira] Commented:
(XERCESC-1413) Build fails on
PowerPC IBM AIX 4.3.3.0
Hello, David,
currently I don't know how to figure out the version of xlC. If you know
how
to get it, tell me please.
This is the bin/ directory containing the executables. maybe you can
identify from filesize or age :-)
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 CC_r4
-r-xr-xr-x 1 bin bin 12419 Feb 27 1999 c++filt
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 c89
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 cc
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 cc128
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 cc_r
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 cc_r4
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 cc_r7
-r-xr-xr-x 1 bin bin 2823 Feb 27 1999 cleanpdf
-r-xr-xr-x 1 bin bin 1261767 Dec 18 1998 irc
-r-xr-xr-x 1 bin bin 254842 Dec 18 1998 irccnv
-r-xr-xr-x 1 bin bin 5845 Feb 26 1999 linkxlC
-r-xr-xr-x 3 bin bin 6248 Feb 26 1999 makeC++SharedLib
-r-xr-xr-x 3 bin bin 6248 Feb 26 1999 makeC++SharedLib128
-r-xr-xr-x 3 bin bin 6248 Feb 26 1999 makeC++SharedLib_r
-r-xr-xr-x 1 bin bin 1613 Feb 26 1999 replaceCSET
-r-xr-xr-x 1 bin bin 3135 Feb 27 1999 resetpdf
-r-xr-xr-x 1 bin bin 1511 Feb 26 1999 restoreCSET
-r-xr-xr-x 1 bin bin 4423 Feb 27 1999 showpdf
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlC
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlC128
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlC_r
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlC_r4
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlC_r7
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlc
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlc128
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlc_r
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlc_r4
-r-xr-xr-x 17 bin bin 74494 Feb 27 1999 xlc_r7
regards,
Kai
> [
>
http://issues.apache.org/jira/browse/XERCESC-1413?page=comments#action_63796
]
>
> cargilld commented on XERCESC-1413:
> -----------------------------------
>
> Hi Kai,
> What version of xlC are you using? I build on AIX regularly and haven't
> encountered these problems.
>
> For the first error I don't see anything wrong with:
> void operator delete(void* p, MemoryManager* memMgr);
>
> For the second error, it is a bug:
> ArrayJanitor& operator=(const ArrayJanitor<T>& copy);
> should be:
> ArrayJanitor<T>& operator=(const ArrayJanitor<T>& copy);
>
> I will fix this later.
>
> David
>
> > Build fails on PowerPC IBM AIX 4.3.3.0
> > --------------------------------------
> >
> > Key: XERCESC-1413
> > URL: http://issues.apache.org/jira/browse/XERCESC-1413
> > Project: Xerces-C++
> > Type: Bug
> > Components: Utilities
> > Versions: 2.6.0
> > Environment: PowerPC IBM AIX 4.3.3.0,
> > Reporter: Kai Hackemesser
>
> >
> > This is the output from 'make' I got:
> > xlC_r -qnotempinc -D_THREAD_SAFE -qnamemangling=ansi -c
> -I/home/edm/mpadm22/xerces-c-src_2_6_0/src/xercesc/include -w -O2
-DPROJ_XMLPARSER
> -DPROJ_XMLUTIL -DPROJ_PARSERS -DPROJ_SAX4C -DPROJ_SAX2 -DPROJ_DOM
> -DPROJ_DEPRECATED_DOM -DPROJ_VALIDATORS -DXML_USE_NATIVE_TRANSCODER
> -DXML_USE_INMEM_MESSAGELOADER -DXML_USE_PTHREADS
-DXML_USE_NETACCESSOR_SOCKET -o
> /home/edm/mpadm22/xerces-c-src_2_6_0/src/xercesc/obj/AIX/Base64.o
Base64.cpp
> >
>
"/home/edm/mpadm22/xerces-c-src_2_6_0/src/xercesc/include/xercesc/util/XMemory.hpp",
line 98.10: 1540-141: (S) Argument 2 for "operator delete"
> must be of type "unsigned long".
> >
>
"/home/edm/mpadm22/xerces-c-src_2_6_0/src/xercesc/include/xercesc/util/Janitor.hpp",
line 146.17: 1540-090: (S) Syntax error - expected "<" and
> found "&".
> > make[1]: *** [Base64.o] Error 1
> > make[1]: Leaving directory
> `/home/edm/mpadm22/xerces-c-src_2_6_0/src/xercesc/util'
> > make: *** [Util] Error 2
> > How to solve?
> > Regards,
> > Kai
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
