unpbook / unpv13e Goto Github PK

I was looking for implemenation of "void Unlink(const char*)" which is declare in unp.h. I could not find implementation

As the title said, I am looking for the pdf of UNIX NETWORK PROGRAMING ... it's very hard to find a free one on our net...

After running "'/configure --prefix=pwd" a "make" in libroute gives the following error:

fatal error: net/if_dl.h: No such file or directory
3 | #include <net/if_dl.h> /* sockaddr_sdl{} */

Why not any update related?

When I compiled the code on MacOS 10.15.3
I got the error as shown below

sunjiantaodeAir:libfree bryan$ make
gcc -I../lib -g -O2 -D_REENTRANT -Wall -c -o in_cksum.o in_cksum.c
gcc -I../lib -g -O2 -D_REENTRANT -Wall -c -o inet_ntop.o inet_ntop.c
gcc -I../lib -g -O2 -D_REENTRANT -Wall -c -o inet_pton.o inet_pton.c
ar rv ../libunp.a in_cksum.o inet_ntop.o inet_pton.o
a - in_cksum.o
a - inet_ntop.o
a - inet_pton.o
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: ../libunp.a(inet_ntop.o) has no symbols
ranlib ../libunp.a
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: ../libunp.a(inet_ntop.o) has no symbols

Could you please give some help?
Thanks!

/usr/bin/clang++ -std=gnu++14 -fcolor-diagnostics -fansi-escape-codes -g /Users/houzhiyang/Desktop/projectC/hw/socket.cpp -o /Users/houzhiyang/Desktop/projectC/hw/socket -std=c++11 -lunp
Undefined symbols for architecture x86_64:
"Bind(int, sockaddr const*, unsigned int)", referenced from:
_main in socket-5d6d69.o
"Close(int)", referenced from:
_main in socket-5d6d69.o
"Write(int, void*, unsigned long)", referenced from:
_main in socket-5d6d69.o
"Accept(int, sockaddr*, unsigned int*)", referenced from:
_main in socket-5d6d69.o
"Listen(int, int)", referenced from:
_main in socket-5d6d69.o
"Socket(int, int, int)", referenced from:
_main in socket-5d6d69.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

What should I do?I have tried adding the - lunp option, but nothing to happen

I've noticed that in the lib folder that are at least a few files that take a socklen_t parameter. Notable examples of this are sock_cmp_addr, sock_cmp_port, and sock_get_port (although, there are others).

None of these functions actually use the socklen_t parameter. Moreover, the sockaddr_in and sockaddr_in6 structs have their on sa_len member. Any idea why the author required the socklen_t parameter despite not actually using it?