[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OS X Build Errors

To: Dominyk Tiller <dominyktiller@gmail.com>
Subject: Re: OS X Build Errors
From: Frederick Akalin <akalin@gmail.com>
Date: Sat, 30 Aug 2014 11:24:09 -0700
Cc: spiped@tarsnap.com, Colin Percival <cperciva@tarsnap.com>
In-reply-to: <54018CA8.9000807@gmail.com>
References: <54018CA8.9000807@gmail.com>

Did you see my post earlier today? http://mail.tarsnap.com/spiped/msg00098.html

On Sat, Aug 30, 2014 at 1:34 AM, Dominyk Tiller <dominyktiller@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hey all,
>
> Trying to compile the latest spiped release on OS X and hitting the
> same set of errors, both with BSDMake and GNUMake. The last version of
> spiped compiled without issue.
>
> This is my compile:
>
> bsdmake BINDIR=/Users/Bob/Downloads/spiped-1.4.0/BUILDINGTEMP   install
> export CFLAGS="${CFLAGS:--O2}"; \
>         export LDADD_POSIX=`export CC="cc"; cd POSIX && command -p sh
> posix-l.sh`;    \
>         export CFLAGS_POSIX=`export CC="cc"; cd POSIX && command -p sh
> posix-cflags.sh`;       \
>         ( export CC="cc"; cd libcperciva/cpusupport/Build && command -p sh
> cpusupport.sh ) > cpusupport-config.h;  \
>         . ./cpusupport-config.h;                        \
>         for D in spiped spipe; do                               \
>                 ( cd ${D} && make all ) || exit 2;      \
>         done
> WARNING: POSIX violation: make's CC doesn't understand -lrt
> WARNING: POSIX violation: make's CC doesn't understand -lxnet
> WARNING: POSIX violation: <sys/socket.h> not defining MSG_NOSIGNAL
> WARNING: POSIX violation: <time.h> not defining CLOCK_REALTIME
> Checking if compiler supports X86 CPUID feature... yes
> Checking if compiler supports X86 AESNI feature... yes, via -maes
> cc -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> clang: error: no input files
> make[1]: *** [main.o] Error 1
> make: *** [all] Error 2
>
> Homebrew got a little further than I did, but still ended in failure:
>
> ==> bsdmake BINDIR_DEFAULT=/usr/local/Cellar/spiped/1.4.0/bin
> MAN1DIR=/usr/local/Cellar/spiped/1.4.0/share/man/man1 install
> export CFLAGS="${CFLAGS:--O2}";  export LDADD_POSIX=`export
> CC="clang"; cd POSIX && command -p sh posix-l.sh`;       export
> CFLAGS_POSIX=`export CC="clang"; cd POSIX && command -p sh
> posix-cflags.sh`;        ( export CC="clang"; cd
> libcperciva/cpusupport/Build && command -p sh cpusupport.sh ) >
> cpusupport-config.h;     . ./cpusupport-config.h;                        for D in spiped
> spipe; do                                ( cd ${D} && make all ) || exit 2;      done
> export CC="clang"; cd POSIX && command -p sh posix-l.sh
> WARNING: POSIX violation: make's CC doesn't understand -lrt
> WARNING: POSIX violation: make's CC doesn't understand -lxnet
> export CC="clang"; cd POSIX && command -p sh posix-cflags.sh
> WARNING: POSIX violation: <sys/socket.h> not defining MSG_NOSIGNAL
> WARNING: POSIX violation: <time.h> not defining CLOCK_REALTIME
> Checking if compiler supports X86 CPUID feature... yes
> Checking if compiler supports X86 AESNI feature... yes, via -maes
> #define CPUSUPPORT_X86_CPUID
> #define CPUSUPPORT_X86_AESNI
> #ifdef cpusupport_dummy
> export CFLAGS_X86_AESNI="-maes"
> #endif
> clang -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> clang -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> clang -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> clang -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> clang -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> clang -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> clang -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> clang -O2 -DPOSIXFAIL_MSG_NOSIGNAL
> Undefined symbols for architecture x86_64:
>   "_main", referenced from:
>      implicit entry/start for main executable
> Undefined symbols for architecture x86_64:
>   "_main", referenced from:
>      implicit entry/start for main executable
> ld: symbol(s) not found for architecture x86_64
> ld: symbol(s) not found for architecture x86_64
> Undefined symbols for architecture x86_64:
>   "_main", referenced from:
>      implicit entry/start for main executable
> ld: symbol(s) not found for architecture x86_64
> Undefined symbols for architecture x86_64:
>   "_main", referenced from:
>      implicit entry/start for main executable
> Undefined symbols for architecture x86_64:
>   "_main", referenced from:
>      implicit entry/start for main executable
> ld: symbol(s) not found for architecture x86_64
> ld: symbol(s) not found for architecture x86_64
> Undefined symbols for architecture x86_64:
> Undefined symbols for architecture x86_64:
>   "_main", referenced from:
>      implicit entry/start for main executable
>   "_main", referenced from:
>      implicit entry/start for main executable
> ld: symbol(s) not found for architecture x86_64
> ld: symbol(s) not found for architecture x86_64
> Undefined symbols for architecture x86_64:
>   "_main", referenced from:
>      implicit entry/start for main executable
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> make: *** [elasticarray.o] Error 1
> make: *** Waiting for unfinished jobs....
> make: *** [sha256.o] Error 1
> make: *** [proto_pipe.o] Error 1
> make: *** [proto_crypt.o] Error 1
> make: *** [proto_conn.o] Error 1
> make: *** [dispatch.o] Error 1
> make: *** [main.o] Error 1
> make: *** [proto_handshake.o] Error 1
> *** Error code 2
> 1 error
>
> Any ideas on this? Appreciate any feedback.
>
> Dom
> - --
> Sent from Thunderbird for OS X. My PGP public key is automatically
> attached to this email.
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - https://gpgtools.org
>
> iQIcBAEBCgAGBQJUAYynAAoJEIclJNuddDJsEtIP/j4Hjvz5Wo2W/2Ri9Njio9hM
> t+l2oUL/wkxPkwMqtJgixlKgrBjOQY7y6CUHHCm7pZd/Np8xObcpyJXzrnu8s/as
> SHbXeB6E/s5c5u13FgcH/zNK3NAf4Io1IFBqTRg7PPjaVRIyl9seZAM20nx2+qEL
> G6PIE6GLREjpIKM+JA0jicbm6zezpHIMy7jrpO1H3jMfBAvD3uX2Bw20s5l1rTlI
> zGyfemMjjjgqyZg9Ye0Q4ZIlyCo4AdwCcoQbvWJuNrE1158UR9I5bDmEXHgn63mt
> DyuoIfqLLtWDcTKKieqwmJ64odd2/OMMy9hUSptw78uGBPj7xhKq6LwT0qo1V2UI
> 9O6qJZdwzecysvSlpudNMsuQa4+PCTAIaMLXOya7vJMgRH5v4Xa1dgHL0sugv+cf
> g+Fz+4wX7OZvr5JDPGrNAXwuv9acEOYHgdsX1R0BPo0Z5wAZ07KyVZ1i8PztPnDS
> +FOeFZyMrUHiXp4EbSgWYO3AKagHv5cmpYJaCHsOm2RPMqfn8KLbm8sH6atsgCEi
> cCSt5YDDgrVBIx8bFZcp9tDauYDNaKmO7pmfqrDOx6LZPmZc6kRYSpFnu6OoLaD6
> leb0uz1c1wFx5z5eHslJchdJwVSn2mpKK5t2zlHRYeEtunzidoa4A12GnmVsNz6m
> FWVCB4MzFdXn0Nf5bukS
> =pJZg
> -----END PGP SIGNATURE-----

Follow-Ups:
- Re: OS X Build Errors
  - From: Colin Percival <cperciva@tarsnap.com>
- Re: OS X Build Errors
  - From: Frederick Akalin <akalin@gmail.com>

References:
- OS X Build Errors
  - From: Dominyk Tiller <dominyktiller@gmail.com>

Prev by Date: Re: Potential spiped 1.4.0 release -- please test
Next by Date: Re: OS X Build Errors
Previous by thread: OS X Build Errors
Next by thread: Re: OS X Build Errors
Index(es):
- Date
- Thread