https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191943
--- Comment #12 from Bryan Drewery <bdrew...@freebsd.org> ---
(In reply to Eir Nym from comment #11)
> Thank you! This fixes issue... but
>
> Why can't I pass UNAME_r in /etc/make.conf ?
You can, see /usr/ports/CHANGES for example:
OSVERSION+= 1100036
UNAME_ENV+= OSVERSION=${OSVERSION}
UNAME_ENV+= UNAME_s=FreeBSD
UNAME_ENV+= UNAME_r=11.0-CURRENT
UNAME_ENV+= UNAME_v="${UNAME_s} ${UNAME_r}"
.MAKEFLAGS: ${UNAME_ENV}
MAKE_ENV+= ${UNAME_ENV}
CONFIGURE_ENV+= ${UNAME_ENV}
SCRIPTS_ENV+= ${UNAME_ENV}
Perhaps I should make it simpler so that setting UNAME_* auto propagates to the
environment.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
