11.1-jail on CURRENT: sh: lint: not found *** [llib-lposix.ln]

Discussion:

(too old to reply)

Warner Losh

2018-01-08 07:07:53 UTC

Does building -DWITHOUT_LINT work? Or linking lint to /bin/true

Warner

We have a bunch of CURRENT boxes running poudriere jails providing
packages for
11.1-RELENG. Since a couple of week sfor now, I face this error when I try
to
[...]
cc -O2 -pipe
-I/pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/xlint/../lint1
-DPREFIX=\"\"
-I/pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/xlint/../arch/amd64
-I/pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/xlint/../common
-DNDEBUG
-std=gnu99 -fstack-protector-strong -Wsystem-headers -Wall -Wno-format-y2k
-W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow
-Wunused-parameter
-Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
-Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations
-Wthread-safety -Wno-empty-body -Wno-string-plus-int
-Wno-unused-const-variable
-Qunused-arguments -o xlint xlint.o mem.o --- lint.1.gz --- gzip
-cn /pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/xlint/lint.1 >
lint.1.gz ===> usr.bin/xlint/llib (all) --- llib-lposix.ln --- lint
-cghapbx
-Cposix /pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/llib/
llib-lposix
sh: lint: not found *** [llib-lposix.ln] Error code 127
[...]
Please advice how this can be resolved.
Kind regards,
Oliver
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current

Don Lewis

2018-01-08 07:46:32 UTC

Permalink

Put the following in /usr/local/etc/poudriere.d/src.conf:
LINT=/usr/bin/false

That skips the attempt to build the lint library because of this:
.if ${LINT} == "lint"
_llib= llib
.else
_llib=
.endif

SUBDIR= lint1 lint2 xlint ${_llib}
in /usr/src/usr.bin/xlint/Makefile

We have a bunch of CURRENT boxes running poudriere jails providing packages for
11.1-RELENG. Since a couple of week sfor now, I face this error when I try to
[...]
cc -O2 -pipe
-I/pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/xlint/../lint1
-DPREFIX=\"\"
-I/pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/xlint/../arch/amd64
-I/pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/xlint/../common -DNDEBUG
-std=gnu99 -fstack-protector-strong -Wsystem-headers -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter
-Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
-Wold-style-definition -Wno-pointer-sign -Wmissing-variable-declarations
-Wthread-safety -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable
-Qunused-arguments -o xlint xlint.o mem.o --- lint.1.gz --- gzip
-cn /pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/xlint/lint.1 >
lint.1.gz ===> usr.bin/xlint/llib (all) --- llib-lposix.ln --- lint -cghapbx
-Cposix /pool/poudriere/jails/11amd64/usr/src/usr.bin/xlint/llib/llib-lposix
sh: lint: not found *** [llib-lposix.ln] Error code 127
[...]
Please advice how this can be resolved.
Kind regards,
Oliver
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current

Don Lewis

2018-01-08 07:49:36 UTC

Permalink

There doesn't appear to be a knob to disable building lint for FreeBSD
11.x. Linking or copying /usr/bin/true to /usr/bin/lint works for cross
building 11 on on a 12.0-CURRENT machine, but I was not able to get it
to work when rebuilding a poudriere jail.

Post by Warner Losh
Does building -DWITHOUT_LINT work? Or linking lint to /bin/true
Warner

_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-current

Ian Lepore

2018-01-08 19:49:20 UTC

Permalink

Hi!
If I understand correctly, in the past we decommissioned stuff from
- announce intent
- analyse/remove from use
- disconnect from build
- remove from tree
It seems dropping lint was done a bit hasty ?

It was discovered that it had not been working for about 3 years and
nobody complained, so hasty removal seemed innocuous at the time. I
don't think these subsequent build problems were anticipated, but they
should be fixable.

https://lists.freebsd.org/pipermail/freebsd-arch/2016-February/017658.html

-- Ian

Warner Losh

2018-01-08 19:53:45 UTC

Permalink

On Jan 8, 2018 12:44 PM, "Kurt Jaeger" <***@opsec.eu> wrote:

Hi!

If I understand correctly, in the past we decommissioned stuff from
the base system in a few steps:

- announce intent
- analyse/remove from use
- disconnect from build
- remove from tree

It seems dropping lint was done a bit hasty

We did all that, but this was an unanticipated issue.

I like Ian's idea.

Warner