[
https://issues.apache.org/jira/browse/MINIFICPP-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814983#comment-16814983
]
Dustin Rodrigues commented on MINIFICPP-655:
--------------------------------------------
[~ottobackwards] Installing bison via homebrew and manually setting the path
does work. However, I'd expect "./bootstrap.sh -e -t && cd build && make" to
work on a machine with just homebrew installed. As it stands, if bison isn't
installed or bison is installed with brew and the path isn't set, the bootstrap
script finds the OS-provided bison which is bison 2.3, decides its now new
enough since it's not 3.x, and tries to wget and install bison using commands
for SUSE. I filed https://issues.apache.org/jira/browse/MINIFICPP-799 for this.
Even if bootstrap did install bison via homebrew, "brew link bison --force"
won't work anymore since homebrew won't allow the linking which means that
cmake will need to explicitly look for the homebrew-installed bison to avoid
only finding the OS-provided one.
> Issues building on OSX 10.14 (Mojave)
> -------------------------------------
>
> Key: MINIFICPP-655
> URL: https://issues.apache.org/jira/browse/MINIFICPP-655
> Project: NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Dustin Rodrigues
> Priority: Major
>
> There are issues building on OSX Mojave when attempting to use homebrew
> dependencies. Homebrew refuses to link macOS-provided software into
> /usr/local/{bin,lib,include} such as bison, flex, and curl and possibly
> others. cmake needs to be aware of the homebrew-installed locations of
> /usr/local/opt/PROGRAMNAME .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
