[
https://issues.apache.org/jira/browse/DAFFODIL-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17676315#comment-17676315
]
John Interrante commented on DAFFODIL-2516:
-------------------------------------------
I don't have users working on Daffodil or runtime2 who need FreeBSD, although I
could start up a FreeBSD Vagrant box if necessary.
How are Makefiles supposed to know that FreeBSD packages are installed in
/usr/local instead of /usr? Most C compilers do not include /usr/local paths
in their pre-initialized system directory search paths so a Makefile would have
to use explicit -I and -L flags when compiling runtime2. How hard is it to
make FreeBSD install Mini-XML in /usr?
We now use p_endian.h to accommodate macOS; we probably just need a slight
modification to handle FreeBSD too.
> runtime2 does not compile on FreeBSD
> ------------------------------------
>
> Key: DAFFODIL-2516
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2516
> Project: Daffodil
> Issue Type: Bug
> Components: Back End C-Generator
> Affects Versions: 3.1.0
> Reporter: Steve Lawrence
> Priority: Minor
>
> runtime2 does not compile on FreeBSD because because of different include
> locations, from a user:
> 1. It looked like the runtime2 C code was looking for the Mini-XML
> dependencies under /usr whereas the package on FreeBSD is stored under
> /usr/local, and;
> 2. Some C files under runtime2 were including <endian.h> whereas the file was
> under /usr/include/sys.
> CFLAGS env variable support might help with this, or maybe there are some
> system properties that could be read to add include locations. Might also be
> able to look for/use pkg-config too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
