mirror of
https://git.freebsd.org/ports.git
synced 2026-06-02 11:08:52 +00:00
afafb6c5732e0d0fa72ad5cb3953367c3466455e
/bin/sh ../../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I./../include -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -std=c++0x -MT fst.lo -MD -MP -MF .deps/fst.Tpo -c -o fst.lo fst.cc
libtool: compile: c++ -DHAVE_CONFIG_H -I./../include -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -std=c++0x -MT fst.lo -MD -MP -MF .deps/fst.Tpo -c fst.cc -o fst.o
In file included from fst.cc:26:
In file included from ./../include/fst/matcher-fst.h:26:
In file included from ./../include/fst/lookahead-matcher.h:28:
In file included from ./../include/fst/label-reachable.h:32:
In file included from ./../include/fst/accumulator.h:36:
In file included from ./../include/fst/replace.h:40:
In file included from ./../include/fst/state-table.h:31:
./../include/fst/bi-table.h:356:31: error: no member named 's_' in 'VectorHashBiTable<I, T, S, FP, H, HS>'
356 | : selector_(new S(table.s_)),
| ~~~~~ ^
1 error generated.
Upstream has since rewritten the whole thing in Python.
Perhaps an update is in order.
Approved by: portmgr (build fix blanket)
…
…
…
This is the FreeBSD Ports Collection. For an easy to use WEB-based interface to it, please see: https://ports.FreeBSD.org For general information on the Ports Collection, please see the FreeBSD Handbook ports section which is available from: https://docs.freebsd.org/en/books/handbook/ports/ for the latest official version or: The ports(7) manual page (man ports). These will explain how to use ports and packages. If you would like to search for a port, you can do so easily by saying (in /usr/ports): make search name="<name>" or: make search key="<keyword>" which will generate a list of all ports matching <name> or <keyword>. make search also supports wildcards, such as: make search name="gtk*" For information about contributing to FreeBSD ports, please see the Porter's Handbook, available at: https://docs.freebsd.org/en/books/porters-handbook/ NOTE: This tree will GROW significantly in size during normal usage! The distribution tar files can and do accumulate in /usr/ports/distfiles, and the individual ports will also use up lots of space in their work subdirectories unless you remember to "make clean" after you're done building a given port. /usr/ports/distfiles can also be periodically cleaned without ill-effect.
Description
Languages
Makefile
45.8%
C++
19.5%
C
18.3%
Shell
4.7%
Roff
4.4%
Other
5.9%