cpip-develop Mailing List for cpip
Status: Alpha
Brought to you by:
cpip
Menu
▾
▴
cpip-develop — CPIP development discussion
You can subscribe to this list here.
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2015 |
Jan
(1) |
Feb
(2) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Jake F. <ja...@fe...> - 2017-09-21 00:10:43
|
Hi all, I came across CPIP in search of an existing C/C++ preprocessor written in python for my own project. It looks like CPIP hasn't seen development for some time, at least on sourceforge. Is there a current location where it's being developed, and if so, what is it? Thanks, Jake Fenton |
|
From: Bengt G. <Ben...@co...> - 2015-03-27 11:07:48
|
I finally came around to testing your annotateLineFile feature. Unfortunately it does not do what I want. You produce some special
Directives intended for the post-cpp steps of gcc, I believe. But I want to send my output to another compiler which does not understand this, so I need it
to output #line directives instead:
#line <lineno> "<filename>"
I made a crude patch to fix this, but you may want to improve on it or maybe support both modes. I assume that post-cpp gcc does not accept #line so in some cases that mode may also be of value. Another improvement would be to not output the filename itself if it didn't change (but I don't see how this would happen in this situation, really). I'm guessing your "flags" could be of help there, but this is not essential so I won't delve into it.
-----Ursprungligt meddelande-----
Från: cpi...@li... [mailto:cpi...@li...]
Skickat: den 2 mars 2015 15:36
Till: cpi...@li...
Ämne: Cpip-develop Digest, Vol 2, Issue 1
Send Cpip-develop mailing list submissions to
cpi...@li...
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/cpip-develop
or, via email, send a message with subject or body 'help' to
cpi...@li...
You can reach the person managing the list at
cpi...@li...
When replying, please edit your Subject line so it is more specific than "Re: Contents of Cpip-develop digest..."
Today's Topics:
1. #line and #pragma issues (Bengt Gustafsson)
2. Re: #line and #pragma issues (cpip cpip)
3. Re: #line and #pragma issues (cpip cpip)
----------------------------------------------------------------------
Message: 1
Date: Thu, 15 Jan 2015 16:50:25 +0100
From: Bengt Gustafsson <Ben...@co...>
Subject: [Cpip-develop] #line and #pragma issues
To: "cpi...@li..."
<cpi...@li...>
Message-ID: <AE21E26C07E9A148A12EE28ED306A2DC467AF8B480@cvs01>
Content-Type: text/plain; charset="us-ascii"
Hi!
I am using the cpip module in a situation where I need to first preprocess, then massage the preprocessed code a bit and finally send the resulting source code off to the "real" compiler.
The cpip module was really easy to get working but I have two problems, listed below.
One is that the original source code contains #pragma directives. I want these to go right through the preprocessing. While it is possible to install a pragma handler it does not seem to be possible to avoid an endless loop if I just send the pragma back to the source stream. I would like a possibility to block further preprocessing of whatever the pragma() function returns. Alternatively and simpler in my case another callback, say keep() which if it exists and returns true moves the entire pragma line to the output stream automatically.
Another problem is that if I get an error in the final compilation step I won't know what the original line number is or which include file a particular line comes from. With other preprocessors the output stream is usually filled with #line directives which the compiler uses to make sure error messages are appointed to the right line in the original source even if the preprocessor is run as a separate step. I would like an option to generate #line directives in the output file!
Best Regards,
Bengt Gustafsson
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Thu, 26 Feb 2015 13:31:30 +0000
From: cpip cpip <cp...@gm...>
Subject: Re: [Cpip-develop] #line and #pragma issues
To: Bengt Gustafsson <Ben...@co...>
Cc: "cpi...@li..."
<cpi...@li...>
Message-ID:
<CAFvR71cSXT0i+8Nk8sB9N-J=vnK...@ma...>
Content-Type: text/plain; charset="utf-8"
Hi Bengt,
Sorry for the delay, I have been snowed under recently and neglecting CPIP!
These are great ideas, I have already implemented the Pragma one in the SF main branch. You now construct a PpLexer with a (just added)
PragmaHandler.PragmaHandlerEcho() like this:
myLexer = PpLexer.PpLexer(
'hello.c',
CppIncludeStringIO([], [], myStr, {}),
pragmaHandler=PragmaHandler.PragmaHandlerEcho(),
)
All pragma statments are now preserved in the output.
As for the line number/file idea, I have partially implemented and should finish it tonight. or at the weekend.
I hope CPIP is being useful!
Thanks,
Paul.
On Thu, Jan 15, 2015 at 3:50 PM, Bengt Gustafsson < Ben...@co...> wrote:
> Hi!
>
>
>
> I am using the cpip module in a situation where I need to first
> preprocess, then massage the preprocessed code a bit and finally send
> the resulting source code off to the ?real? compiler.
>
>
>
> The cpip module was really easy to get working but I have two
> problems, listed below.
>
>
>
> One is that the original source code contains #pragma directives. I
> want these to go right through the preprocessing. While it is possible
> to install a pragma handler it does not seem to be possible to avoid
> an endless loop if
>
> I just send the pragma back to the source stream. I would like a
> possibility to block further preprocessing of whatever the pragma()
> function returns. Alternatively and simpler in my case another
> callback, say keep() which if it exists and returns true moves the
> entire pragma line to the output stream automatically.
>
>
>
> Another problem is that if I get an error in the final compilation
> step I won?t know what the original line number is or which include
> file a particular line comes from. With other preprocessors the output
> stream is usually filled with #line directives which the compiler uses
> to make sure error messages are appointed to the right line in the
> original source even if the preprocessor is run as a separate step. I
> would like an option to generate #line directives in the output file!
>
>
>
> Best Regards,
>
> Bengt Gustafsson
>
>
>
>
> ----------------------------------------------------------------------
> -------- New Year. New Location. New Benefits. New Data Center in
> Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Cpip-develop mailing list
> Cpi...@li...
> https://lists.sourceforge.net/lists/listinfo/cpip-develop
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Fri, 27 Feb 2015 08:46:03 +0000
From: cpip cpip <cp...@gm...>
Subject: Re: [Cpip-develop] #line and #pragma issues
To: Bengt Gustafsson <Ben...@co...>
Cc: "cpi...@li..."
<cpi...@li...>
Message-ID:
<CAF...@ma...>
Content-Type: text/plain; charset="utf-8"
Hi Bengt,
The fix for emitting line/file information is now in on the tip. Just create the PpLexer with an additional flag "annotateLineFile" set to True,
thus:
myLexer = PpLexer.PpLexer(..., annotateLineFile=True)
Regards,
Paul Ross.
On Thu, Feb 26, 2015 at 1:31 PM, cpip cpip <cp...@gm...> wrote:
> Hi Bengt,
>
> Sorry for the delay, I have been snowed under recently and neglecting CPIP!
>
> These are great ideas, I have already implemented the Pragma one in
> the SF main branch. You now construct a PpLexer with a (just added)
> PragmaHandler.PragmaHandlerEcho() like this:
>
> myLexer = PpLexer.PpLexer(
> 'hello.c',
> CppIncludeStringIO([], [], myStr, {}),
> pragmaHandler=PragmaHandler.PragmaHandlerEcho(),
> )
>
> All pragma statments are now preserved in the output.
>
> As for the line number/file idea, I have partially implemented and
> should finish it tonight. or at the weekend.
>
> I hope CPIP is being useful!
>
> Thanks,
>
> Paul.
>
>
>
>
> On Thu, Jan 15, 2015 at 3:50 PM, Bengt Gustafsson <
> Ben...@co...> wrote:
>
>> Hi!
>>
>>
>>
>> I am using the cpip module in a situation where I need to first
>> preprocess, then massage the preprocessed code a bit and finally send
>> the resulting source code off to the ?real? compiler.
>>
>>
>>
>> The cpip module was really easy to get working but I have two
>> problems, listed below.
>>
>>
>>
>> One is that the original source code contains #pragma directives. I
>> want these to go right through the preprocessing. While it is
>> possible to install a pragma handler it does not seem to be possible
>> to avoid an endless loop if
>>
>> I just send the pragma back to the source stream. I would like a
>> possibility to block further preprocessing of whatever the pragma()
>> function returns. Alternatively and simpler in my case another
>> callback, say keep() which if it exists and returns true moves the
>> entire pragma line to the output stream automatically.
>>
>>
>>
>> Another problem is that if I get an error in the final compilation
>> step I won?t know what the original line number is or which include
>> file a particular line comes from. With other preprocessors the
>> output stream is usually filled with #line directives which the
>> compiler uses to make sure error messages are appointed to the right
>> line in the original source even if the preprocessor is run as a
>> separate step. I would like an option to generate #line directives in the output file!
>>
>>
>>
>> Best Regards,
>>
>> Bengt Gustafsson
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> --------- New Year. New Location. New Benefits. New Data Center in
>> Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Cpip-develop mailing list
>> Cpi...@li...
>> https://lists.sourceforge.net/lists/listinfo/cpip-develop
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
------------------------------
_______________________________________________
Cpip-develop mailing list
Cpi...@li...
https://lists.sourceforge.net/lists/listinfo/cpip-develop
End of Cpip-develop Digest, Vol 2, Issue 1
******************************************
|
|
From: Bengt G. <Ben...@co...> - 2015-03-09 10:44:43
|
I had to add a u before the "#pragma%s" on the very last line of pragmahandler.py to get it to work on python 2.x which we still use for some reason. |
|
From: Bengt G. <Ben...@co...> - 2015-03-09 09:21:13
|
Hi Paul, I was giving up on anybody monitoring this list so I made a patch myself for the #pragma issue. I will probably change over to using your version now that it exists, but nevertheless here is the patch file for your reference. When it comes to the #line issue I was ignoring error message line number mismatches as it was a little too hard to figure out how to patch CPIP up to generate #line directives. Now that you have done it I will make sure to put it to use. Thanks for the effort! Bengt |
|
From: cpip c. <cp...@gm...> - 2015-02-27 08:46:11
|
Hi Bengt,
The fix for emitting line/file information is now in on the tip. Just
create the PpLexer with an additional flag "annotateLineFile" set to True,
thus:
myLexer = PpLexer.PpLexer(..., annotateLineFile=True)
Regards,
Paul Ross.
On Thu, Feb 26, 2015 at 1:31 PM, cpip cpip <cp...@gm...> wrote:
> Hi Bengt,
>
> Sorry for the delay, I have been snowed under recently and neglecting CPIP!
>
> These are great ideas, I have already implemented the Pragma one in the SF
> main branch. You now construct a PpLexer with a (just added)
> PragmaHandler.PragmaHandlerEcho() like this:
>
> myLexer = PpLexer.PpLexer(
> 'hello.c',
> CppIncludeStringIO([], [], myStr, {}),
> pragmaHandler=PragmaHandler.PragmaHandlerEcho(),
> )
>
> All pragma statments are now preserved in the output.
>
> As for the line number/file idea, I have partially implemented and should
> finish it tonight. or at the weekend.
>
> I hope CPIP is being useful!
>
> Thanks,
>
> Paul.
>
>
>
>
> On Thu, Jan 15, 2015 at 3:50 PM, Bengt Gustafsson <
> Ben...@co...> wrote:
>
>> Hi!
>>
>>
>>
>> I am using the cpip module in a situation where I need to first
>> preprocess, then massage the preprocessed code a bit and finally send the
>> resulting source code off to the “real” compiler.
>>
>>
>>
>> The cpip module was really easy to get working but I have two problems,
>> listed below.
>>
>>
>>
>> One is that the original source code contains #pragma directives. I want
>> these to go right through the preprocessing. While it is possible to
>> install a pragma handler it does not seem to be possible to avoid an
>> endless loop if
>>
>> I just send the pragma back to the source stream. I would like a
>> possibility to block further preprocessing of whatever the pragma()
>> function returns. Alternatively and simpler in my case another callback,
>> say keep() which if it exists and returns true moves the entire pragma line
>> to the output stream automatically.
>>
>>
>>
>> Another problem is that if I get an error in the final compilation step I
>> won’t know what the original line number is or which include file a
>> particular line comes from. With other preprocessors the output stream is
>> usually filled with #line directives which the compiler uses to make sure
>> error messages are appointed to the right line in the original source even
>> if the preprocessor is run as a separate step. I would like an option to
>> generate #line directives in the output file!
>>
>>
>>
>> Best Regards,
>>
>> Bengt Gustafsson
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Cpip-develop mailing list
>> Cpi...@li...
>> https://lists.sourceforge.net/lists/listinfo/cpip-develop
>>
>>
>
|
|
From: cpip c. <cp...@gm...> - 2015-02-26 13:31:37
|
Hi Bengt,
Sorry for the delay, I have been snowed under recently and neglecting CPIP!
These are great ideas, I have already implemented the Pragma one in the SF
main branch. You now construct a PpLexer with a (just added)
PragmaHandler.PragmaHandlerEcho() like this:
myLexer = PpLexer.PpLexer(
'hello.c',
CppIncludeStringIO([], [], myStr, {}),
pragmaHandler=PragmaHandler.PragmaHandlerEcho(),
)
All pragma statments are now preserved in the output.
As for the line number/file idea, I have partially implemented and should
finish it tonight. or at the weekend.
I hope CPIP is being useful!
Thanks,
Paul.
On Thu, Jan 15, 2015 at 3:50 PM, Bengt Gustafsson <
Ben...@co...> wrote:
> Hi!
>
>
>
> I am using the cpip module in a situation where I need to first
> preprocess, then massage the preprocessed code a bit and finally send the
> resulting source code off to the “real” compiler.
>
>
>
> The cpip module was really easy to get working but I have two problems,
> listed below.
>
>
>
> One is that the original source code contains #pragma directives. I want
> these to go right through the preprocessing. While it is possible to
> install a pragma handler it does not seem to be possible to avoid an
> endless loop if
>
> I just send the pragma back to the source stream. I would like a
> possibility to block further preprocessing of whatever the pragma()
> function returns. Alternatively and simpler in my case another callback,
> say keep() which if it exists and returns true moves the entire pragma line
> to the output stream automatically.
>
>
>
> Another problem is that if I get an error in the final compilation step I
> won’t know what the original line number is or which include file a
> particular line comes from. With other preprocessors the output stream is
> usually filled with #line directives which the compiler uses to make sure
> error messages are appointed to the right line in the original source even
> if the preprocessor is run as a separate step. I would like an option to
> generate #line directives in the output file!
>
>
>
> Best Regards,
>
> Bengt Gustafsson
>
>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Cpip-develop mailing list
> Cpi...@li...
> https://lists.sourceforge.net/lists/listinfo/cpip-develop
>
>
|
|
From: Bengt G. <Ben...@co...> - 2015-01-15 15:50:36
|
Hi! I am using the cpip module in a situation where I need to first preprocess, then massage the preprocessed code a bit and finally send the resulting source code off to the "real" compiler. The cpip module was really easy to get working but I have two problems, listed below. One is that the original source code contains #pragma directives. I want these to go right through the preprocessing. While it is possible to install a pragma handler it does not seem to be possible to avoid an endless loop if I just send the pragma back to the source stream. I would like a possibility to block further preprocessing of whatever the pragma() function returns. Alternatively and simpler in my case another callback, say keep() which if it exists and returns true moves the entire pragma line to the output stream automatically. Another problem is that if I get an error in the final compilation step I won't know what the original line number is or which include file a particular line comes from. With other preprocessors the output stream is usually filled with #line directives which the compiler uses to make sure error messages are appointed to the right line in the original source even if the preprocessor is run as a separate step. I would like an option to generate #line directives in the output file! Best Regards, Bengt Gustafsson |
|
From: Engelen, C.P.M. v. (Chris) <chr...@po...> - 2014-10-07 10:06:13
|
Paul, Thanks for the support, Today I've again spent some time on the problem with cpip. The problem is that on my RedHat system (Linux itiu08 2.6.32-431.23.3.el6.x86_64 #1 SMP Wed Jul 16 06:12:23 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux) there is no libc or glibc directory, and that file shlib-compat.h cannot be found anywhere on the system (I searched as user root with find from the root node, "/", to be sure). What I do not understand is that cpip does not give an error for not finding file shlib-compat.h, but does give the python error on processing SHLIB_COMPAT, because the include of file shlib-compat.h and the call to macro SHLIB_COMPAT are combine in file /usr/include/libio.h in the following way: # if __GNUC__ >= 2 /* While compiling glibc we have to handle compatibility with very old versions. */ # if defined _LIBC && defined SHARED # include <shlib-compat.h> # if SHLIB_COMPAT (libc, GLIBC_2_0, GLIBC_2_1) # define _IO_fwide_maybe_incompatible \ (__builtin_expect (&_IO_stdin_used == NULL, 0)) extern const int _IO_stdin_used; weak_extern (_IO_stdin_used); # endif # endif So cpip does not give an error for not finding shlib-compat.h, but does give an error for not being able to process SHLIB_COMPAT? This looks like a bug to me. As a workaround: is there an RPM which I should install which holds the libc or glibc include dirs? Met vriendelijke groet, Chris van Engelen Software developer Politie | IV-organisatie | Divisie MDC | GMS Odijkerweg 25, 3972 NE Driebergen Postbus 238, 3970 AE Driebergen M 06 11956342 T 088 6620049 ________________________________ Van: cpip cpip [mailto:cp...@go...] Verzonden: zondag 5 oktober 2014 22:17 Aan: Engelen, C.P.M. van (Chris) CC: cpi...@li... Onderwerp: Re: [Cpip-develop] CPIPMain.py crash on actual code Hi Chris, Did this work for you? Do you need any more help? Paul. On Wed, Oct 1, 2014 at 12:02 PM, cpip cpip <cp...@go...<mailto:cp...@go...>> wrote: Hi Chris, You need to provide CPIP with the location of the libc source code. The problem is that CPIP can not see the definition of the macro SHLIB_COMPAT. Undefined macros are treated as 0 as per the standard. You can provide a definition by using -D on the command line but the better idea is configure CPIP so it can find one in your source. Googling around suggests that SHLIB_COMPAT is defined in libc/include/shlib-compat.h or glibc/include/shlib-compat.h and I notice that CPIP is complaining earlier with this error: ERROR <gnu/stubs-32.h>: No such file or directory This also suggests CPIP can not find the libc source. You need to add the path to this (and any other) include with the -J option and that will allow CPIP to find the libc source. I think this SO answer<http://stackoverflow.com/questions/7412548/error-gnu-stubs-32-h-no-such-file-or-directory-while-compiling-nachos-source> might be relevant. I realise the CPIP could make this clearer, I'll work on that. Let me know how you get on. Cheers, Paul. On Tue, Sep 30, 2014 at 2:56 PM, Engelen, C.P.M. van (Chris) <chr...@po...<mailto:chr...@po...>> wrote: After reading the article about CPIP in InfoWorld (via the link provided by the CodeProject news letter), I got interested and decided to give it a try. After installing CPIP beta_02_2014-09-23-1659 in a Linux REDHAT 2.6.32-431.23.3.el6.x86_64 machine, I was able to successfully run CPIPMain om the main.cpp program in the demo directory., using python 2.7.8. However, when trying CPIPMain on an actual cpp source file, it ran about a minute on 100% CPU, then crashed with the following output: cvengel@itiu08 [15:44:15]> python2.7 /opt/CPIP/beta_02/cpip/CPIPMain.py -l 20 -p -o /home/cvengel/temp/CPIP/test/ggk -D __USE_STD_IOSTREAM -D _DEBUG -D _TRACE -D DONT_INCLUDETCL -D ACE_NDEBUG -J /usr/include -J /usr/include/c++/4.4.4 -J /usr/include/c++/4.4.4/x86_64-redhat-linux -J /usr/lib64/gcc/i686-pc-mingw32/4.4.6/include -I .. -I /home/cvengel/include -I /home/cvengel/workdir/gmslib/src -J /home/cvengel/workdir/gmslib/src/include -J /home/cvengel/workdir/gmslib/src/GmsApi -I . -J /usr/gmsdev/ACE/ACE_wrappers -J /home/cvengel/workdir/xerces-c-3.1.1/src -I /opt/ActiveTcl-8.4/include /home/cvengel/workdir/gmsapp/src/ggk/GgkInitialisatie.cpp 2014-09-30 15:44:51,396 INFO preprocessFileToOutput(): /home/cvengel/workdir/gmsapp/src/ggk/GgkInitialisatie.cpp 2014-09-30 15:44:51,397 INFO TU in HTML: 2014-09-30 15:44:51,397 INFO /home/cvengel/temp/CPIP/test/ggk/GgkInitialisatie.cpp.html 2014-09-30 15:44:51,901 ERROR <gnu/stubs-32.h>: No such file or directory at line=8, col=1 of file "/usr/include/gnu/stubs.h" Traceback (most recent call last): File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 1079, in <module> sys.exit(main()) File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 1050, in main preprocessFileToOutput(args[0], opts.output, jobSpec) File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 812, in preprocessFileToOutput incItuAnchors=True, File "/opt/CPIP/beta_02/cpip/Tu2Html.py", line 167, in processTuToHtml for t in theLex.ppTokens(incWs=True, minWs=True, condLevel=theCondLevel): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 493, in ppTokens for aTok in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude for aTtt in self._genPpTokensRecursive(myGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive for aTtt in self._processCppDirective(myTtt, theGen): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective for aTok in mySubGenFn(theGen, myFlc): File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1041, in _cppIf myBool, myStr = self._retIfEvalAndTokens(theGen) File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 988, in _retIfEvalAndTokens self._fis.fileLineCol) File "/opt/CPIP/beta_02/cpip/core/CppDiagnostic.py", line 109, in undefined theLoc cpip.core.CppDiagnostic.ExceptionCppDiagnosticUndefined: Can not evaluate constant expression "SHLIB_COMPAT (libc, GLIBC_2_0, GLIBC_2_1)", error: Evaluation of " 0 (0, 0, 0) " gives error: 'int' object is not callable at line=512, col=1 of file "/usr/include/libio.h" I'm using python 2.7.8: Python 2.7.8 (default, Sep 30 2014, 15:04:29) [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2 Any suggestions? BTW: In the Unit Testing section the file name is incorrect, it should be in plural: core/test/UnitTests.py Met vriendelijke groet, Chris van Engelen Software developer Politie | IV-organisatie | Divisie MDC | GMS Odijkerweg 25, 3972 NE Driebergen Postbus 238, 3970 AE Driebergen M 06 11956342 T 088 6620049 ------------------------- Disclaimer ---------------------------- De informatie verzonden met dit e-mailbericht (en bijlagen) is uitsluitend bestemd voor de geadresseerde(n) en zij die van de geadresseerde(n) toestemming kregen dit bericht te lezen. Kennisneming door anderen is niet toegestaan. De informatie in dit e-mailbericht (en bijlagen) kan vertrouwelijk van aard zijn en binnen het bereik van een geheimhoudingsplicht en/of een verschoningsrecht vallen. Indien dit e-mailbericht niet voor u bestemd is, wordt u verzocht de afzender daarover onmiddellijk te informeren en het e-mailbericht (en bijlagen) te vernietigen. ----------------------------------------------------------------- ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Cpip-develop mailing list Cpi...@li...<mailto:Cpi...@li...> https://lists.sourceforge.net/lists/listinfo/cpip-develop ------------------------- Disclaimer ---------------------------- De informatie verzonden met dit e-mailbericht (en bijlagen) is uitsluitend bestemd voor de geadresseerde(n) en zij die van de geadresseerde(n) toestemming kregen dit bericht te lezen. Kennisneming door anderen is niet toegestaan. De informatie in dit e-mailbericht (en bijlagen) kan vertrouwelijk van aard zijn en binnen het bereik van een geheimhoudingsplicht en/of een verschoningsrecht vallen. Indien dit e-mailbericht niet voor u bestemd is, wordt u verzocht de afzender daarover onmiddellijk te informeren en het e-mailbericht (en bijlagen) te vernietigen. ----------------------------------------------------------------- |
|
From: cpip c. <cp...@go...> - 2014-10-05 20:17:10
|
Hi Chris, Did this work for you? Do you need any more help? Paul. On Wed, Oct 1, 2014 at 12:02 PM, cpip cpip <cp...@go...> wrote: > > Hi Chris, > > You need to provide CPIP with the location of the libc source code. The > problem is that CPIP can not see the definition of the macro SHLIB_COMPAT. > Undefined macros are treated as 0 as per the standard. > > You can provide a definition by using -D on the command line but the > better idea is configure CPIP so it can find one in your source. Googling > around suggests that SHLIB_COMPAT is defined in libc/include/shlib-compat.h > or glibc/include/shlib-compat.h and I notice that CPIP is complaining > earlier with this error: > ERROR <gnu/stubs-32.h>: No such file or directory > > This also suggests CPIP can not find the libc source. You need to add the > path to this (and any other) include with the -J option and that will allow > CPIP to find the libc source. I think this SO answer > <http://stackoverflow.com/questions/7412548/error-gnu-stubs-32-h-no-such-file-or-directory-while-compiling-nachos-source> > might be relevant. > > I realise the CPIP could make this clearer, I'll work on that. > > Let me know how you get on. > > Cheers, > > Paul. > > > On Tue, Sep 30, 2014 at 2:56 PM, Engelen, C.P.M. van (Chris) < > chr...@po...> wrote: > >> After reading the article about CPIP in InfoWorld (via the link >> provided by the CodeProject news letter), I got interested and decided to >> give it a try. >> >> After installing CPIP beta_02_2014-09-23-1659 in a Linux REDHAT >> 2.6.32-431.23.3.el6.x86_64 machine, I was able to successfully run CPIPMain >> om the main.cpp program in the demo directory., using python 2.7.8. >> However, when trying CPIPMain on an actual cpp source file, it ran about a >> minute on 100% CPU, then crashed with the following output: >> >> cvengel@itiu08 [15:44:15]> python2.7 /opt/CPIP/beta_02/cpip/CPIPMain.py >> -l 20 -p -o /home/cvengel/temp/CPIP/test/ggk -D __USE_STD_IOSTREAM -D >> _DEBUG -D _TRACE -D DONT_INCLUDETCL -D ACE_NDEBUG -J /usr/include -J >> /usr/include/c++/4.4.4 -J /usr/include/c++/4.4.4/x86_64-redhat-linux -J >> /usr/lib64/gcc/i686-pc-mingw32/4.4.6/include -I .. -I >> /home/cvengel/include -I /home/cvengel/workdir/gmslib/src -J >> /home/cvengel/workdir/gmslib/src/include -J >> /home/cvengel/workdir/gmslib/src/GmsApi -I . -J >> /usr/gmsdev/ACE/ACE_wrappers -J /home/cvengel/workdir/xerces-c-3.1.1/src -I >> /opt/ActiveTcl-8.4/include >> /home/cvengel/workdir/gmsapp/src/ggk/GgkInitialisatie.cpp >> 2014-09-30 15:44:51,396 INFO preprocessFileToOutput(): >> /home/cvengel/workdir/gmsapp/src/ggk/GgkInitialisatie.cpp >> 2014-09-30 15:44:51,397 INFO TU in HTML: >> 2014-09-30 15:44:51,397 INFO >> /home/cvengel/temp/CPIP/test/ggk/GgkInitialisatie.cpp.html >> 2014-09-30 15:44:51,901 ERROR <gnu/stubs-32.h>: No such file or >> directory at line=8, col=1 of file "/usr/include/gnu/stubs.h" >> Traceback (most recent call last): >> File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 1079, in <module> >> sys.exit(main()) >> File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 1050, in main >> preprocessFileToOutput(args[0], opts.output, jobSpec) >> File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 812, in >> preprocessFileToOutput >> incItuAnchors=True, >> File "/opt/CPIP/beta_02/cpip/Tu2Html.py", line 167, in processTuToHtml >> for t in theLex.ppTokens(incWs=True, minWs=True, >> condLevel=theCondLevel): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 493, in ppTokens >> for aTok in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude >> for aTtt in self._genPpTokensRecursive(myGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in >> _genPpTokensRecursive >> for aTtt in self._processCppDirective(myTtt, theGen): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in >> _processCppDirective >> for aTok in mySubGenFn(theGen, myFlc): >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1041, in _cppIf >> myBool, myStr = self._retIfEvalAndTokens(theGen) >> File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 988, in >> _retIfEvalAndTokens >> self._fis.fileLineCol) >> File "/opt/CPIP/beta_02/cpip/core/CppDiagnostic.py", line 109, in >> undefined >> theLoc >> cpip.core.CppDiagnostic.ExceptionCppDiagnosticUndefined: Can not evaluate >> constant expression "SHLIB_COMPAT (libc, GLIBC_2_0, GLIBC_2_1)", error: >> Evaluation of " 0 (0, 0, 0) " gives error: 'int' object is not callable at >> line=512, col=1 of file "/usr/include/libio.h" >> >> I'm using python 2.7.8: >> Python 2.7.8 (default, Sep 30 2014, 15:04:29) >> [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2 >> >> Any suggestions? >> >> BTW: In the Unit Testing section the file name is incorrect, it should be >> in plural: *core/test/UnitTest**s**.py* >> >> Met vriendelijke groet, >> >> *Chris van Engelen *Software developer >> >> Politie | IV-organisatie | Divisie MDC | GMS >> Odijkerweg 25, 3972 NE Driebergen >> Postbus 238, 3970 AE Driebergen >> M 06 11956342 >> T 088 6620049 >> >> ------------------------- Disclaimer ---------------------------- De >> informatie verzonden met dit e-mailbericht (en bijlagen) is uitsluitend >> bestemd voor de geadresseerde(n) en zij die van de geadresseerde(n) >> toestemming kregen dit bericht te lezen. Kennisneming door anderen is niet >> toegestaan. De informatie in dit e-mailbericht (en bijlagen) kan >> vertrouwelijk van aard zijn en binnen het bereik van een >> geheimhoudingsplicht en/of een verschoningsrecht vallen. Indien dit >> e-mailbericht niet voor u bestemd is, wordt u verzocht de afzender daarover >> onmiddellijk te informeren en het e-mailbericht (en bijlagen) te >> vernietigen. >> ----------------------------------------------------------------- >> >> >> ------------------------------------------------------------------------------ >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >> >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >> _______________________________________________ >> Cpip-develop mailing list >> Cpi...@li... >> https://lists.sourceforge.net/lists/listinfo/cpip-develop >> >> > |
|
From: cpip c. <cp...@go...> - 2014-10-01 11:02:16
|
Hi Chris, You need to provide CPIP with the location of the libc source code. The problem is that CPIP can not see the definition of the macro SHLIB_COMPAT. Undefined macros are treated as 0 as per the standard. You can provide a definition by using -D on the command line but the better idea is configure CPIP so it can find one in your source. Googling around suggests that SHLIB_COMPAT is defined in libc/include/shlib-compat.h or glibc/include/shlib-compat.h and I notice that CPIP is complaining earlier with this error: ERROR <gnu/stubs-32.h>: No such file or directory This also suggests CPIP can not find the libc source. You need to add the path to this (and any other) include with the -J option and that will allow CPIP to find the libc source. I think this SO answer <http://stackoverflow.com/questions/7412548/error-gnu-stubs-32-h-no-such-file-or-directory-while-compiling-nachos-source> might be relevant. I realise the CPIP could make this clearer, I'll work on that. Let me know how you get on. Cheers, Paul. On Tue, Sep 30, 2014 at 2:56 PM, Engelen, C.P.M. van (Chris) < chr...@po...> wrote: > After reading the article about CPIP in InfoWorld (via the link provided > by the CodeProject news letter), I got interested and decided to give it a > try. > > After installing CPIP beta_02_2014-09-23-1659 in a Linux REDHAT > 2.6.32-431.23.3.el6.x86_64 machine, I was able to successfully run CPIPMain > om the main.cpp program in the demo directory., using python 2.7.8. > However, when trying CPIPMain on an actual cpp source file, it ran about a > minute on 100% CPU, then crashed with the following output: > > cvengel@itiu08 [15:44:15]> python2.7 /opt/CPIP/beta_02/cpip/CPIPMain.py > -l 20 -p -o /home/cvengel/temp/CPIP/test/ggk -D __USE_STD_IOSTREAM -D > _DEBUG -D _TRACE -D DONT_INCLUDETCL -D ACE_NDEBUG -J /usr/include -J > /usr/include/c++/4.4.4 -J /usr/include/c++/4.4.4/x86_64-redhat-linux -J > /usr/lib64/gcc/i686-pc-mingw32/4.4.6/include -I .. -I > /home/cvengel/include -I /home/cvengel/workdir/gmslib/src -J > /home/cvengel/workdir/gmslib/src/include -J > /home/cvengel/workdir/gmslib/src/GmsApi -I . -J > /usr/gmsdev/ACE/ACE_wrappers -J /home/cvengel/workdir/xerces-c-3.1.1/src -I > /opt/ActiveTcl-8.4/include > /home/cvengel/workdir/gmsapp/src/ggk/GgkInitialisatie.cpp > 2014-09-30 15:44:51,396 INFO preprocessFileToOutput(): > /home/cvengel/workdir/gmsapp/src/ggk/GgkInitialisatie.cpp > 2014-09-30 15:44:51,397 INFO TU in HTML: > 2014-09-30 15:44:51,397 INFO > /home/cvengel/temp/CPIP/test/ggk/GgkInitialisatie.cpp.html > 2014-09-30 15:44:51,901 ERROR <gnu/stubs-32.h>: No such file or > directory at line=8, col=1 of file "/usr/include/gnu/stubs.h" > Traceback (most recent call last): > File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 1079, in <module> > sys.exit(main()) > File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 1050, in main > preprocessFileToOutput(args[0], opts.output, jobSpec) > File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 812, in > preprocessFileToOutput > incItuAnchors=True, > File "/opt/CPIP/beta_02/cpip/Tu2Html.py", line 167, in processTuToHtml > for t in theLex.ppTokens(incWs=True, minWs=True, > condLevel=theCondLevel): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 493, in ppTokens > for aTok in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude > for aTtt in self._genPpTokensRecursive(myGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in > _genPpTokensRecursive > for aTtt in self._processCppDirective(myTtt, theGen): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in > _processCppDirective > for aTok in mySubGenFn(theGen, myFlc): > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1041, in _cppIf > myBool, myStr = self._retIfEvalAndTokens(theGen) > File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 988, in > _retIfEvalAndTokens > self._fis.fileLineCol) > File "/opt/CPIP/beta_02/cpip/core/CppDiagnostic.py", line 109, in > undefined > theLoc > cpip.core.CppDiagnostic.ExceptionCppDiagnosticUndefined: Can not evaluate > constant expression "SHLIB_COMPAT (libc, GLIBC_2_0, GLIBC_2_1)", error: > Evaluation of " 0 (0, 0, 0) " gives error: 'int' object is not callable at > line=512, col=1 of file "/usr/include/libio.h" > > I'm using python 2.7.8: > Python 2.7.8 (default, Sep 30 2014, 15:04:29) > [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2 > > Any suggestions? > > BTW: In the Unit Testing section the file name is incorrect, it should be > in plural: *core/test/UnitTest**s**.py* > > Met vriendelijke groet, > > *Chris van Engelen *Software developer > > Politie | IV-organisatie | Divisie MDC | GMS > Odijkerweg 25, 3972 NE Driebergen > Postbus 238, 3970 AE Driebergen > M 06 11956342 > T 088 6620049 > > ------------------------- Disclaimer ---------------------------- De > informatie verzonden met dit e-mailbericht (en bijlagen) is uitsluitend > bestemd voor de geadresseerde(n) en zij die van de geadresseerde(n) > toestemming kregen dit bericht te lezen. Kennisneming door anderen is niet > toegestaan. De informatie in dit e-mailbericht (en bijlagen) kan > vertrouwelijk van aard zijn en binnen het bereik van een > geheimhoudingsplicht en/of een verschoningsrecht vallen. Indien dit > e-mailbericht niet voor u bestemd is, wordt u verzocht de afzender daarover > onmiddellijk te informeren en het e-mailbericht (en bijlagen) te > vernietigen. > ----------------------------------------------------------------- > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Cpip-develop mailing list > Cpi...@li... > https://lists.sourceforge.net/lists/listinfo/cpip-develop > > |
|
From: Engelen, C.P.M. v. (Chris) <chr...@po...> - 2014-09-30 14:32:05
|
After reading the article about CPIP in InfoWorld (via the link provided by the CodeProject news letter), I got interested and decided to give it a try.
After installing CPIP beta_02_2014-09-23-1659 in a Linux REDHAT 2.6.32-431.23.3.el6.x86_64 machine, I was able to successfully run CPIPMain om the main.cpp program in the demo directory., using python 2.7.8. However, when trying CPIPMain on an actual cpp source file, it ran about a minute on 100% CPU, then crashed with the following output:
cvengel@itiu08 [15:44:15]> python2.7 /opt/CPIP/beta_02/cpip/CPIPMain.py -l 20 -p -o /home/cvengel/temp/CPIP/test/ggk -D __USE_STD_IOSTREAM -D _DEBUG -D _TRACE -D DONT_INCLUDETCL -D ACE_NDEBUG -J /usr/include -J /usr/include/c++/4.4.4 -J /usr/include/c++/4.4.4/x86_64-redhat-linux -J /usr/lib64/gcc/i686-pc-mingw32/4.4.6/include -I .. -I /home/cvengel/include -I /home/cvengel/workdir/gmslib/src -J /home/cvengel/workdir/gmslib/src/include -J /home/cvengel/workdir/gmslib/src/GmsApi -I . -J /usr/gmsdev/ACE/ACE_wrappers -J /home/cvengel/workdir/xerces-c-3.1.1/src -I /opt/ActiveTcl-8.4/include /home/cvengel/workdir/gmsapp/src/ggk/GgkInitialisatie.cpp
2014-09-30 15:44:51,396 INFO preprocessFileToOutput(): /home/cvengel/workdir/gmsapp/src/ggk/GgkInitialisatie.cpp
2014-09-30 15:44:51,397 INFO TU in HTML:
2014-09-30 15:44:51,397 INFO /home/cvengel/temp/CPIP/test/ggk/GgkInitialisatie.cpp.html
2014-09-30 15:44:51,901 ERROR <gnu/stubs-32.h>: No such file or directory at line=8, col=1 of file "/usr/include/gnu/stubs.h"
Traceback (most recent call last):
File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 1079, in <module>
sys.exit(main())
File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 1050, in main
preprocessFileToOutput(args[0], opts.output, jobSpec)
File "/opt/CPIP/beta_02/cpip/CPIPMain.py", line 812, in preprocessFileToOutput
incItuAnchors=True,
File "/opt/CPIP/beta_02/cpip/Tu2Html.py", line 167, in processTuToHtml
for t in theLex.ppTokens(incWs=True, minWs=True, condLevel=theCondLevel):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 493, in ppTokens
for aTok in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1196, in _cppInclude
for aTtt in self._genPpTokensRecursive(myGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 558, in _genPpTokensRecursive
for aTtt in self._processCppDirective(myTtt, theGen):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 873, in _processCppDirective
for aTok in mySubGenFn(theGen, myFlc):
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 1041, in _cppIf
myBool, myStr = self._retIfEvalAndTokens(theGen)
File "/opt/CPIP/beta_02/cpip/core/PpLexer.py", line 988, in _retIfEvalAndTokens
self._fis.fileLineCol)
File "/opt/CPIP/beta_02/cpip/core/CppDiagnostic.py", line 109, in undefined
theLoc
cpip.core.CppDiagnostic.ExceptionCppDiagnosticUndefined: Can not evaluate constant expression "SHLIB_COMPAT (libc, GLIBC_2_0, GLIBC_2_1)", error: Evaluation of " 0 (0, 0, 0) " gives error: 'int' object is not callable at line=512, col=1 of file "/usr/include/libio.h"
I'm using python 2.7.8:
Python 2.7.8 (default, Sep 30 2014, 15:04:29)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2
Any suggestions?
BTW: In the Unit Testing section the file name is incorrect, it should be in plural: core/test/UnitTests.py
Met vriendelijke groet,
Chris van Engelen
Software developer
Politie | IV-organisatie | Divisie MDC | GMS
Odijkerweg 25, 3972 NE Driebergen
Postbus 238, 3970 AE Driebergen
M 06 11956342
T 088 6620049
------------------------- Disclaimer ---------------------------- De informatie verzonden met dit e-mailbericht (en bijlagen) is uitsluitend bestemd voor de geadresseerde(n) en zij die van de geadresseerde(n) toestemming kregen dit bericht te lezen. Kennisneming door anderen is niet toegestaan. De informatie in dit e-mailbericht (en bijlagen) kan vertrouwelijk van aard zijn en binnen het bereik van een geheimhoudingsplicht en/of een verschoningsrecht vallen. Indien dit e-mailbericht niet voor u bestemd is, wordt u verzocht de afzender daarover onmiddellijk te informeren en het e-mailbericht (en bijlagen) te vernietigen. -----------------------------------------------------------------
|
