Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build on OSX #8

Open
wapowell opened this issue May 17, 2017 · 3 comments
Open

Build on OSX #8

wapowell opened this issue May 17, 2017 · 3 comments
Labels

Comments

@wapowell
Copy link

wapowell commented May 17, 2017

$ make
getconf: no such configuration parameter LFS_CFLAGS' gcc -D_FORTIFY_SOURCE=2 -O2 -fstack-protector --param=ssp-buffer-size=4 -Wall -Wextra -std=gnu99 -pedantic -Wformat -Werror=format-security -g -c pcap.c -o pcap.o getconf: no such configuration parameter LFS_CFLAGS'
gcc -D_FORTIFY_SOURCE=2 -O2 -fstack-protector --param=ssp-buffer-size=4 -Wall -Wextra -std=gnu99 -pedantic -Wformat -Werror=format-security -g -c pcapng.c -o pcapng.o
pcapng.c:377:118: warning: format specifies type 'unsigned long long' but the
argument has type 'unsigned long' [-Wformat]
...(%" PRIu64 " > %" PRId64 ") ==> SKIPPING.\n", packets, sizeof(pb), left);
~~~ ^~~~~~~~~~
1 warning generated.
getconf: no such configuration parameter `LFS_CFLAGS'
gcc -D_FORTIFY_SOURCE=2 -O2 -fstack-protector --param=ssp-buffer-size=4 -Wall -Wextra -std=gnu99 -pedantic -Wformat -Werror=format-security -g -Wl,-z,relro pcapfix.c pcap.o pcapng.o -o pcapfix
ld: unknown option: -z
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [all] Error 1

I used the latest from the repository.
I'm on 10.10.5 Yosemite.

@wapowell wapowell changed the title Buils on OSX Build on OSX May 17, 2017
@Rup0rt
Copy link
Owner

Rup0rt commented Jun 25, 2018

Can somebody using OSX tell me how to fix this?

@Rup0rt Rup0rt added the bug label Oct 29, 2018
@mdeweerd mdeweerd mentioned this issue Sep 12, 2020
@Rup0rt
Copy link
Owner

Rup0rt commented Jan 20, 2021

Some changes have been made to the makefile. Can you check the devel branch whether this problem still exists?

@wolveix
Copy link

wolveix commented Nov 4, 2023

@Rup0rt working here on the latest version of macOS (10.14, Sonoma)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants