When building libc with the syscall compatibility, don't also generate the
syscall assembly files. This results in conflicting dependencies and can cause unexpected results for parallel builds. This is because the .c file and the .S file both generate the same .o file. Submitted by: Simon Gerraty <sjg@juniper.net> Sponsored by: Juniper Networks
This commit is contained in:
parent
a8d044f390
commit
3166a207c5
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=219710
@ -18,7 +18,10 @@
|
||||
# Sources common to both syscall interfaces:
|
||||
SRCS+= stack_protector.c stack_protector_compat.c __error.c
|
||||
.if !defined(WITHOUT_SYSCALL_COMPAT)
|
||||
SRCS+= fcntl.c ftruncate.c lseek.c mmap.c pread.c pwrite.c truncate.c
|
||||
SYSCALL_COMPAT_SRCS= fcntl.c ftruncate.c lseek.c mmap.c pread.c \
|
||||
pwrite.c truncate.c
|
||||
SRCS+= ${SYSCALL_COMPAT_SRCS}
|
||||
NOASM+= ${SYSCALL_COMPAT_SRCS:S/.c/.o/}
|
||||
PSEUDO+= _fcntl.o
|
||||
.endif
|
||||
SRCS+= sigwait.c
|
||||
|
Loading…
Reference in New Issue
Block a user