libfsm
libfsm copied to clipboard
`make install` fails
When I run bmake PREFIX=$out install
, it fails, with the last few lines saying:
install -m 644 build/pc /nix/store/jj9j4kylaprcpy46gpdjb2mj119vbdpr-libfsm/share/pkgconfig/pc
install: omitting directory 'build/pc'
*** Error code 1
I'm a bit confused by this — I can't reproduce the same effect. Did you intentionally elide -r
there? That's required, so as not to use bmake's pre-supplied sys.mk files.
I don't understand where the rule for build/pc
would come from, though.
; bmake -r PREFIX=/tmp/x install
install -m 755 -d /tmp/x/bin
install -m 755 -d /tmp/x/include/fsm
install -m 755 -d /tmp/x/include/re
install -m 755 -d /tmp/x/lib
install -m 755 -d /tmp/x/share/pkgconfig
install -m 644 build/pc/libfsm.pc /tmp/x/share/pkgconfig/libfsm.pc
install -m 644 build/pc/libre.pc /tmp/x/share/pkgconfig/libre.pc
install -m 644 build/lib/libfsm.a /tmp/x/lib/libfsm.a
install -m 644 build/lib/libre.a /tmp/x/lib/libre.a
install -m 644 build/lib/libfsm.so /tmp/x/lib/libfsm.so
install -m 644 build/lib/libre.so /tmp/x/lib/libre.so
install -m 755 build/bin/fsm /tmp/x/bin/fsm
install -m 755 build/bin/re /tmp/x/bin/re
install -m 755 build/bin/lx /tmp/x/bin/lx
install -m 644 include/fsm/bool.h /tmp/x/include/fsm/bool.h
install -m 644 include/fsm/cost.h /tmp/x/include/fsm/cost.h
install -m 644 include/fsm/fsm.h /tmp/x/include/fsm/fsm.h
install -m 644 include/fsm/options.h /tmp/x/include/fsm/options.h
install -m 644 include/fsm/pred.h /tmp/x/include/fsm/pred.h
install -m 644 include/fsm/print.h /tmp/x/include/fsm/print.h
install -m 644 include/fsm/walk.h /tmp/x/include/fsm/walk.h
install -m 644 include/re/re.h /tmp/x/include/re/re.h
; ls /tmp/x/share/pkgconfig
libfsm.pc libre.pc
I wonder if this is the same cause from #107
Arch Linux, bmake package from crufty.net
bmake -r
ld: build/src/libre/dialect/like/parser.o:(.bss+0x0): multiple definition of
ast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/dialect/literal/parser.o:(.bss+0x0): multiple definition of
ast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/dialect/native/parser.o:(.bss+0x0): multiple definition ofast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/dialect/pcre/parser.o:(.bss+0x0): multiple definition of
ast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/dialect/sql/parser.o:(.bss+0x0): multiple definition ofast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/print/dot.o:(.bss+0x0): multiple definition of
ast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/print/abnf.o:(.bss+0x0): multiple definition ofast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/print/pcre.o:(.bss+0x0): multiple definition of
ast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/print/tree.o:(.bss+0x0): multiple definition ofast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/re.o:(.bss+0x0): multiple definition of
ast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/ast.o:(.data.rel.local+0x0): multiple definition ofast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/ast_analysis.o:(.bss+0x0): multiple definition of
ast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/ast_compile.o:(.bss+0x0): multiple definition ofast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here ld: build/src/libre/ast_rewrite.o:(.bss+0x0): multiple definition of
ast_expr_tombstone'; build/src/libre/dialect/glob/parser.o:(.bss+0x0): first defined here
@data-man thanks! That seems like a genuine bug. Perhaps that symbol is being defined in the wrong place.
@data-man this should be fixed now as of #239, thank you.
I'm leaving this ticket open because @jameysharp's reported issue is still present.
Thanks! Now I can try. :)