Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Aug 2013 20:49:20 +0200 (CEST)
From:      Slaven Rezic <slaven@rezic.de>
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   bin/181436: /usr/bin/file cannot detect BSD makefiles
Message-ID:  <201308201849.r7KInKfb074304@cvrsnica.herceg.de>
Resent-Message-ID: <201308201850.r7KIo0AO009236@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         181436
>Category:       bin
>Synopsis:       /usr/bin/file cannot detect BSD makefiles
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 20 18:50:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Slaven Rezic
>Release:        FreeBSD 9.0-RELEASE amd64
>Organization:
www.rezic.de
>Environment:
System: FreeBSD cvrsnica.herceg.de 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64


	The behavior is visible with FreeBSD 9.0 (file-5.03) and
	FreeBSD 10.0 (file-5.11).

>Description:
	Most BSD makefiles are not recognized by /usr/bin/file as
	such. Worse, if less is configured to use lesspipe from the
	ports (misc/lesspipe), then many BSD makefiles are recognized
	as troff files, causing unreadable input.

>How-To-Repeat:
	For example:

	    cd /usr/share/mk
	    /usr/bin/file * | grep -i troff | wc -l

	Or configure less to use lesspipe as per lesspipe's manpage
	(see FILTER ACTIVATION section) and try to use less on any of
	misrecognized BSD makefiles.

>Fix:

	Maybe adding keywords as ".if", ".include", ".else" etc. as
	BSD makefile keywords before the troff section could help.


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201308201849.r7KInKfb074304>