[Bug 193446] lang/icc: Add RESTRICTED, Take Maintainership
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Sep 8 14:18:11 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193446
--- Comment #2 from Carlos Jacobo Puga Medina <cpm at fbsd.es> ---
Build logs via poudriere on 8.4-i386, 9.2-i386 and 10.0-i386
https://fbsd.es/~cpm/freebsd/poudriere/freebsd:8:x86:32/icc-8.1.038_2.log
https://fbsd.es/~cpm/freebsd/poudriere/freebsd:9:x86:32/icc-8.1.038_2.log
https://fbsd.es/~cpm/freebsd/poudriere/freebsd:10:x86:32/icc-8.1.038_2.log
portlint -AC output:
WARN: Makefile: [58]: IGNORE messages should begin with a lowercase letter and
end without a period.
WARN: Makefile: possible use of absolute pathname "/usr/include/c++/${G...".
WARN: Makefile: possible use of absolute pathname "/usr/lib/${f}".
WARN: Makefile: possible direct use of "work" " @${ECHO} "Please use FreeBSD
as the name of your OS in communications with the support, the larger the
FreeBSD userbase is, the more work gets done on FreeBSD specific issues by
Intel. And please thank them for the FreeBSD support, they are already spending
some time to improve icc on FreeBSD." | fmt" found. if so, use ${WRKDIR}
instead.
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section empty, to
make SVN happy.
WARN: Makefile: new ports should not set PORTREVISION.
WARN: Makefile: no MASTER_SITES found. is it ok?
WARN: Makefile: use of DISTFILES with single file discouraged. distribution
filename should be set by DISTNAME and EXTRACT_SUFX.
WARN: Makefile: Consider defining LICENSE.
WARN: Makefile: "EXTRACT_DEPENDS" has to appear earlier.
WARN: Makefile: "PATCH_DEPENDS" has to appear earlier.
WARN: Makefile: do not use DISTFILES and DISTNAME to control WRKSRC. how about
"WRKSRC=${WRKDIR}/l_cc_pc_${PORTVERSION:C/p.+$//}"?
WARN: Makefile: "RESTRICTED" found. do not forget to update ports/LEGAL.
WARN: Consider to set DEVELOPER=yes in /etc/make.conf
0 fatal errors and 14 warnings found.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list