CINT for embeded application

[Aki Niimura]

Hello everyone,

It is common to use C or C++ to write programs for embedded applications.
Now, I'm investigating if I can use CINT to remotely control the target device.

The challenge is that control registers (for writes) and status registers (for reads) are mapped to memory space and are accessed much like regular memory location.

#define REG_READ (a, val) ((val) = *(volatile UNIT32 *)(a))
#define REG_WRITE (a, val)  (*(volatile UNIT32 *)(a) = (val))

Of course, if I run a program that uses such register accesses from CINT, it spits out 'Segmentation violation'.

What I wanted to do is to route such pointer de-references to my routine so that they are fed to the target device.

Of course, CINT cannot tell which pointer de-reference is aimed for a target device and which one is for program itself.
So, only way I can tell is from the address value. I could create a list of address ranges so that if the address of the pointer is within the address ranges, then the pointer de-reference is aimed for accessing the target. Alternatively, pointer de-references that resulted in SEGV may be re-interpreted as pointers to registers in the target device.

Now CINT is a large and complex piece of software and I don't know if this kind of usage of CINT does make sense.
My questions are:
(1) Does anybody try a similar thing in the past? (So far, I couldn't find any)
(2) Is there any easy way to hook up my routine to CINT without modifying the CINT source code?
(3) If I need to modify the CINT, any suggestion where to dig?

Any info, feedback is greatly appreciated.

Best regards,
Aki Niimura

[Axel Naumann]

Hi,

if you have the reads and writes located (e.g. though a function or a
CPP macro like in your example) you could have a different definition
for local and remote. You could have the CPP macros you quoted as part
of the embedded application, and then e.g.

#ifdef EMBEDDED
# define REG_READ (a, val) ((val) = *(volatile UNIT32 *)(a))
# define REG_WRITE (a, val)  (*(volatile UNIT32 *)(a) = (val))
#else
# define REG_READ (a, val) ((val) = *(REMOTE_READ(a))
# define REG_WRITE (a, val)  (REMOTE_WRITE(a, val))
#endif

So then all that's left is the implementation of REMOTE_READ and
REMOTE_WRITE. If that doesn't work then I probably didn't understand the
problem well enough...

Cheers, Axel.


On 2009-02-04 20:08, Aki Niimura wrote:

> Hello everyone,
>
> It is common to use C or C++ to write programs for embedded applications.
> Now, I'm investigating if I can use CINT to remotely control the target
> device.
>
> The challenge is that control registers (for writes) and status
> registers (for reads) are mapped to memory space and are accessed much
> like regular memory location.
>
> #define REG_READ (a, val) ((val) = *(volatile UNIT32 *)(a))
> #define REG_WRITE (a, val)  (*(volatile UNIT32 *)(a) = (val))
>
> Of course, if I run a program that uses such register accesses from
> CINT, it spits out 'Segmentation violation'.
>
> What I wanted to do is to route such pointer de-references to my routine
> so that they are fed to the target device.
>
> Of course, CINT cannot tell which pointer de-reference is aimed for a
> target device and which one is for program itself.
> So, only way I can tell is from the address value. I could create a list
> of address ranges so that if the address of the pointer is within the
> address ranges, then the pointer de-reference is aimed for accessing the
> target. Alternatively, pointer de-references that resulted in SEGV may
> be re-interpreted as pointers to registers in the target device.
>
> Now CINT is a large and complex piece of software and I don't know if
> this kind of usage of CINT does make sense.
> My questions are:
> (1) Does anybody try a similar thing in the past? (So far, I couldn't
> find any)
> (2) Is there any easy way to hook up my routine to CINT without
> modifying the CINT source code?
> (3) If I need to modify the CINT, any suggestion where to dig?
>
> Any info, feedback is greatly appreciated.
>
> Best regards,
> Aki Niimura
>
>
>

[Aki Niimura]

Hello Axel,

Thank you for your prompt response to my question.
I think your approach, which I didn't think of, would work for most cases.
However, it would restrict the accesses to the registers to those via macros.
I was hoping that I could find a way to handle the issues in more generic way.
But the approach you presented is probably the most pragmatic way to deal with the challenge.

Thanks!,
Aki-

On Wed, Feb 4, 2009 at 2:01 PM, Axel Naumann <Axel.Naumann@...> wrote:

Hi,

if you have the reads and writes located (e.g. though a function or a
CPP macro like in your example) you could have a different definition
for local and remote. You could have the CPP macros you quoted as part
of the embedded application, and then e.g.

#ifdef EMBEDDED
# define REG_READ (a, val) ((val) = *(volatile UNIT32 *)(a))

# define REG_WRITE (a, val)  (*(volatile UNIT32 *)(a) = (val))

#else
# define REG_READ (a, val) ((val) = *(REMOTE_READ(a))
# define REG_WRITE (a, val)  (REMOTE_WRITE(a, val))
#endif

So then all that's left is the implementation of REMOTE_READ and
REMOTE_WRITE. If that doesn't work then I probably didn't understand the
problem well enough...

Cheers, Axel.

On 2009-02-04 20:08, Aki Niimura wrote:
> Hello everyone,
>
> It is common to use C or C++ to write programs for embedded applications.
> Now, I'm investigating if I can use CINT to remotely control the target
> device.
>
> The challenge is that control registers (for writes) and status
> registers (for reads) are mapped to memory space and are accessed much
> like regular memory location.
>
> #define REG_READ (a, val) ((val) = *(volatile UNIT32 *)(a))
> #define REG_WRITE (a, val)  (*(volatile UNIT32 *)(a) = (val))
>
> Of course, if I run a program that uses such register accesses from
> CINT, it spits out 'Segmentation violation'.
>
> What I wanted to do is to route such pointer de-references to my routine
> so that they are fed to the target device.
>
> Of course, CINT cannot tell which pointer de-reference is aimed for a
> target device and which one is for program itself.
> So, only way I can tell is from the address value. I could create a list
> of address ranges so that if the address of the pointer is within the
> address ranges, then the pointer de-reference is aimed for accessing the
> target. Alternatively, pointer de-references that resulted in SEGV may
> be re-interpreted as pointers to registers in the target device.
>
> Now CINT is a large and complex piece of software and I don't know if
> this kind of usage of CINT does make sense.
> My questions are:
> (1) Does anybody try a similar thing in the past? (So far, I couldn't
> find any)
> (2) Is there any easy way to hook up my routine to CINT without
> modifying the CINT source code?
> (3) If I need to modify the CINT, any suggestion where to dig?
>
> Any info, feedback is greatly appreciated.
>
> Best regards,
> Aki Niimura
>
>
>

[Philippe Canal]

Hi Aki,

 > I was hoping that I could find a way to handle the issues in more
generic way.

How do you handle this in compiled code? (i.e. have you been able to
remotely
control your device from a compiled C++?)

Cheers,
Philippe.

Aki Niimura wrote:

> Hello Axel,
>
> Thank you for your prompt response to my question.
> I think your approach, which I didn't think of, would work for most cases.
> However, it would restrict the accesses to the registers to those via
> macros.
> I was hoping that I could find a way to handle the issues in more
> generic way.
> But the approach you presented is probably the most pragmatic way to
> deal with the challenge.
>
> Thanks!,
> Aki-
>
> On Wed, Feb 4, 2009 at 2:01 PM, Axel Naumann <Axel.Naumann@...> wrote:
>
>     Hi,
>
>     if you have the reads and writes located (e.g. though a function or a
>     CPP macro like in your example) you could have a different definition
>     for local and remote. You could have the CPP macros you quoted as part
>     of the embedded application, and then e.g.
>
>     #ifdef EMBEDDED
>     # define REG_READ (a, val) ((val) = *(volatile UNIT32 *)(a))
>     # define REG_WRITE (a, val)  (*(volatile UNIT32 *)(a) = (val))
>     #else
>     # define REG_READ (a, val) ((val) = *(REMOTE_READ(a))
>     # define REG_WRITE (a, val)  (REMOTE_WRITE(a, val))
>     #endif
>
>     So then all that's left is the implementation of REMOTE_READ and
>     REMOTE_WRITE. If that doesn't work then I probably didn't
>     understand the
>     problem well enough...
>
>     Cheers, Axel.
>
>
>     On 2009-02-04 20:08, Aki Niimura wrote:
>     > Hello everyone,
>     >
>     > It is common to use C or C++ to write programs for embedded
>     applications.
>     > Now, I'm investigating if I can use CINT to remotely control the
>     target
>     > device.
>     >
>     > The challenge is that control registers (for writes) and status
>     > registers (for reads) are mapped to memory space and are
>     accessed much
>     > like regular memory location.
>     >
>     > #define REG_READ (a, val) ((val) = *(volatile UNIT32 *)(a))
>     > #define REG_WRITE (a, val)  (*(volatile UNIT32 *)(a) = (val))
>     >
>     > Of course, if I run a program that uses such register accesses from
>     > CINT, it spits out 'Segmentation violation'.
>     >
>     > What I wanted to do is to route such pointer de-references to my
>     routine
>     > so that they are fed to the target device.
>     >
>     > Of course, CINT cannot tell which pointer de-reference is aimed
>     for a
>     > target device and which one is for program itself.
>     > So, only way I can tell is from the address value. I could
>     create a list
>     > of address ranges so that if the address of the pointer is
>     within the
>     > address ranges, then the pointer de-reference is aimed for
>     accessing the
>     > target. Alternatively, pointer de-references that resulted in
>     SEGV may
>     > be re-interpreted as pointers to registers in the target device.
>     >
>     > Now CINT is a large and complex piece of software and I don't
>     know if
>     > this kind of usage of CINT does make sense.
>     > My questions are:
>     > (1) Does anybody try a similar thing in the past? (So far, I
>     couldn't
>     > find any)
>     > (2) Is there any easy way to hook up my routine to CINT without
>     > modifying the CINT source code?
>     > (3) If I need to modify the CINT, any suggestion where to dig?
>     >
>     > Any info, feedback is greatly appreciated.
>     >
>     > Best regards,
>     > Aki Niimura
>     >
>     >
>     >
>
>

[Dr. Prasad, B.V.L.S.]

Hi,

Compiling Cint on cygwin is giving these initial problems:

How to avoid this problem. can I get around with rmkdepend.exe ?
Since its showing undefined reference: some standard library is not being used.
I saw the source, it has ctype.h and stdlib.h included in one of the files.

The following is part of the error.  Seems some thing very basic, thought I could not
resolve.
any help is appreciatd. Thank you,
Prasad.

g++ -O2  tool/rmkdepend//cppsetup.o tool/rmkdepend//ifparser.o tool/rmkdepend//i
nclude.o tool/rmkdepend//main.o tool/rmkdepend//parse.o tool/rmkdepend//pr.o too
l/rmkdepend//mainroot.o -o tool/rmkdepend/rmkdepend.exe
tool/rmkdepend//cppsetup.o:cppsetup.c:(.text+0x162): undefined reference to `_is
defined'
tool/rmkdepend//cppsetup.o:cppsetup.c:(.text+0x28c): undefined reference to `_Pa
rseIfExpression'
tool/rmkdepend//ifparser.o: In function `parse_variable':
ifparser.c:(.text+0x11): undefined reference to `__ctype_b_loc'
tool/rmkdepend//ifparser.o: In function `parse_value':
ifparser.c:(.text+0xa9): undefined reference to `__ctype_b_loc'
ifparser.c:(.text+0x4bc): undefined reference to `strtol'
ifparser.c:(.text+0x52e): undefined reference to `strtol'
ifparser.c:(.text+0x5bb): undefined reference to `strtol'
tool/rmkdepend//ifparser.o: In function `parse_product':
ifparser.c:(.text+0x649): undefined reference to `__ctype_b_loc'
tool/rmkdepend//ifparser.o: In function `parse_sum':
ifparser.c:(.text+0x719): undefined reference to `__ctype_b_loc'
tool/rmkdepend//ifparser.o: In function `parse_shift':
ifparser.c:(.text+0x7a9): undefined reference to `__ctype_b_loc'
tool/rmkdepend//ifparser.o: In function `parse_inequality':
ifparser.c:(.text+0x839): undefined reference to `__ctype_b_loc'
tool/rmkdepend//ifparser.o: In function `parse_equality':
ifparser.c:(.text+0x939): undefined reference to `__ctype_b_loc'
tool/rmkdepend//ifparser.o:ifparser.c:(.text+0x9e9): more undefined references t
o `__ctype_b_loc' follow
tool/rmkdepend//include.o: In function `remove_dotdot':
include.c:(.text+0x237): undefined reference to `strcpy'
include.c:(.text+0x29e): undefined reference to `__stack_chk_fail'
tool/rmkdepend//include.o: In function `included_by':
include.c:(.text+0x33d): undefined reference to `realloc'
include.c:(.text+0x352): undefined reference to `realloc'
include.c:(.text+0x379): undefined reference to `strlen'
include.c:(.text+0x410): undefined reference to `malloc'
include.c:(.text+0x41e): undefined reference to `malloc'
tool/rmkdepend//include.o: In function `inc_path':
include.c:(.text+0x4bf): undefined reference to `strcmp'
include.c:(.text+0x52a): undefined reference to `sprintf'
include.c:(.text+0x551): undefined reference to `__xstat'
include.c:(.text+0x5a1): undefined reference to `__xstat'
include.c:(.text+0x5d7): undefined reference to `strlen'
include.c:(.text+0x61a): undefined reference to `strncpy'
include.c:(.text+0x630): undefined reference to `strcpy'
include.c:(.text+0x657): undefined reference to `__xstat'
include.c:(.text+0x6e5): undefined reference to `strcpy'
tool/rmkdepend//main.o: In function `warning1':
main.c:(.text+0x183): undefined reference to `stderr'
main.c:(.text+0x18b): undefined reference to `vfprintf'
tool/rmkdepend//main.o: In function `warning':
main.c:(.text+0x1c4): undefined reference to `stderr'
main.c:(.text+0x1cc): undefined reference to `fprintf'

[Axel Naumann]

Hi,

I cannot reproduce this problem; it works fine for me:

l/rmkdepend//pr.o tool/rmkdepend//mainroot.o -o tool/rmkdepend/rmkdepend.exe
cp -f build/Makefile Makefile
tool/rmkdepend/rmkdepend.exe -R -fcint7/main/G__setup.d -Y -w 1000 --
-O2    -DG__CYGWIN -DG__STD_EXCEPTION -DG__HAVE_CONFIG -DG__NOMAKEINFO
 -Icint7/inc -Icint7/src -Ireflex/inc -DG__CINTBODY -- cint7/main/G__setup.c
gcc -O2    -DG__CYGWIN -DG__STD_EXCEPTION -DG__HAVE_CONFIG
-DG__NOMAKEINFO   -Icint7/inc -Icint7/src -Ireflex/inc -DG__CINTBODY -c
cint7/main/G__setup.c -o cint7/main/G__setup.o

...

So my guess is that something is wrong with your cygwin installation.

Cheers, Axel.

Dr. Prasad, B.V.L.S. wrote:

> Hi,
>
> Compiling Cint on cygwin is giving these initial problems:
>
> How to avoid this problem. can I get around with rmkdepend.exe ?
> Since its showing undefined reference: some standard library is not being used.
> I saw the source, it has ctype.h and stdlib.h included in one of the files.
>
> The following is part of the error.  Seems some thing very basic, thought I could not
> resolve.
> any help is appreciatd. Thank you,
> Prasad.
>
> g++ -O2  tool/rmkdepend//cppsetup.o tool/rmkdepend//ifparser.o tool/rmkdepend//i
> nclude.o tool/rmkdepend//main.o tool/rmkdepend//parse.o tool/rmkdepend//pr.o too
> l/rmkdepend//mainroot.o -o tool/rmkdepend/rmkdepend.exe
> tool/rmkdepend//cppsetup.o:cppsetup.c:(.text+0x162): undefined reference to `_is
> defined'
> tool/rmkdepend//cppsetup.o:cppsetup.c:(.text+0x28c): undefined reference to `_Pa
> rseIfExpression'
> tool/rmkdepend//ifparser.o: In function `parse_variable':
> ifparser.c:(.text+0x11): undefined reference to `__ctype_b_loc'
> tool/rmkdepend//ifparser.o: In function `parse_value':
> ifparser.c:(.text+0xa9): undefined reference to `__ctype_b_loc'
> ifparser.c:(.text+0x4bc): undefined reference to `strtol'
> ifparser.c:(.text+0x52e): undefined reference to `strtol'
> ifparser.c:(.text+0x5bb): undefined reference to `strtol'
> tool/rmkdepend//ifparser.o: In function `parse_product':
> ifparser.c:(.text+0x649): undefined reference to `__ctype_b_loc'
> tool/rmkdepend//ifparser.o: In function `parse_sum':
> ifparser.c:(.text+0x719): undefined reference to `__ctype_b_loc'
> tool/rmkdepend//ifparser.o: In function `parse_shift':
> ifparser.c:(.text+0x7a9): undefined reference to `__ctype_b_loc'
> tool/rmkdepend//ifparser.o: In function `parse_inequality':
> ifparser.c:(.text+0x839): undefined reference to `__ctype_b_loc'
> tool/rmkdepend//ifparser.o: In function `parse_equality':
> ifparser.c:(.text+0x939): undefined reference to `__ctype_b_loc'
> tool/rmkdepend//ifparser.o:ifparser.c:(.text+0x9e9): more undefined references t
> o `__ctype_b_loc' follow
> tool/rmkdepend//include.o: In function `remove_dotdot':
> include.c:(.text+0x237): undefined reference to `strcpy'
> include.c:(.text+0x29e): undefined reference to `__stack_chk_fail'
> tool/rmkdepend//include.o: In function `included_by':
> include.c:(.text+0x33d): undefined reference to `realloc'
> include.c:(.text+0x352): undefined reference to `realloc'
> include.c:(.text+0x379): undefined reference to `strlen'
> include.c:(.text+0x410): undefined reference to `malloc'
> include.c:(.text+0x41e): undefined reference to `malloc'
> tool/rmkdepend//include.o: In function `inc_path':
> include.c:(.text+0x4bf): undefined reference to `strcmp'
> include.c:(.text+0x52a): undefined reference to `sprintf'
> include.c:(.text+0x551): undefined reference to `__xstat'
> include.c:(.text+0x5a1): undefined reference to `__xstat'
> include.c:(.text+0x5d7): undefined reference to `strlen'
> include.c:(.text+0x61a): undefined reference to `strncpy'
> include.c:(.text+0x630): undefined reference to `strcpy'
> include.c:(.text+0x657): undefined reference to `__xstat'
> include.c:(.text+0x6e5): undefined reference to `strcpy'
> tool/rmkdepend//main.o: In function `warning1':
> main.c:(.text+0x183): undefined reference to `stderr'
> main.c:(.text+0x18b): undefined reference to `vfprintf'
> tool/rmkdepend//main.o: In function `warning':
> main.c:(.text+0x1c4): undefined reference to `stderr'
> main.c:(.text+0x1cc): undefined reference to `fprintf'
>
>
>
>
>
>

[Dr. Prasad, B.V.L.S.]

Thank you for the comments.
I looked back into the code.

this time I did :  make clean.
then make.

This solved my problem.
Thank you once again.
Prasad.

[Dr. Prasad, B.V.L.S.]

Hi,

What mistake is happening from my side that I am unable to create a string.dll and all other STL dlls.
Here is the error message I am getting.  Same code works well in Linux.

I have also exported the CINTSYSDIR and LD_LIBRARY_PATH env. variables into the source file.
Still this doesnt work.

Here are some more details: I am using Vista Home Premium, Cygwin, g++ 3.4.4,

Thank you,
Prasad.
##########################################################################
# makecint : interpreter-compiler for cint (Windows Cygwin DLL version)
# Copyright(c) 1995~2007 Masaharu Goto. Mailing list: cint@...
##########################################################################
Run 'make -f Makestr' to compile the object
make[1]: Entering directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cin
t/cint/lib/dll_stl'
/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint/bin/cint.exe  -w2 -zstring
-nG__cpp_string.cxx  -D__MAKECINT__ -DG__MAKECINT  -c-1 -A -I/cygdrive/c/Users/a
nagha/OldBOSandOthers18Dec08/cint//cint/inc  -DG__CYGWIN -DG__STD_EXCEPTION -DG_
_HAVE_CONFIG -DG__NOMAKEINFO  -Z0 str.h
make[1]: *** [G__cpp_string.cxx] Error 53
make[1]: Leaving directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint
/cint/lib/dll_stl'
mv: cannot stat `string.dll': No such file or directory

[Axel Naumann]

Hi,

this part is now fixed in the trunk; thanks for the report! Cygwin
changed its behavior wrt LD_LIBRARY_PATH, and that caused it.

But CINT still doesn't build the cintdlls on cygwin because it has a
problem loading string.dll etc. I will let you know when that's resolved.

Cheers, Axel.

Dr. Prasad, B.V.L.S. wrote:

> Hi,
>
> What mistake is happening from my side that I am unable to create a string.dll and all other STL dlls.
> Here is the error message I am getting.  Same code works well in Linux.
>
> I have also exported the CINTSYSDIR and LD_LIBRARY_PATH env. variables into the source file.
> Still this doesnt work.
>
> Here are some more details: I am using Vista Home Premium, Cygwin, g++ 3.4.4,
>
> Thank you,
> Prasad.
> ##########################################################################
> # makecint : interpreter-compiler for cint (Windows Cygwin DLL version)
> # Copyright(c) 1995~2007 Masaharu Goto. Mailing list: cint@...
> ##########################################################################
> Run 'make -f Makestr' to compile the object
> make[1]: Entering directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cin
> t/cint/lib/dll_stl'
> /cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint/bin/cint.exe  -w2 -zstring
> -nG__cpp_string.cxx  -D__MAKECINT__ -DG__MAKECINT  -c-1 -A -I/cygdrive/c/Users/a
> nagha/OldBOSandOthers18Dec08/cint//cint/inc  -DG__CYGWIN -DG__STD_EXCEPTION -DG_
> _HAVE_CONFIG -DG__NOMAKEINFO  -Z0 str.h
> make[1]: *** [G__cpp_string.cxx] Error 53
> make[1]: Leaving directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint
> /cint/lib/dll_stl'
> mv: cannot stat `string.dll': No such file or directory
>
>
>
>
>

[Dr. Prasad, B.V.L.S.]

Hi Axel,
Thank you.
I am using 5.16.29 version of cint. I am more comfortable with 5 and not cint7 yet.
I would like to stick with the older one.

Does your post mean - I can download the 'fixed' older version or do I need to start with cint7?

or can you let me know the fix so that I can add into my source here.

thanks for the help.

Prasad.

 

----- Original Message ----
From: Axel Naumann <Axel.Naumann@...>
To: "Dr. Prasad, B.V.L.S." <burrashiva@...>
Cc: cint@...
Sent: Tuesday, 24 February, 2009 10:19:44
Subject: Re: [CINT] CINT Compilation Problem with Cygwin: Prasad.

Hi,

this part is now fixed in the trunk; thanks for the report! Cygwin
changed its behavior wrt LD_LIBRARY_PATH, and that caused it.

But CINT still doesn't build the cintdlls on cygwin because it has a
problem loading string.dll etc. I will let you know when that's resolved.

Cheers, Axel.

Dr. Prasad, B.V.L.S. wrote:

> Hi,
>
> What mistake is happening from my side that I am unable to create a string.dll and all other STL dlls.
> Here is the error message I am getting.  Same code works well in Linux.
>
> I have also exported the CINTSYSDIR and LD_LIBRARY_PATH env. variables into the source file.
> Still this doesnt work.
>
> Here are some more details: I am using Vista Home Premium, Cygwin, g++ 3.4.4,
>
> Thank you,
> Prasad.
> ##########################################################################
> # makecint : interpreter-compiler for cint (Windows Cygwin DLL version)
> # Copyright(c) 1995~2007 Masaharu Goto. Mailing list: cint@...
> ##########################################################################
> Run 'make -f Makestr' to compile the object
> make[1]: Entering directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cin
> t/cint/lib/dll_stl'
> /cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint/bin/cint.exe  -w2 -zstring
> -nG__cpp_string.cxx  -D__MAKECINT__ -DG__MAKECINT  -c-1 -A -I/cygdrive/c/Users/a
> nagha/OldBOSandOthers18Dec08/cint//cint/inc  -DG__CYGWIN -DG__STD_EXCEPTION -DG_
> _HAVE_CONFIG -DG__NOMAKEINFO  -Z0 str.h
> make[1]: *** [G__cpp_string.cxx] Error 53
> make[1]: Leaving directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint
> /cint/lib/dll_stl'
> mv: cannot stat `string.dll': No such file or directory
>
>
>
>
>

[Axel Naumann]

Hi,

the fix should work for both cint5 and 7. But I also expect the other
issue to show up with cint5 - but you are very welcome to give it a try!
Let me know whether it works.

You will need to use the SVN version of CINT to get this patch, or
manually import it: <http://root.cern.ch/viewcvs?view=rev&revision=27598>

Cheers, Axel.

Dr. Prasad, B.V.L.S. wrote:

> Hi Axel,
> Thank you.
> I am using 5.16.29 version of cint. I am more comfortable with 5 and not cint7 yet.
> I would like to stick with the older one.
>
> Does your post mean - I can download the 'fixed' older version or do I need to start with cint7?
>
> or can you let me know the fix so that I can add into my source here.
>
> thanks for the help.
>
> Prasad.
>
>  
>
> ----- Original Message ----
> From: Axel Naumann <Axel.Naumann@...>
> To: "Dr. Prasad, B.V.L.S." <burrashiva@...>
> Cc: cint@...
> Sent: Tuesday, 24 February, 2009 10:19:44
> Subject: Re: [CINT] CINT Compilation Problem with Cygwin: Prasad.
>
> Hi,
>
> this part is now fixed in the trunk; thanks for the report! Cygwin
> changed its behavior wrt LD_LIBRARY_PATH, and that caused it.
>
> But CINT still doesn't build the cintdlls on cygwin because it has a
> problem loading string.dll etc. I will let you know when that's resolved.
>
> Cheers, Axel.
>
> Dr. Prasad, B.V.L.S. wrote:
>> Hi,
>>
>> What mistake is happening from my side that I am unable to create a string.dll and all other STL dlls.
>> Here is the error message I am getting.  Same code works well in Linux.
>>
>> I have also exported the CINTSYSDIR and LD_LIBRARY_PATH env. variables into the source file.
>> Still this doesnt work.
>>
>> Here are some more details: I am using Vista Home Premium, Cygwin, g++ 3.4.4,
>>
>> Thank you,
>> Prasad.
>> ##########################################################################
>> # makecint : interpreter-compiler for cint (Windows Cygwin DLL version)
>> # Copyright(c) 1995~2007 Masaharu Goto. Mailing list: cint@...
>> ##########################################################################
>> Run 'make -f Makestr' to compile the object
>> make[1]: Entering directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cin
>> t/cint/lib/dll_stl'
>> /cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint/bin/cint.exe  -w2 -zstring
>> -nG__cpp_string.cxx  -D__MAKECINT__ -DG__MAKECINT  -c-1 -A -I/cygdrive/c/Users/a
>> nagha/OldBOSandOthers18Dec08/cint//cint/inc  -DG__CYGWIN -DG__STD_EXCEPTION -DG_
>> _HAVE_CONFIG -DG__NOMAKEINFO  -Z0 str.h
>> make[1]: *** [G__cpp_string.cxx] Error 53
>> make[1]: Leaving directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint
>> /cint/lib/dll_stl'
>> mv: cannot stat `string.dll': No such file or directory
>>
>>
>>
>>
>>
>
>
>
>

[Philippe Canal]

Hi,

Support for shared library has been re-enabled for  cygwin/gcc platform.

In consequence the cintdlls now builds properly.

Cheers,
Philippe.

Axel Naumann wrote:

> Hi,
>
> this part is now fixed in the trunk; thanks for the report! Cygwin
> changed its behavior wrt LD_LIBRARY_PATH, and that caused it.
>
> But CINT still doesn't build the cintdlls on cygwin because it has a
> problem loading string.dll etc. I will let you know when that's resolved.
>
> Cheers, Axel.
>
> Dr. Prasad, B.V.L.S. wrote:
>  
>> Hi,
>>
>> What mistake is happening from my side that I am unable to create a string.dll and all other STL dlls.
>> Here is the error message I am getting.  Same code works well in Linux.
>>
>> I have also exported the CINTSYSDIR and LD_LIBRARY_PATH env. variables into the source file.
>> Still this doesnt work.
>>
>> Here are some more details: I am using Vista Home Premium, Cygwin, g++ 3.4.4,
>>
>> Thank you,
>> Prasad.
>> ##########################################################################
>> # makecint : interpreter-compiler for cint (Windows Cygwin DLL version)
>> # Copyright(c) 1995~2007 Masaharu Goto. Mailing list: cint@...
>> ##########################################################################
>> Run 'make -f Makestr' to compile the object
>> make[1]: Entering directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cin
>> t/cint/lib/dll_stl'
>> /cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint/bin/cint.exe  -w2 -zstring
>> -nG__cpp_string.cxx  -D__MAKECINT__ -DG__MAKECINT  -c-1 -A -I/cygdrive/c/Users/a
>> nagha/OldBOSandOthers18Dec08/cint//cint/inc  -DG__CYGWIN -DG__STD_EXCEPTION -DG_
>> _HAVE_CONFIG -DG__NOMAKEINFO  -Z0 str.h
>> make[1]: *** [G__cpp_string.cxx] Error 53
>> make[1]: Leaving directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint
>> /cint/lib/dll_stl'
>> mv: cannot stat `string.dll': No such file or directory
>>
>>
>>
>>
>>
>>    
>
>
>  

[Dr. Prasad, B.V.L.S.]

Hi Philippe, Axel,

Thank you for the help.
Now I could compile the compile cint and compile the stl dlls too.

this is NOT a problem with cint.
But I would like to know if some body faced following problem and got a fix for the same.

I am running cygwin, cint on Window Vista Home Premium.

From inside cygwin, if I run  $CINTSYSDIR/bin/cint.exe - a window pops up saying cint.exe has stopped.
This window pops for 6 times - after 6 okays, again I am back to the cygwin console window..

But, here is the interesting observation:

From inside cygwin, if I run cint_tmp.exe (cint old ) - it works and opens the usual cint interactive prompt.

Can some body advice me why this is happening or how to fix this problem.

If I using cint7, both cint.exe and cint_tmp.exe - both are not working and giving the above problem.

thank you for any help regarding this.
Regards,
Prasad.




----- Original Message ----
From: Philippe Canal <pcanal@...>
To: Axel Naumann <Axel.Naumann@...>
Cc: "Dr. Prasad, B.V.L.S." <burrashiva@...>; cint@...
Sent: Saturday, 28 February, 2009 0:36:56
Subject: Re: [CINT] CINT Compilation Problem with Cygwin: Prasad.

Hi,

Support for shared library has been re-enabled for  cygwin/gcc platform.

In consequence the cintdlls now builds properly.

Cheers,
Philippe.

Axel Naumann wrote:

> Hi,
>
> this part is now fixed in the trunk; thanks for the report! Cygwin
> changed its behavior wrt LD_LIBRARY_PATH, and that caused it.
>
> But CINT still doesn't build the cintdlls on cygwin because it has a
> problem loading string.dll etc. I will let you know when that's resolved.
>
> Cheers, Axel.
>
> Dr. Prasad, B.V.L.S. wrote:
>  
>> Hi,
>> What mistake is happening from my side that I am unable to create a string.dll and all other STL dlls. Here is the error message I am getting.  Same code works well in Linux.
>> I have also exported the CINTSYSDIR and LD_LIBRARY_PATH env. variables into the source file.
>> Still this doesnt work.
>>
>> Here are some more details: I am using Vista Home Premium, Cygwin, g++ 3.4.4,
>> Thank you, Prasad.
>> ##########################################################################
>> # makecint : interpreter-compiler for cint (Windows Cygwin DLL version)
>> # Copyright(c) 1995~2007 Masaharu Goto. Mailing list: cint@...
>> ##########################################################################
>> Run 'make -f Makestr' to compile the object
>> make[1]: Entering directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cin
>> t/cint/lib/dll_stl'
>> /cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint/bin/cint.exe  -w2 -zstring
>> -nG__cpp_string.cxx  -D__MAKECINT__ -DG__MAKECINT  -c-1 -A -I/cygdrive/c/Users/a
>> nagha/OldBOSandOthers18Dec08/cint//cint/inc  -DG__CYGWIN -DG__STD_EXCEPTION -DG_
>> _HAVE_CONFIG -DG__NOMAKEINFO  -Z0 str.h
>> make[1]: *** [G__cpp_string.cxx] Error 53
>> make[1]: Leaving directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint
>> /cint/lib/dll_stl'
>> mv: cannot stat `string.dll': No such file or directory
>>
>>
>>
>>
>>
>>    
>
>
>  

[Axel Naumann]

Hi,

could you try the following:
export PATH=$CINTSYSDIR/lib:$PATH
and test it again? I believe cygwin has dropped the use of
LD_LIBRARY_PATH, so libReflex is not found anymore in lib/. Which means
we will have to do the same for cygwin as for MSVC: put the DLLs into
bin/. Once you have confirmed that this solves the issue I will add the
Makefile rules.

Cheers, Axel.

On 2009-03-01 02:00, Dr. Prasad, B.V.L.S. wrote:

> Hi Philippe, Axel,
>
> Thank you for the help.
> Now I could compile the compile cint and compile the stl dlls too.
>
> this is NOT a problem with cint.
> But I would like to know if some body faced following problem and got a fix for the same.
>
> I am running cygwin, cint on Window Vista Home Premium.
>
> From inside cygwin, if I run  $CINTSYSDIR/bin/cint.exe - a window pops up saying cint.exe has stopped.
> This window pops for 6 times - after 6 okays, again I am back to the cygwin console window..
>
> But, here is the interesting observation:
>
> From inside cygwin, if I run cint_tmp.exe (cint old ) - it works and opens the usual cint interactive prompt.
>
> Can some body advice me why this is happening or how to fix this problem.
>
> If I using cint7, both cint.exe and cint_tmp.exe - both are not working and giving the above problem.
>
> thank you for any help regarding this.
> Regards,
> Prasad.
>
>
>
>
> ----- Original Message ----
> From: Philippe Canal <pcanal@...>
> To: Axel Naumann <Axel.Naumann@...>
> Cc: "Dr. Prasad, B.V.L.S." <burrashiva@...>; cint@...
> Sent: Saturday, 28 February, 2009 0:36:56
> Subject: Re: [CINT] CINT Compilation Problem with Cygwin: Prasad.
>
> Hi,
>
> Support for shared library has been re-enabled for  cygwin/gcc platform.
>
> In consequence the cintdlls now builds properly.
>
> Cheers,
> Philippe.
>
> Axel Naumann wrote:
>> Hi,
>>
>> this part is now fixed in the trunk; thanks for the report! Cygwin
>> changed its behavior wrt LD_LIBRARY_PATH, and that caused it.
>>
>> But CINT still doesn't build the cintdlls on cygwin because it has a
>> problem loading string.dll etc. I will let you know when that's resolved.
>>
>> Cheers, Axel.
>>
>> Dr. Prasad, B.V.L.S. wrote:
>>  
>>> Hi,
>>> What mistake is happening from my side that I am unable to create a string.dll and all other STL dlls. Here is the error message I am getting.  Same code works well in Linux.
>>> I have also exported the CINTSYSDIR and LD_LIBRARY_PATH env. variables into the source file.
>>> Still this doesnt work.
>>>
>>> Here are some more details: I am using Vista Home Premium, Cygwin, g++ 3.4.4,
>>> Thank you, Prasad.
>>> ##########################################################################
>>> # makecint : interpreter-compiler for cint (Windows Cygwin DLL version)
>>> # Copyright(c) 1995~2007 Masaharu Goto. Mailing list: cint@...
>>> ##########################################################################
>>> Run 'make -f Makestr' to compile the object
>>> make[1]: Entering directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cin
>>> t/cint/lib/dll_stl'
>>> /cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint/bin/cint.exe  -w2 -zstring
>>> -nG__cpp_string.cxx  -D__MAKECINT__ -DG__MAKECINT  -c-1 -A -I/cygdrive/c/Users/a
>>> nagha/OldBOSandOthers18Dec08/cint//cint/inc  -DG__CYGWIN -DG__STD_EXCEPTION -DG_
>>> _HAVE_CONFIG -DG__NOMAKEINFO  -Z0 str.h
>>> make[1]: *** [G__cpp_string.cxx] Error 53
>>> make[1]: Leaving directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint
>>> /cint/lib/dll_stl'
>>> mv: cannot stat `string.dll': No such file or directory
>>>
>>>
>>>
>>>
>>>
>>>    
>>
>>  
>
>
>
>

[Dr. Prasad, B.V.L.S.]

Hi Axel,

cint is working now.
Your suggestion seems to have worked.

Thank you very much.

Prasad.






----- Original Message ----
From: Axel Naumann <Axel.Naumann@...>
To: "Dr. Prasad, B.V.L.S." <burrashiva@...>
Cc: cint@...
Sent: Sunday, 1 March, 2009 2:42:34
Subject: Re: [CINT] CINT Compilation Problem with Cygwin: Prasad.

Hi,

could you try the following:
export PATH=$CINTSYSDIR/lib:$PATH
and test it again? I believe cygwin has dropped the use of
LD_LIBRARY_PATH, so libReflex is not found anymore in lib/. Which means
we will have to do the same for cygwin as for MSVC: put the DLLs into
bin/. Once you have confirmed that this solves the issue I will add the
Makefile rules.

Cheers, Axel.

On 2009-03-01 02:00, Dr. Prasad, B.V.L.S. wrote:

> Hi Philippe, Axel,
>
> Thank you for the help.
> Now I could compile the compile cint and compile the stl dlls too.
>
> this is NOT a problem with cint.
> But I would like to know if some body faced following problem and got a fix for the same.
>
> I am running cygwin, cint on Window Vista Home Premium.
>
> From inside cygwin, if I run  $CINTSYSDIR/bin/cint.exe - a window pops up saying cint.exe has stopped.
> This window pops for 6 times - after 6 okays, again I am back to the cygwin console window..
>
> But, here is the interesting observation:
>
> From inside cygwin, if I run cint_tmp.exe (cint old ) - it works and opens the usual cint interactive prompt.
>
> Can some body advice me why this is happening or how to fix this problem.
>
> If I using cint7, both cint.exe and cint_tmp.exe - both are not working and giving the above problem.
>
> thank you for any help regarding this.
> Regards,
> Prasad.
>
>
>
>
> ----- Original Message ----
> From: Philippe Canal <pcanal@...>
> To: Axel Naumann <Axel.Naumann@...>
> Cc: "Dr. Prasad, B.V.L.S." <burrashiva@...>; cint@...
> Sent: Saturday, 28 February, 2009 0:36:56
> Subject: Re: [CINT] CINT Compilation Problem with Cygwin: Prasad.
>
> Hi,
>
> Support for shared library has been re-enabled for  cygwin/gcc platform.
>
> In consequence the cintdlls now builds properly.
>
> Cheers,
> Philippe.
>
> Axel Naumann wrote:
>> Hi,
>>
>> this part is now fixed in the trunk; thanks for the report! Cygwin
>> changed its behavior wrt LD_LIBRARY_PATH, and that caused it.
>>
>> But CINT still doesn't build the cintdlls on cygwin because it has a
>> problem loading string.dll etc. I will let you know when that's resolved.
>>
>> Cheers, Axel.
>>
>> Dr. Prasad, B.V.L.S. wrote:
>>  
>>> Hi,
>>> What mistake is happening from my side that I am unable to create a string.dll and all other STL dlls. Here is the error message I am getting.  Same code works well in Linux.
>>> I have also exported the CINTSYSDIR and LD_LIBRARY_PATH env. variables into the source file.
>>> Still this doesnt work.
>>>
>>> Here are some more details: I am using Vista Home Premium, Cygwin, g++ 3.4.4,
>>> Thank you, Prasad.
>>> ##########################################################################
>>> # makecint : interpreter-compiler for cint (Windows Cygwin DLL version)
>>> # Copyright(c) 1995~2007 Masaharu Goto. Mailing list: cint@...
>>> ##########################################################################
>>> Run 'make -f Makestr' to compile the object
>>> make[1]: Entering directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cin
>>> t/cint/lib/dll_stl'
>>> /cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint/bin/cint.exe  -w2 -zstring
>>> -nG__cpp_string.cxx  -D__MAKECINT__ -DG__MAKECINT  -c-1 -A -I/cygdrive/c/Users/a
>>> nagha/OldBOSandOthers18Dec08/cint//cint/inc  -DG__CYGWIN -DG__STD_EXCEPTION -DG_
>>> _HAVE_CONFIG -DG__NOMAKEINFO  -Z0 str.h
>>> make[1]: *** [G__cpp_string.cxx] Error 53
>>> make[1]: Leaving directory `/cygdrive/c/Users/anagha/OldBOSandOthers18Dec08/cint
>>> /cint/lib/dll_stl'
>>> mv: cannot stat `string.dll': No such file or directory
>>>
>>>
>>>
>>>
>>>
>>>    
>>
>>  
>
>
>
>

[Dr. Prasad, B.V.L.S.]

Hi Axel

This is in continuation to my Cygwin problems with cint.  

I was trying to run a small test script using the current cint. i.e
{ cout<<"hello"<<endl; }
It mentioned it doesnt understand "<<".
so I tried:
{ #include <iostream>
cout<<"hello"<<endl;
}

this also is not working. It complains "CINTSYSDIR" is not set.
but as you can see below, I have set that prior to running cint.exe, which is displayed at the end of the log below.

could you help me?
thank you,
Prasad.

anagha@anagha-PC ~/cint/bin
$ ./cint.exe

cint : C/C++ interpreter  (mailing list 'cint@...')
   Copyright(c) : 1995~2005 Masaharu Goto (gotom@...)
   revision     : 5.17.00, Dec 21, 2008 by M.Goto

No main() function found in given source file. Interactive interface started.
'h':help, 'q':quit, '{statements;}' or 'p [expr]' to evaluate

cint> {
end with '}', '@':abort > cout<<"hello"<<endl;
end with '}', '@':abort > }
Error: Symbol cout is not defined in current scope  FILE:(tmpfile) LINE:2
Error: << Illegal operator for pointer 3 FILE:(tmpfile) LINE:2
Error: Symbol endl is not defined in current scope  FILE:(tmpfile) LINE:2
!!!Dictionary position rewound... !!!Error recovered!!!
cint> { #include <iostream>
end with '}', '@':abort > cout<<"hello"<<endl;
end with '}', '@':abort > }
Warning: environment variable CINTSYSDIR is not set. Standard include files igno
red
Error: cannot open file "iostream"  FILE:(tmpfile) LINE:2
!!!Dictionary position rewound... !!!Error recovered!!!
cint>

cint> quit
  Bye... (try 'qqq' if still running)

anagha@anagha-PC ~/cint/bin
$ echo $CINTSYSDIR
/home/anagha/cint

anagha@anagha-PC ~/cint/bin
$

[Philippe Canal]

Hi,

I can not reproduce this problem (is it with the old or new core, i.e
cint5 or cint7).
How did you set the CINTSYSDIR variable?
Did you do
export CINTSYSDIR=.....
?

Cheers,
Philippe.

Dr. Prasad, B.V.L.S. wrote:

> Hi Axel
>
> This is in continuation to my Cygwin problems with cint.  
>
> I was trying to run a small test script using the current cint. i.e
> { cout<<"hello"<<endl; }
> It mentioned it doesnt understand "<<".
> so I tried:
> { #include <iostream>
> cout<<"hello"<<endl;
> }
>
> this also is not working. It complains "CINTSYSDIR" is not set.
> but as you can see below, I have set that prior to running cint.exe, which is displayed at the end of the log below.
>
> could you help me?
> thank you,
> Prasad.
>
> anagha@anagha-PC ~/cint/bin
> $ ./cint.exe
>
> cint : C/C++ interpreter  (mailing list 'cint@...')
>    Copyright(c) : 1995~2005 Masaharu Goto (gotom@...)
>    revision     : 5.17.00, Dec 21, 2008 by M.Goto
>
> No main() function found in given source file. Interactive interface started.
> 'h':help, 'q':quit, '{statements;}' or 'p [expr]' to evaluate
>
> cint> {
> end with '}', '@':abort > cout<<"hello"<<endl;
> end with '}', '@':abort > }
> Error: Symbol cout is not defined in current scope  FILE:(tmpfile) LINE:2
> Error: << Illegal operator for pointer 3 FILE:(tmpfile) LINE:2
> Error: Symbol endl is not defined in current scope  FILE:(tmpfile) LINE:2
> !!!Dictionary position rewound... !!!Error recovered!!!
> cint> { #include <iostream>
> end with '}', '@':abort > cout<<"hello"<<endl;
> end with '}', '@':abort > }
> Warning: environment variable CINTSYSDIR is not set. Standard include files igno
> red
> Error: cannot open file "iostream"  FILE:(tmpfile) LINE:2
> !!!Dictionary position rewound... !!!Error recovered!!!
> cint>
>
> cint> quit
>   Bye... (try 'qqq' if still running)
>
> anagha@anagha-PC ~/cint/bin
> $ echo $CINTSYSDIR
> /home/anagha/cint
>
> anagha@anagha-PC ~/cint/bin
> $
>
>
>
>
>
>  

[Dr. Prasad, B.V.L.S.]

Hi Philippe,

I am using cint5 using >>./configure --arch-cygwin --coreversion=cint command

Inside the cygwin console window, I opened ~/.bashrc and put
CINTSYSDIR=/home/anagha/cint
export $PATH=$CINTSYSDIR:$PATH;

sourced this file.
Then cross checked from the command line >> echo $CINTSYSDIR which is giving me the correct path.

I have to mention - I am using cygwin on windows Vista Home premium if that has any thing to do with the problem.

In linux this is not a problem, it works after providing #include <iostream>

can we not make cint load <iostream> automatically during loading the application.?

thank you,
Prasad.




How did you set the CINTSYSDIR variable?
Did you do
export CINTSYSDIR=.....
?

Cheers,
Philippe.

Dr. Prasad, B.V.L.S. wrote:

> Hi Axel
>
> This is in continuation to my Cygwin problems with cint.  
> I was trying to run a small test script using the current cint. i.e { cout<<"hello"<<endl; }
> It mentioned it doesnt understand "<<". so I tried: { #include <iostream> cout<<"hello"<<endl;
> }
>
> this also is not working. It complains "CINTSYSDIR" is not set. but as you can see below, I have set that prior to running cint.exe, which is displayed at the end of the log below.
> could you help me? thank you, Prasad.
>
> anagha@anagha-PC ~/cint/bin
> $ ./cint.exe
>
> cint : C/C++ interpreter  (mailing list 'cint@...')
>    Copyright(c) : 1995~2005 Masaharu Goto (gotom@...)
>    revision     : 5.17.00, Dec 21, 2008 by M.Goto
>
> No main() function found in given source file. Interactive interface started.
> 'h':help, 'q':quit, '{statements;}' or 'p [expr]' to evaluate
>
> cint> {
> end with '}', '@':abort > cout<<"hello"<<endl;
> end with '}', '@':abort > }
> Error: Symbol cout is not defined in current scope  FILE:(tmpfile) LINE:2
> Error: << Illegal operator for pointer 3 FILE:(tmpfile) LINE:2
> Error: Symbol endl is not defined in current scope  FILE:(tmpfile) LINE:2
> !!!Dictionary position rewound... !!!Error recovered!!!
> cint> { #include <iostream>
> end with '}', '@':abort > cout<<"hello"<<endl;
> end with '}', '@':abort > }
> Warning: environment variable CINTSYSDIR is not set. Standard include files igno
> red
> Error: cannot open file "iostream"  FILE:(tmpfile) LINE:2
> !!!Dictionary position rewound... !!!Error recovered!!!
> cint>
>
> cint> quit
>   Bye... (try 'qqq' if still running)
>
> anagha@anagha-PC ~/cint/bin
> $ echo $CINTSYSDIR
> /home/anagha/cint
>
> anagha@anagha-PC ~/cint/bin
> $
>
>
>
>
>
>  

[Philippe Canal]

Hi,

It looks like you need to replace

CINTSYSDIR=/home/anagha/cint

with

export CINTSYSDIR=/home/anagha/cint

Cheers,
Philippe.


Dr. Prasad, B.V.L.S. wrote:

> Hi Philippe,
>
> I am using cint5 using >>./configure --arch-cygwin --coreversion=cint command
>
> Inside the cygwin console window, I opened ~/.bashrc and put
> CINTSYSDIR=/home/anagha/cint
> export $PATH=$CINTSYSDIR:$PATH;
>
> sourced this file.
> Then cross checked from the command line >> echo $CINTSYSDIR which is giving me the correct path.
>
> I have to mention - I am using cygwin on windows Vista Home premium if that has any thing to do with the problem.
>
> In linux this is not a problem, it works after providing #include <iostream>
>
> can we not make cint load <iostream> automatically during loading the application.?
>
> thank you,
> Prasad.
>
>
>
>
> How did you set the CINTSYSDIR variable?
> Did you do
> export CINTSYSDIR=.....
> ?
>
> Cheers,
> Philippe.
>
> Dr. Prasad, B.V.L.S. wrote:
>  
>> Hi Axel
>>
>> This is in continuation to my Cygwin problems with cint.  
>> I was trying to run a small test script using the current cint. i.e { cout<<"hello"<<endl; }
>> It mentioned it doesnt understand "<<". so I tried: { #include <iostream> cout<<"hello"<<endl;
>> }
>>
>> this also is not working. It complains "CINTSYSDIR" is not set. but as you can see below, I have set that prior to running cint.exe, which is displayed at the end of the log below.
>> could you help me? thank you, Prasad.
>>
>> anagha@anagha-PC ~/cint/bin
>> $ ./cint.exe
>>
>> cint : C/C++ interpreter  (mailing list 'cint@...')
>>    Copyright(c) : 1995~2005 Masaharu Goto (gotom@...)
>>    revision     : 5.17.00, Dec 21, 2008 by M.Goto
>>
>> No main() function found in given source file. Interactive interface started.
>> 'h':help, 'q':quit, '{statements;}' or 'p [expr]' to evaluate
>>
>> cint> {
>> end with '}', '@':abort > cout<<"hello"<<endl;
>> end with '}', '@':abort > }
>> Error: Symbol cout is not defined in current scope  FILE:(tmpfile) LINE:2
>> Error: << Illegal operator for pointer 3 FILE:(tmpfile) LINE:2
>> Error: Symbol endl is not defined in current scope  FILE:(tmpfile) LINE:2
>> !!!Dictionary position rewound... !!!Error recovered!!!
>> cint> { #include <iostream>
>> end with '}', '@':abort > cout<<"hello"<<endl;
>> end with '}', '@':abort > }
>> Warning: environment variable CINTSYSDIR is not set. Standard include files igno
>> red
>> Error: cannot open file "iostream"  FILE:(tmpfile) LINE:2
>> !!!Dictionary position rewound... !!!Error recovered!!!
>> cint>
>>
>> cint> quit
>>   Bye... (try 'qqq' if still running)
>>
>> anagha@anagha-PC ~/cint/bin
>> $ echo $CINTSYSDIR
>> /home/anagha/cint
>>
>> anagha@anagha-PC ~/cint/bin
>> $
>>
>>
>>
>>
>>
>>  
>>    
>
>
>
>
>  

[Axel Naumann]

Hi,

this cannot possibly be your configure line - it has two bugs that
configure should complain about. I think I know what you mean, but I
would like to make sure that this is really what you did. So: what's the
output of "cat config.status"?

Cheers, Axel.

On 2009-03-02 21:10, Dr. Prasad, B.V.L.S. wrote:

> Hi Philippe,
>
> I am using cint5 using >>./configure --arch-cygwin --coreversion=cint command
>
> Inside the cygwin console window, I opened ~/.bashrc and put
> CINTSYSDIR=/home/anagha/cint
> export $PATH=$CINTSYSDIR:$PATH;
>
> sourced this file.
> Then cross checked from the command line >> echo $CINTSYSDIR which is giving me the correct path.
>
> I have to mention - I am using cygwin on windows Vista Home premium if that has any thing to do with the problem.
>
> In linux this is not a problem, it works after providing #include <iostream>
>
> can we not make cint load <iostream> automatically during loading the application.?
>
> thank you,
> Prasad.
>
>
>
>
> How did you set the CINTSYSDIR variable?
> Did you do
> export CINTSYSDIR=.....
> ?
>
> Cheers,
> Philippe.
>
> Dr. Prasad, B.V.L.S. wrote:
>> Hi Axel
>>
>> This is in continuation to my Cygwin problems with cint.  
>> I was trying to run a small test script using the current cint. i.e { cout<<"hello"<<endl; }
>> It mentioned it doesnt understand "<<". so I tried: { #include <iostream> cout<<"hello"<<endl;
>> }
>>
>> this also is not working. It complains "CINTSYSDIR" is not set. but as you can see below, I have set that prior to running cint.exe, which is displayed at the end of the log below.
>> could you help me? thank you, Prasad.
>>
>> anagha@anagha-PC ~/cint/bin
>> $ ./cint.exe
>>
>> cint : C/C++ interpreter  (mailing list 'cint@...')
>>    Copyright(c) : 1995~2005 Masaharu Goto (gotom@...)
>>    revision     : 5.17.00, Dec 21, 2008 by M.Goto
>>
>> No main() function found in given source file. Interactive interface started.
>> 'h':help, 'q':quit, '{statements;}' or 'p [expr]' to evaluate
>>
>> cint> {
>> end with '}', '@':abort > cout<<"hello"<<endl;
>> end with '}', '@':abort > }
>> Error: Symbol cout is not defined in current scope  FILE:(tmpfile) LINE:2
>> Error: << Illegal operator for pointer 3 FILE:(tmpfile) LINE:2
>> Error: Symbol endl is not defined in current scope  FILE:(tmpfile) LINE:2
>> !!!Dictionary position rewound... !!!Error recovered!!!
>> cint> { #include <iostream>
>> end with '}', '@':abort > cout<<"hello"<<endl;
>> end with '}', '@':abort > }
>> Warning: environment variable CINTSYSDIR is not set. Standard include files igno
>> red
>> Error: cannot open file "iostream"  FILE:(tmpfile) LINE:2
>> !!!Dictionary position rewound... !!!Error recovered!!!
>> cint>
>>
>> cint> quit
>>   Bye... (try 'qqq' if still running)
>>
>> anagha@anagha-PC ~/cint/bin
>> $ echo $CINTSYSDIR
>> /home/anagha/cint
>>
>> anagha@anagha-PC ~/cint/bin
>> $
>>
>>
>>
>>
>>
>>  
>
>
>
>