Re: EPICS in Docker image Build Error base-3.15.6 (alpine linux)

[Josh Fiddler via Tech-talk <tech-talk at aps.anl.gov>]

Thank you for having me!

I managed to compile EPICS 7.0.5 within the MDSplus Alapine container and ran `make runtests`. Only two tests Failed

###### Begin Error Output ######

/Test Summary Report

-------------------
epicsTimeZoneTest.t         (Wstat: 256 Tests: 160 Failed: 4)
  Failed tests:  84, 90, 104, 110
  Non-zero exit status: 1
epicsThreadTest.t           (Wstat: 256 Tests: 15 Failed: 2)
  Failed tests:  3, 5
  Non-zero exit status: 1
Files=48, Tests=4285, 211 wallclock secs ( 0.49 usr  0.07 sys +  1.42 cusr  0.72 csys =  2.70 CPU)
Result: FAIL

###### End Error Output ######

Are the test cases published? 

On Tue, Apr 20, 2021 at 7:33 PM Johnson, Andrew N. <anj at anl.gov> wrote:

Hi Josh,

Welcome to the EPICS community!

On Apr 20, 2021, at 6:07 PM, Josh Fiddler via Tech-talk <tech-talk at aps.anl.gov> wrote:
>
> I have what seems to be a unique problem.

Apparently, but it should be easily solvable...

> To build the MDSplus EPICS interface requirements I appear to need the MDSplus libraries. MDSplus provides a docker image based on Alpine linux. I've added the required build tools with `apk`.

I don’t know of anyone using Alpine Linux with EPICS yet, but we're a pretty big community now.

...


> Everything goes swimmingly, so far as I can tell, until it comes to `src/libCom/osi` and then  the compiler complains and quits. Here's the error
>
> ############# Begin Error snippet  #############
> usr/bin/gcc  -D_GNU_SOURCE -D_DEFAULT_SOURCE            -D_X86_64_  -DUNIX  -Dlinux     -O3 -g   -Wall      -mtune=generic     -m64 -fPIC -I. -I../O.Common -I. -I../../../src/libCom/osi/compiler/gcc -I../../../src/libCom/osi/compiler/default -I. -I../../../src/libCom/osi/os/Linux -I../../../src/libCom/osi/os/posix -I../../../src/libCom/osi/os/default -I.. -I../../../src/libCom/as -I../../../src/libCom/bucketLib -I../../../src/libCom/calc -I../../../src/libCom/cvtFast -I../../../src/libCom/cppStd -I../../../src/libCom/cxxTemplates -I../../../src/libCom/dbmf -I../../../src/libCom/ellLib -I../../../src/libCom/env -I../../../src/libCom/error -I../../../src/libCom/fdmgr -I../../../src/libCom/flex -I../../../src/libCom/freeList -I../../../src/libCom/gpHash -I../../../src/libCom/iocsh -I../../../src/libCom/log -I../../../src/libCom/macLib -I../../../src/libCom/misc -I../../../src/libCom/osi -I../../../src/libCom/pool -I../../../src/libCom/ring -I../../../src/libCom/taskwd -I../../../src/libCom/timer -I../../../src/libCom/yacc -I../../../src/libCom/yacc -I../../../src/libCom/yajl -I../../../include/compiler/gcc -I../../../include/os/Linux -I../../../include         -c ../../../src/libCom/env/envSubr.c
> ../../../src/libCom/env/envSubr.c: In function 'envGetInetPortConfigParam':
> ../../../src/libCom/env/envSubr.c:411:21: error: 'IPPORT_USERRESERVED' undeclared (first use in this function)
>      if (epicsParam<=IPPORT_USERRESERVED || epicsParam>USHRT_MAX) {
>                      ^~~~~~~~~~~~~~~~~~~
> ../../../src/libCom/env/envSubr.c:411:21: note: each undeclared identifier is reported only once for each function it appears in
> make[3]: *** [../../../configure/RULES_BUILD:232: envSubr.o] Error 1
> make[3]: Leaving directory '/epics/base-3.15.6/src/libCom/O.linux-x86_64'
> make[2]: *** [../../configure/RULES_ARCHS:58: install.linux-x86_64] Error 2
> make[2]: Leaving directory '/epics/base-3.15.6/src/libCom'
> make[1]: *** [../configure/RULES_DIRS:84: libCom.install] Error 2
> make[1]: Leaving directory '/epics/base-3.15.6/src'
> ############# END ERROR SNIPPET ############# 
>
> The Asks:
> 1) Is there anyone who has some insights into this error or has built in Alpine?

The macro IPPORT_USERRESERVED is defined in /usr/include/netinet/in.h in my Linux (RHEL-7) system so my guess is that you need some networking -devel or similar package to be installed that provides that header or an equivalent. It’s definitely a standard networking constant so you just have to work out how to get hold of the right headers.

Our build documentation is somewhat out of date. If you want to test your build after it’s done, run ‘make runtests’ and it will execute the built-in test programs and report the results – always a good thing to do after building on a new OS-type.

Good luck!

- Andrew

--
Complexity comes for free, simplicity you have to work for.