- changed title to using libutil's efun(3) in sed(1) may cause build.sh tools failure on non-N**BSD for cross build
-
assigned issue to
- edited description
using libutil's efun(3) in sed(1) may cause build.sh tools failure on non-N**BSD for cross build
Issue #284
resolved
apparently USETOOLS doesn’t have libutil and efun(3)
Comments (3)
-
reporter -
reporter - efun(3) is already included in libnbcompat
- usr.bin/Makefile need -lutil
- but tools/sed/Makefile need -lnbcompat
- so that if HOSTPROG is true, don’t try to link -lutil
diff --git a/usr.bin/sed/Makefile b/usr.bin/sed/Makefile index 7c3f7cc..3d34ce2 100644 --- a/usr.bin/sed/Makefile +++ b/usr.bin/sed/Makefile @@ -1,11 +1,16 @@ # $NetBSD: Makefile,v 1.14 2009/04/14 22:15:26 lukem Exp $ # from: @(#)Makefile 8.1 (Berkeley) 6/6/93 +.ifndef HOSTPROG .include <bsd.own.mk> +.endif PROG= sed SRCS= compile.c main.c misc.c process.c + +.ifndef HOSTPROG DPADD= ${LIBUTIL} LDADD= -lutil +.endif
-
reporter - changed status to resolved
BUGFIX: Issue
#284- using libutil's efun(3) in sed(1) may cause build.sh tools failure on non-N**BSD for cross build→ <<cset bf8fce2b1f45>>
- Log in to comment