Dear Andy:
The reason why I appended other option in CC is that I want to
load my defined feature under CIL. The problem is that the header
files can be found if the -D option make effect. Now the option under
Make does not function at all. But by mannual the same command is
executed CORRECTLY. I plan to change the cilly.pm under the directory
lib in CIL.
PANG Long
2010/1/6 Andrew Y. Yang <yuyan...@gmail.com>:
> I guess that using
> CC="/home/me/mywork/sca/compilertools/cil/cil-1.3.7/bin/cilly" shuould be
> fine to make CIL act as a C compiler
> If the header files cannot be added, you can modify the makefile a little
> bit to add the paths whether
> files such as sha.h can be found.
>
> On Tue, Jan 5, 2010 at 8:22 PM, pang long <hitpangl...@gmail.com> wrote:
>>
>> Dear Andy:
>> Thanks for ur reply. I have replaced the compiler with the perl
>> code cilly as following and then reports the error I mentioned in
>> prior message.
>> -----------------my cmd to replace with cilly-----------------
>> time -p make CC="/home/me/mywork/sca/compilertools/cil/cil-1.3.7/bin/cilly
>> --save-temps --doploutvaa -c -O1
>> --gcc=/home/me/mywork/gccs/installed/bin/gcc "
>> LD="/home/me/mywork/gccs/installed/bin/gcc" -i > make.log
>> 2>make.error
>> --------------------end------------------------------------------------
>> The option --gcc is pointed to my pass-added GCC version, which
>> doesn't matter for this problem. In my opinion, the problem is the
>> corresponding shell command that the perl cilly generates to pass the
>> preprocess parameters on to underlying preprocessor. The parameter
>> -DSHA1_HEADER='<'openssl/sha.h'>' does not make effect to replace the
>> macro definition in preprocessing .c file so that the underlying
>> preprocessor reports that error. BUT, I can directly execute the same
>> command recorded error reprot log file correctly. In my opinion, maybe
>> the reason is on the compatibility between the shell command generated
>> by cilly and the underlying shell. How to solve it? Do I explain
>> clearly?
>>
>> PANG Long
>>
>> 2010/1/6 Andrew Y. Yang <yuyan...@gmail.com>:
>> > Hi,
>> > I think that that you can replace the compiler that git-1.6.6's makefile
>> > uses with cilly. Then everything should be fine. Setting up the path
>> > correctly should solve the problem.
>> > -Andy
>> >
>> > On Tue, Jan 5, 2010 at 5:18 PM, pang long <hitpangl...@gmail.com> wrote:
>> >>
>> >> Dear
>> >> My Cil version is 1.3.7. I planned to analysis git-1.6.6 using my
>> >> own defined feature. The command line executed in Makefile is like the
>> >> following:
>> >> gcc -D_GNUCC -E -O1 -g -O2 -DTHREADED_DELTA_SEARCH
>> >> -DSHA1_HEADER='<'openssl/sha.h'>' -DNO_STRLCPY -DNO_MKSTEMPS -DCIL=1
>> >> fast-import.c -o ./fast-import.i
>> >> It reports the error under make:
>> >> In file included from builtin.h:6,
>> >> from fast-import.c:147:
>> >> cache.h:9:10: error: #include expects "FILENAME" or <FILENAME>
>> >> make: [fast-import.o] Error 1 (ignored)
>> >> But in shell, I directly copy-paste and execute the command,it
>> >> runs correctly. I was trying to locate the function generating the
>> >> option parameter in cilly perl code, but I failed.
>> >> How to handle the problem? Where is the exactly location to
>> >> process and generate the option parameter for GCC preprocess?
>> >>
>> >> Thanks in advance
>> >> PANG Long
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> This SF.Net email is sponsored by the Verizon Developer Community
>> >> Take advantage of Verizon's best-in-class app development support
>> >> A streamlined, 14 day to market process makes app distribution fast and
>> >> easy
>> >> Join now and get one step closer to millions of Verizon customers
>> >> http://p.sf.net/sfu/verizon-dev2dev
>> >> _______________________________________________
>> >> CIL-users mailing list
>> >> CIL-users@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/cil-users
>> >
>> >
>
>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
CIL-users mailing list
CIL-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cil-users
