Re: [Nasm-devel] build fails on OS X

[H. P. A. <hp...@zy...>]

On August 1, 2016 4:35:08 PM PDT, anonymous coward <nas...@us...> wrote:
>yeah, building definitely worked on this system
>a while back... but since then OS X has seen a
>bunch of updates... as has NASM's make
>
>fwiw, even with a step by step process...
>
> sh autogen.sh
> sh configure
>
> make
> make asm/pptok.h
> make
> make x86/insnsi.h
> make
> make asm/directiv.h
> make
> make x86/regs.h
> make
> make asm/tokens.h
> make
> make x86/iflaggen.h
> make
>
>...I get this at the end:
>
>gcc -c -g -O2 -fwrapv -W -Wall -std=c99 -pedantic
>-Werror=unknown-warning-option -Wno-long-long -Werror=implicit
>-Werror=missing-braces -Werror=return-type -Werror=trigraphs
>-Werror=pointer-arith -Werror=strict-prototypes
>-Werror=missing-prototypes -Werror=missing-declarations
>-Werror=comment -Werror=vla -DHAVE_CONFIG_H -I. -I. -I./include
>-I./include -I./x86 -I./x86 -I./asm -I./asm -I./disasm -I./disasm
>-I./output -I./output -o x86/iflag.o x86/iflag.c
>rm -f libnasm.a
>ar cq libnasm.a stdlib/snprintf.o stdlib/vsnprintf.o stdlib/strlcpy.o
>stdlib/strnlen.o nasmlib/ver.o nasmlib/crc64.o nasmlib/malloc.o
>nasmlib/error.o nasmlib/md5c.o nasmlib/string.o nasmlib/file.o
>nasmlib/ilog2.o nasmlib/realpath.o nasmlib/filename.o
>nasmlib/srcfile.o nasmlib/zerobuf.o nasmlib/readnum.o nasmlib/bsi.o
>nasmlib/rbtree.o nasmlib/hashtbl.o nasmlib/raa.o nasmlib/saa.o
>common/common.o x86/insnsa.o x86/insnsb.o x86/insnsd.o x86/insnsn.o
>x86/regs.o x86/regvals.o x86/regflags.o x86/regdis.o x86/disp8.o
>x86/iflag.o
>/Library/Developer/CommandLineTools/usr/bin/ranlib: file:
>libnasm.a(snprintf.o) has no symbols
>/Library/Developer/CommandLineTools/usr/bin/ranlib: file:
>libnasm.a(vsnprintf.o) has no symbols
>/Library/Developer/CommandLineTools/usr/bin/ranlib: file:
>libnasm.a(strlcpy.o) has no symbols
>/Library/Developer/CommandLineTools/usr/bin/ranlib: file:
>libnasm.a(strnlen.o) has no symbols
>ranlib libnasm.a
>/Library/Developer/CommandLineTools/usr/bin/ranlib: file:
>libnasm.a(snprintf.o) has no symbols
>/Library/Developer/CommandLineTools/usr/bin/ranlib: file:
>libnasm.a(vsnprintf.o) has no symbols
>/Library/Developer/CommandLineTools/usr/bin/ranlib: file:
>libnasm.a(strlcpy.o) has no symbols
>/Library/Developer/CommandLineTools/usr/bin/ranlib: file:
>libnasm.a(strnlen.o) has no symbols
>
>gcc  -o nasm asm/nasm.o asm/float.o asm/directiv.o asm/assemble.o
>asm/labels.o asm/parser.o asm/preproc.o asm/quote.o asm/pptok.o
>asm/listing.o asm/eval.o asm/exprlib.o asm/stdscan.o asm/strfunc.o
>asm/tokhash.o asm/segalloc.o asm/preproc-nop.o asm/rdstrnum.o
>macros/macros.o output/outform.o output/outlib.o output/nulldbg.o
>output/nullout.o output/outbin.o output/outaout.o output/outcoff.o
>output/outelf.o output/outobj.o output/outas86.o output/outrdf2.o
>output/outdbg.o output/outieee.o output/outmacho.o output/codeview.o
>libnasm.a
>Undefined symbols for architecture x86_64:
>  "_zero_buffer", referenced from:
>      _assemble in assemble.o
>      _out in assemble.o
>      _macho32_init in outmacho.o
>      _macho64_init in outmacho.o
>      _fwritezero in libnasm.a(file.o)
>ld: symbol(s) not found for architecture x86_64
>clang: error: linker command failed with exit code 1 (use -v to see
>invocation)
>make: *** [nasm] Error 1

What happens if you run "make alldeps" before making?
-- 
Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.