filecoin-project / filecoin-ffi

C and CGO bindings for Filecoin's Rust libraries

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Build errors on M1 pro

nickboot opened this issue · comments

m1 Pro macOS 12.1 Xcode 13.2.1 Build lotus v1.13.2

Error

╰─➤ make all rm -f lotus go build -ldflags="-X=github.com/filecoin-project/lotus/build.CurrentCommit=+git.f9db71ee1.dirty -extldflags=-framework OpenCL" -o lotus ./cmd/lotus github.com/filecoin-project/filecoin-ffi/generated ld: warning: ignoring file /opt/homebrew/lib/libhwloc.dylib, building for macOS-x86_64 but attempting to link with file built for macOS-arm64 ld: warning: ignoring file /Users/m1/workspace/filecoin-project/lotus/extern/filecoin-ffi/libfilcrypto.a, building for macOS-x86_64 but attempting to link with file built for macOS-arm64 Undefined symbols for architecture x86_64:

commented

This looks like a known warning. Can you confirm the build does not complete?

╰─➤ make all 2 ↵
rm -f lotus
go build -ldflags="-X=github.com/filecoin-project/lotus/build.CurrentCommit=+git.f9db71ee1.dirty" -o lotus ./cmd/lotus

github.com/filecoin-project/filecoin-ffi/generated

