Experimental Physics and
Industrial Control System

Pierrick Hanlet <[email protected]> · Tue, 08 Sep 2009 15:40:48 -0500

Thanks for the help; there was a problem with file corruption.  I deleted the tarball, reloaded,
reextracted, and rebuilt.  All is well.
Pierrick

-----------------------------------------------------------------------------------------
Pierrick Hanlet
Fermilab, P.O. Box 500, M.S. 122
Batavia, IL 60510
[email protected]
(630)840-5555/8871/6039         office/lab/fax 
http://www-d0.fnal.gov/~hanlet 

"Whether you think you can or think you can't, either way, you are correct" -- Henry Ford

----- Original Message -----
From: Mark Rivers <[email protected]>
Date: Tuesday, September 8, 2009 3:35 pm
Subject: RE: asyn compiler problems
To: Emmanuel Mayssat <[email protected]>, Pierrick Hanlet <[email protected]>
Cc: [email protected]

> I don't think the problem is that it cannot find base, at least not at 
> compile time.  If that were the case I would expect to see many error 
> messages about not being able to find epicsMutex.h, etc.
>  
> I concur with Eric, I think something was corrupted with your download 
> or tar file extraction.
>  
> I normally build asyn from a CVS checkout, but just to be sure that 
> there was nothing wrong with the tar.gz file on the asyn Web site, I 
> just downloaded and built asyn from that file on Linux and vxWorks.  
> It built fine, there is nothing wrong with the asynRecord.dbd file.
>  
> Mark
>  
> 
> ________________________________
> 
> From: [email protected] on behalf of Emmanuel Mayssat
> Sent: Tue 9/8/2009 2:54 PM
> To: Pierrick Hanlet
> Cc: [email protected]
> Subject: Re: asyn compiler problems
> 
> 
> 
> Pierrick Hanlet wrote:
> > Hi,
> > n attempting to build the asyn support package, v4.12, and even 
> v4.11, I cannot even compile the
> > package.  Initially, I found some spurious characters in the dbd 
> file.  I'm now stumped (and have
> > been since 08:00 today) with the compilation error message.
> >
> > /usr/bin/gcc -c   -D_POSIX_C_SOURCE=199506L -D_POSIX_THREADS 
> -D_XOPEN_SOURCE=500           -D_X86_  -DUNIX  -D_BSD_SOURCE -Dlinux  
> -D_REENTRANT -ansi   -O3   -Wall      -m32     -g -fPIC -I. 
> -I../O.Common -I. -I.. -I../../asyn/asynDriver -I../../asyn/asynGpib 
> -I../../asyn/drvAsynSerial -I../../asyn/interfaces 
> -I../../asyn/miscellaneous -I../../asyn/devEpics 
> -I../../asyn/asynRecord -I../../asyn/vxi11 -I../../asyn/ni1014 
> -I../../asyn/devGpib -I../../include/os/Linux -I../../include   
> -I/home/epics/epics/base/include/os/Linux 
> -I/home/epics/epics/base/include        ../../asyn/asynRecord/asynRecord.c
> > ../../asyn/asynRecord/asynRecord.c: In function 'init_record':
> > ../../asyn/asynRecord/asynRecord.c:264: error: 'asynRecord' has no 
> member named 'dpvt'
> > ../../asyn/asynRecord/asynRecord.c:272: error: 'asynRecord' has no 
> member named 'dpvt'
> > ../../asyn/asynRecord/asynRecord.c:285: error: 'asynRecord' has no 
> member named 'udf'
> > ../../asyn/asynRecord/asynRecord.c:296: error: 'asynRecord' has no 
> member named 'name'
> >
> >  
> 
> It seems asyn cannot find dbCommon.dbd where all those fields are declared.
> dbCommon is located in the epics base. So check where your
> config/configure files are pointing to. (did you 'make' the base?)
> 
> > These members are defined in a number of 
> /home/epics/epics/base/include files of different
> > record types.  Can (will) you kindly assist me?
> > Thanks,
> > Pierrick
> >
> > -----------------------------------------------------------------------------------------
> > Pierrick Hanlet
> > Fermilab, P.O. Box 500, M.S. 122
> > Batavia, IL 60510
> > [email protected]
> > (630)840-5555/8871/6039         office/lab/fax
> > http://www-d0.fnal.gov/~hanlet
> >
> > "Whether you think you can or think you can't, either way, you are 
> correct" -- Henry Ford
> >
> >
> >
> >  
> 
> 
> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System