EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: Re: unknown type name 'DBLINK'
From: Heinz Junkes via Core-talk <core-talk at aps.anl.gov>
To: Michael Davidsaver <mdavidsaver at gmail.com>
Cc: core-talk at aps.anl.gov
Date: Sat, 12 Mar 2022 20:24:29 +0100
Bull's eye

I could have thought of it myself ;-(

more ./rtems/6/powerpc-rtems6/beatnik/lib/include/link.h

...
#ifndef _LINK_H_
#define	_LINK_H_

/*
 * Pull in the correct definitions for our toolchain target.
 */
#ifdef __ELF__
#include <link_elf.h>
#else
#include <link_aout.h>
#endif

#endif /* _LINK_H_ */

Danke! Heinz


> On 12. Mar 2022, at 18:23, Michael Davidsaver <mdavidsaver at gmail.com> wrote:
> 
> On 3/12/22 09:13, Heinz Junkes via Core-talk wrote:
>> When compiling epics-base with rtems6 I get the error " unknown type name 'DBLINK' “.
>> in link.h (wird von dbAccess.h included) findet man dies:
>> struct link {
>>     struct dbCommon *precord;   /* Pointer to record owning link */
>>     short type;
>>     short flags;
>>     struct lset *lset;
>>     char *text;             /* Raw link text */
>>     union value value;
>> };
>> typedef struct link DBLINK;
>> Does anyone have an idea what is going wrong here? Can this be due to gcc-10 (powerpc-rtems6-gcc (GCC) 10.3.1) ?
> 
> I've been successfully using GCC 10.2 for some time, and GCC developers are usually strict
> about not making potentially breaking changes in a minor release.
> 
> I'd suggest approaching this by looking at the output of the preprocessor to make sure the
> typedef DBLINK from link.h is really being included.  Maybe there is another link.h ?
> 
> The straightforward, but ugly, way to do this is to copy+paste the failing gcc invocation
> and replace '-c' with '-o .../some.c -E'.  Running this from the appropriate
> O.* directory.
> 
> 
>> Heinz
>> ...
>> /home/rtems/MVME6100_WORK/rtems/6/bin/powerpc-rtems6-gcc  -fasm  -I/home/rtems/MVME6100_WORK/rtems/6/powerpc-rtems6/beatnik/lib/include -mcpu=7400       -D_GNU_SOURCE -D_DEFAULT_SOURCE         -DUSE_TYPED_RSET -DUSE_TYPED_DSET    -DUNIX      -O2 -g -fdata-sections -ffunction-sections   -Wall -Werror-implicit-function-declaration       -DRTEMS_HAS_ALTIVEC -DHAVE_MOTLOAD -DRTEMS_NETWORK_CONFIG_MBUF_SPACE=2048 -DRTEMS_NETWORK_CONFIG_CLUSTER_SPACE=5120 -mcpu=7400 -I/home/rtems/MVME6100_WORK/rtems/6/powerpc-rtems6/beatnik/lib/include    -D__LINUX_ERRNO_EXTENSIONS__    -I. -I../O.Common -I. -I. -I.. -I../as -I../bpt -I../db -I../dbStatic -I../dbtemplate -I../misc -I../registry -I../rsrv -I../../../../../include/compiler/gcc -I../../../../../include/os/RTEMS -I../../../../../include         -MM -MF asDbLib.d  ../as/asDbLib.c
>> perl -CSD /home/rtems/EPICS_TST/epics-base/bin/linux-x86_64/genVersionHeader.pl   -t ../../../../.. -N EPICS_VCS_VERSION -V "" ../O.Common/epicsVCS.h
>> Keeping VCS header ../O.Common/epicsVCS.h
>>     EPICS_VCS_VERSION = "R7.0.6.1-75-g91941af992f6c32ef4f4-dirty"
>> Expanding ../databaseVersion.h@ to ../O.Common/databaseVersion.h
>> perl -CSD /home/rtems/EPICS_TST/epics-base/bin/linux-x86_64/expandVars.pl -t ../../../../..   -DEPICS_DATABASE_MAJOR_VERSION="3"  -DEPICS_DATABASE_MINOR_VERSION="21"  -DEPICS_DATABASE_MAINTENANCE_VERSION="1"  -DEPICS_DATABASE_DEVELOPMENT_FLAG="1"  ../databaseVersion.h@ databaseVersion.h
>> Installing generated generic include file ../../../../../include/databaseVersion.h
>> /home/rtems/MVME6100_WORK/rtems/6/bin/powerpc-rtems6-gcc  -fasm  -I/home/rtems/MVME6100_WORK/rtems/6/powerpc-rtems6/beatnik/lib/include -mcpu=7400       -D_GNU_SOURCE -D_DEFAULT_SOURCE         -DUSE_TYPED_RSET -DUSE_TYPED_DSET    -DUNIX      -O2 -g -fdata-sections -ffunction-sections   -Wall -Werror-implicit-function-declaration       -DRTEMS_HAS_ALTIVEC -DHAVE_MOTLOAD -DRTEMS_NETWORK_CONFIG_MBUF_SPACE=2048 -DRTEMS_NETWORK_CONFIG_CLUSTER_SPACE=5120 -mcpu=7400 -I/home/rtems/MVME6100_WORK/rtems/6/powerpc-rtems6/beatnik/lib/include    -D__LINUX_ERRNO_EXTENSIONS__    -I. -I../O.Common -I. -I. -I.. -I../as -I../bpt -I../db -I../dbStatic -I../dbtemplate -I../misc -I../registry -I../rsrv -I../../../../../include/compiler/gcc -I../../../../../include/os/RTEMS -I../../../../../include         -c ../as/asDbLib.c
>> In file included from ../db/dbAccess.h:27,
>>                  from ../as/asDbLib.c:31:
>> ../O.Common/dbCommon.h:27:5: error: unknown type name 'DBLINK'
>>    27 |     DBLINK              tsel;       /**< @brief Time Stamp Link */
>>       |     ^~~~~~
>> ../O.Common/dbCommon.h:31:5: error: unknown type name 'DBLINK'
>>    31 |     DBLINK              sdis;       /**< @brief Scanning Disable */
>>       |     ^~~~~~
>> ../O.Common/dbCommon.h:66:5: error: unknown type name 'DBLINK'
>>    66 |     DBLINK              flnk;       /**< @brief Forward Process Link */
>>       |     ^~~~~~
>> make[5]: *** [../../../../../configure/RULES_BUILD:259: asDbLib.o] Error 1
>> make[5]: Leaving directory '/home/rtems/EPICS_TST/epics-base/modules/database/src/ioc/O.RTEMS-beatnik'
>> make[4]: *** [../../../../configure/RULES_ARCHS:58: install.RTEMS-beatnik] Error 2
>> make[4]: Leaving directory '/home/rtems/EPICS_TST/epics-base/modules/database/src/ioc'
>> make[3]: *** [../../../configure/RULES_DIRS:85: ioc.install] Error 2
>> make[3]: Leaving directory '/home/rtems/EPICS_TST/epics-base/modules/database/src'
>> make[2]: *** [../../configure/RULES_DIRS:85: src.install] Error 2
>> make[2]: Leaving directory '/home/rtems/EPICS_TST/epics-base/modules/database'
>> make[1]: *** [../configure/RULES_DIRS:85: database.install] Error 2
>> make[1]: Leaving directory '/home/rtems/EPICS_TST/epics-base/modules'
>> make: *** [configure/RULES_DIRS:85: modules.install] Error 2
> 


Replies:
Re: unknown type name 'DBLINK' Michael Davidsaver via Core-talk
References:
unknown type name 'DBLINK' Heinz Junkes via Core-talk
Re: unknown type name 'DBLINK' Michael Davidsaver via Core-talk

Navigate by Date:
Prev: Build failed: EPICS Base 7 base-7.0-483 AppVeyor via Core-talk
Next: Re: unknown type name 'DBLINK' Michael Davidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
Navigate by Thread:
Prev: Re: unknown type name 'DBLINK' Michael Davidsaver via Core-talk
Next: Re: unknown type name 'DBLINK' Michael Davidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
ANJ, 14 Sep 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·