Re: unknown type name 'DBLINK'

[Heinz Junkes via Core-talk <core-talk at aps.anl.gov>]

> On 12. Mar 2022, at 20:45, Michael Davidsaver <mdavidsaver at gmail.com> wrote:
> 
> On 3/12/22 11:24, Heinz Junkes wrote:
>> Bull's eye
>> I could have thought of it myself ;-(
>> more ./rtems/6/powerpc-rtems6/beatnik/lib/include/link.h
> 
> Ok.  So the first '-I'

exactly and that is built by the RTEMS :

rtems@rtems-dev:~/MVME6100_WORK/rtems/6/make/custom$ more beatnik.cfg
include $(RTEMS_ROOT)/make/custom/default.cfg
CPU_DEFINES = -I$(exec_prefix)/$(RTEMS_BSP)/lib/include
CPU_CFLAGS = -mcpu=7400
CFLAGS_OPTIMIZE_V = -O2 -g -fdata-sections -ffunction-sections
LDFLAGS = -B$(exec_prefix)/$(RTEMS_BSP)/lib -qrtems -Wl,--gc-sections

in share/rtems6/make/compilers/gcc-target-default.cfg
...
# NOTE: CPU_DEFINES should probably be merged with CPU_CFLAGS
CPPFLAGS += $(CPU_DEFINES) $(CPU_CFLAGS) $(DEFINES) $(XCPPFLAGS)

Which gets called in CONFIG.Common.RTEMS by inlude $(CONFIG.CC)

…
# Pick up the RTEMS tool/path definitions from the RTEMS BSP directory.
include $(RTEMS_BASE)/$(GNU_TARGET)$(RTEMS_VERSION)/$(RTEMS_BSP)/Makefile.inc
include $(RTEMS_CUSTOM)
include $(CONFIG.CC)

> 
>> .../powerpc-rtems6-gcc  -fasm  -I/home/rtems/MVME6100_WORK/rtems/6/powerpc-rtems6/beatnik/lib/include ...
> 
> needs to be shifted to the end, or included with '-isystem /...'.
> 
> https://gcc.gnu.org/onlinedocs/gcc/Directory-Options.html

I have not yet managed to do the “shifting to the end”.  I first renamed link.h in the rtems/beatnik/include.

And could build anything with it:

rtems@rtems-dev:~/EPICS_TST/epics-base$ ls -l bin/RTEMS-beatnik/
total 733132
-r-xr-xr-x 1 rtems rtems 82120228 Mar 12 21:09 caTestHarness
-r-xr-xr-x 1 rtems rtems  9131356 Mar 12 21:09 caTestHarness.boot
-r-xr-xr-x 1 rtems rtems 44712968 Mar 12 21:00 dbTestHarness
-r-xr-xr-x 1 rtems rtems  6837396 Mar 12 21:00 dbTestHarness.boot
-r-xr-xr-x 1 rtems rtems 44336416 Mar 12 21:00 filterTestHarness
-r-xr-xr-x 1 rtems rtems  6704788 Mar 12 21:00 filterTestHarness.boot
-r-xr-xr-x 1 rtems rtems 43103048 Mar 12 20:58 libComTestHarness
-r-xr-xr-x 1 rtems rtems  6617180 Mar 12 20:58 libComTestHarness.boot
-r-xr-xr-x 1 rtems rtems 44245416 Mar 12 21:00 linkTestHarness
-r-xr-xr-x 1 rtems rtems  6684748 Mar 12 21:00 linkTestHarness.boot
-r-xr-xr-x 1 rtems rtems 76804920 Mar 12 21:09 pvaTestHarness
-r-xr-xr-x 1 rtems rtems  8134900 Mar 12 21:09 pvaTestHarness.boot
-r-xr-xr-x 1 rtems rtems 78878688 Mar 12 21:13 pvDbTestHarness
-r-xr-xr-x 1 rtems rtems  8021692 Mar 12 21:13 pvDbTestHarness.boot
-r-xr-xr-x 1 rtems rtems 64832056 Mar 12 21:04 pvdTestHarness
-r-xr-xr-x 1 rtems rtems  7511412 Mar 12 21:04 pvdTestHarness.boot
-r-xr-xr-x 1 rtems rtems 49582488 Mar 12 21:00 recordTestHarness
-r-xr-xr-x 1 rtems rtems 10247044 Mar 12 21:00 recordTestHarness.boot
-r-xr-xr-x 1 rtems rtems 47634852 Mar 12 21:00 softIoc
-r-xr-xr-x 1 rtems rtems  7435660 Mar 12 21:00 softIoc.boot
-r-xr-xr-x 1 rtems rtems 87876340 Mar 12 21:14 softIocPVA
-r-xr-xr-x 1 rtems rtems  9217444 Mar 12 21:14 softIocPVA.boot


I'll have a look at the -isystem. Thanks Heinz