Fix afterinstall rule for generating links to the real libcrypt
Submitted by: Geoff
This commit is contained in:
parent
c8023944f8
commit
db5408c498
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=2156
@ -1,5 +1,5 @@
|
|||||||
#
|
#
|
||||||
# $Id: Makefile,v 1.3 1994/08/09 18:52:52 csgr Exp $
|
# $Id: Makefile,v 1.4 1994/08/12 21:02:31 csgr Exp $
|
||||||
#
|
#
|
||||||
|
|
||||||
LCRYPTBASE= libcrypt
|
LCRYPTBASE= libcrypt
|
||||||
@ -18,25 +18,33 @@ SRCS= crypt.c
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
.include <bsd.lib.mk>
|
|
||||||
|
|
||||||
test:
|
test:
|
||||||
cd test ; make test ; make clean
|
cd test ; make test ; make clean
|
||||||
|
|
||||||
|
|
||||||
|
.include <bsd.lib.mk>
|
||||||
|
|
||||||
# We only install the links if they do not already exist.
|
# We only install the links if they do not already exist.
|
||||||
# This may have to be revised
|
# This may have to be revised
|
||||||
afterinstall:
|
afterinstall:
|
||||||
.if defined(SHLIB_MAJOR) && ! defined(NOSHARED)
|
.if !defined(NOPIC) && defined(SHLIB_MAJOR)
|
||||||
@if [ ! -e $(LCRYPTSO) ]; then \
|
@cd $(DESTDIR)/$(LIBDIR); \
|
||||||
cd $(DESTDIR)/$(LIBDIR); \
|
if [ ! -e $(LCRYPTSO) ]; then \
|
||||||
rm -f $(LCRYPTSO); \
|
rm -f $(LCRYPTSO); \
|
||||||
ln -s $(LDCRYPTSO) $(LCRYPTSO); \
|
ln -s $(LDCRYPTSO) $(LCRYPTSO); \
|
||||||
fi
|
fi
|
||||||
.endif
|
.endif
|
||||||
@if [ ! -e $(LCRYPTBASE).a ]; then \
|
@cd $(DESTDIR)/$(LIBDIR); \
|
||||||
cd $(DESTDIR)/$(LIBDIR); \
|
if [ ! -e $(LCRYPTBASE).a ]; then \
|
||||||
rm -f $(LCRYPTBASE).a $(LCRYPTBASE)_p.a; \
|
rm -f $(LCRYPTBASE).a; \
|
||||||
ln -s $(LDCRYPTBASE).a libcrypt.a; \
|
ln -s $(LDCRYPTBASE).a libcrypt.a; \
|
||||||
|
fi
|
||||||
|
.if !defined(NOPROFILE)
|
||||||
|
@cd $(DESTDIR)/$(LIBDIR); \
|
||||||
|
if [ ! -e $(LCRYPTBASE)_p.a ]; then \
|
||||||
|
rm -f $(LCRYPTBASE)_p.a; \
|
||||||
ln -s $(LDCRYPTBASE)_p.a libcrypt_p.a; \
|
ln -s $(LDCRYPTBASE)_p.a libcrypt_p.a; \
|
||||||
fi
|
fi
|
||||||
|
.endif
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user