ld: warning: ignoring file /opt/homebrew/lib/libhwloc.dylib, building for macOS-x86_64 but attempting to link with file built for macOS-arm64
ld: warning: ignoring file /Users/m1/workspace/filecoin-project/lotus/extern/filecoin-ffi/libfilcrypto.a, building for macOS-x86_64 but attempting to link with file built for macOS-arm64
Undefined symbols for architecture x86_64:
"_fil_aggregate", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_aggregate in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_aggregate, __cgo_fe0a164c3578_Cfunc_fil_aggregate_seal_proofs )
"_fil_aggregate_seal_proofs", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_aggregate_seal_proofs in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_aggregate_seal_proofs)
"_fil_clear_cache", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_clear_cache in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_clear_cache)
"_fil_create_zero_signature", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_create_zero_signature in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_create_zero_signature)
"_fil_destroy_aggregate_proof", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_aggregate_proof in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_aggregate_proof)
"_fil_destroy_aggregate_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_aggregate_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_aggregate_response)
"_fil_destroy_clear_cache_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_clear_cache_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_clear_cache_response)
"_fil_destroy_fauxrep_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_fauxrep_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_fauxrep_response)
"_fil_destroy_finalize_ticket_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_finalize_ticket_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_finalize_ticket_response)
"_fil_destroy_generate_data_commitment_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_generate_data_commitment_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_generate_data_commitment_response)
"_fil_destroy_generate_fallback_sector_challenges_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_generate_fallback_sector_challenges_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_generate_fallback_sector_challenges_response)
"_fil_destroy_generate_piece_commitment_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_generate_piece_commitment_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_generate_piece_commitment_response)
"_fil_destroy_generate_single_vanilla_proof_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_generate_single_vanilla_proof_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_generate_single_vanilla_proof_response)
"_fil_destroy_generate_single_window_post_with_vanilla_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_generate_single_window_post_with_vanilla_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_generate_single_window_post_with_vanilla_response)
"_fil_destroy_generate_window_post_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_generate_window_post_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_generate_window_post_response)
"_fil_destroy_generate_winning_post_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_generate_winning_post_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_generate_winning_post_response)
"_fil_destroy_generate_winning_post_sector_challenge", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_generate_winning_post_sector_challenge in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_generate_winning_post_sector_challenge)
"_fil_destroy_get_num_partition_for_fallback_post_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_get_num_partition_for_fallback_post_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_get_num_partition_for_fallback_post_response)
"_fil_destroy_gpu_device_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_gpu_device_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_gpu_device_response)
"_fil_destroy_hash_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_hash_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_hash_response)
"_fil_destroy_init_log_fd_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_init_log_fd_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_init_log_fd_response)
"_fil_destroy_merge_window_post_partition_proofs_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_merge_window_post_partition_proofs_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_merge_window_post_partition_proofs_response)
"_fil_destroy_private_key_generate_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_private_key_generate_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_private_key_generate_response)
"_fil_destroy_private_key_public_key_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_private_key_public_key_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_private_key_public_key_response)
"_fil_destroy_private_key_sign_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_private_key_sign_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_private_key_sign_response)
"_fil_destroy_seal_commit_phase1_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_seal_commit_phase1_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_seal_commit_phase1_response)
"_fil_destroy_seal_commit_phase2_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_seal_commit_phase2_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_seal_commit_phase2_response)
"_fil_destroy_seal_pre_commit_phase1_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_seal_pre_commit_phase1_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_seal_pre_commit_phase1_response)
"_fil_destroy_seal_pre_commit_phase2_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_seal_pre_commit_phase2_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_seal_pre_commit_phase2_response)
"_fil_destroy_string_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_string_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_string_response)
"_fil_destroy_unseal_range_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_unseal_range_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_unseal_range_response)
"_fil_destroy_verify_aggregate_seal_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_verify_aggregate_seal_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_verify_aggregate_seal_response)
"_fil_destroy_verify_seal_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_verify_seal_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_verify_seal_response)
"_fil_destroy_verify_window_post_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_verify_window_post_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_verify_window_post_response)
"_fil_destroy_verify_winning_post_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_verify_winning_post_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_verify_winning_post_response)
"_fil_destroy_write_with_alignment_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_write_with_alignment_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_write_with_alignment_response)
"_fil_destroy_write_without_alignment_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_write_without_alignment_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_write_without_alignment_response)
"_fil_destroy_zero_signature_response", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_destroy_zero_signature_response in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_destroy_zero_signature_response)
"_fil_drop_signature", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_drop_signature in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_drop_signature)
"_fil_fauxrep", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_fauxrep in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_fauxrep2, __cgo_fe0a164c3578_Cfunc_fil_fauxrep )
"_fil_fauxrep2", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_fauxrep2 in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_fauxrep2)
"_fil_generate_data_commitment", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_data_commitment in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_data_commitment)
"_fil_generate_fallback_sector_challenges", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_fallback_sector_challenges in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_fallback_sector_challenges)
"_fil_generate_piece_commitment", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_piece_commitment in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_piece_commitment)
"_fil_generate_single_vanilla_proof", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_single_vanilla_proof in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_single_vanilla_proof)
"_fil_generate_single_window_post_with_vanilla", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_single_window_post_with_vanilla in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_single_window_post_with_vanilla)
"_fil_generate_window_post", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_window_post in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_window_post_with_vanilla, __cgo_fe0a164c3578_Cfunc_fil_generate_window_post )
"_fil_generate_window_post_with_vanilla", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_window_post_with_vanilla in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_window_post_with_vanilla)
"_fil_generate_winning_post", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_winning_post in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_winning_post_with_vanilla, __cgo_fe0a164c3578_Cfunc_fil_generate_winning_post_sector_challenge , __cgo_fe0a164c3578_Cfunc_fil_generate_winning_post )
"_fil_generate_winning_post_sector_challenge", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_winning_post_sector_challenge in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_winning_post_sector_challenge)
"_fil_generate_winning_post_with_vanilla", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_generate_winning_post_with_vanilla in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_generate_winning_post_with_vanilla)
"_fil_get_gpu_devices", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_gpu_devices in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_gpu_devices)
"_fil_get_max_user_bytes_per_staged_sector", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_max_user_bytes_per_staged_sector in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_max_user_bytes_per_staged_sector)
"_fil_get_num_partition_for_fallback_post", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_num_partition_for_fallback_post in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_num_partition_for_fallback_post)
"_fil_get_post_circuit_identifier", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_post_circuit_identifier in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_post_circuit_identifier)
"_fil_get_post_params_cid", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_post_params_cid in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_post_params_cid)
"_fil_get_post_params_path", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_post_params_path in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_post_params_path)
"_fil_get_post_verifying_key_cid", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_post_verifying_key_cid in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_post_verifying_key_cid)
"_fil_get_post_verifying_key_path", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_post_verifying_key_path in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_post_verifying_key_path)
"_fil_get_post_version", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_post_version in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_post_version)
"_fil_get_seal_circuit_identifier", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_seal_circuit_identifier in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_seal_circuit_identifier)
"_fil_get_seal_params_cid", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_seal_params_cid in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_seal_params_cid)
"_fil_get_seal_params_path", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_seal_params_path in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_seal_params_path)
"_fil_get_seal_verifying_key_cid", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_seal_verifying_key_cid in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_seal_verifying_key_cid)
"_fil_get_seal_verifying_key_path", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_seal_verifying_key_path in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_seal_verifying_key_path)
"_fil_get_seal_version", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_get_seal_version in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_get_seal_version)
"_fil_hash", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_hash in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_hash_verify, __cgo_fe0a164c3578_Cfunc_fil_hash )
"_fil_hash_verify", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_hash_verify in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_hash_verify)
"_fil_init_log_fd", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_init_log_fd in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_init_log_fd)
"_fil_merge_window_post_partition_proofs", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_merge_window_post_partition_proofs in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_merge_window_post_partition_proofs)
"_fil_private_key_generate", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_private_key_generate in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_private_key_generate, __cgo_fe0a164c3578_Cfunc_fil_private_key_generate_with_seed )
"_fil_private_key_generate_with_seed", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_private_key_generate_with_seed in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_private_key_generate_with_seed)
"_fil_private_key_public_key", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_private_key_public_key in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_private_key_public_key)
"_fil_private_key_sign", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_private_key_sign in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_private_key_sign)
"_fil_seal_commit_phase1", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_seal_commit_phase1 in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_seal_commit_phase1)
"_fil_seal_commit_phase2", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_seal_commit_phase2 in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_seal_commit_phase2)
"_fil_seal_pre_commit_phase1", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_seal_pre_commit_phase1 in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_seal_pre_commit_phase1)
"_fil_seal_pre_commit_phase2", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_seal_pre_commit_phase2 in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_seal_pre_commit_phase2)
"_fil_unseal_range", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_unseal_range in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_unseal_range)
"_fil_verify", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_verify in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_verify_winning_post, __cgo_fe0a164c3578_Cfunc_fil_verify_seal , __cgo_fe0a164c3578_Cfunc_fil_verify , __cgo_fe0a164c3578_Cfunc_fil_verify_window_post , __cgo_fe0a164c3578_Cfunc_fil_verify_aggregate_seal_proof )
"_fil_verify_aggregate_seal_proof", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_verify_aggregate_seal_proof in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_verify_aggregate_seal_proof)
"_fil_verify_seal", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_verify_seal in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_verify_seal)
"_fil_verify_window_post", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_verify_window_post in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_verify_window_post)
"_fil_verify_winning_post", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_verify_winning_post in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_verify_winning_post)
"_fil_write_with_alignment", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_write_with_alignment in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_write_with_alignment)
"_fil_write_without_alignment", referenced from:
__cgo_fe0a164c3578_Cfunc_fil_write_without_alignment in _x004.o
(maybe you meant: __cgo_fe0a164c3578_Cfunc_fil_write_without_alignment)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [lotus] Error 2