Date: Thu, 22 Apr 2021 02:35:38 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 255315] misc/vifm fix macro 'BSD' is not defined on 13.0-RELEASE Message-ID: <bug-255315-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255315 Bug ID: 255315 Summary: misc/vifm fix macro 'BSD' is not defined on 13.0-RELEASE Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: ark.misc9090@gmail.com CC: mp39590@gmail.com CC: mp39590@gmail.com Flags: maintainer-feedback?(mp39590@gmail.com) Created attachment 224346 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D224346&action= =3Dedit patch Macro 'BSD' is required for correct package logic. In particular function 'is_dir_fast' defined in src/utils/fs.c uses this macro to select method for checking if 'path' variable is a directory. If macro is not defined then pa= ths to executables are detected as directories. For example, executable '/usr/local/bin/feh' is reported by 'is_dir' function as directory. This incorrect reports lead to various bugs: 1. Files with extensions can't be opened by registered programs ( defined by filextype ). Default editor (Vim) used instead. 2. During copy directory there are error messages like 'Target path specifi= es existing directory' 3. Files with 'sticky bit' are displayed as directories Working solution is to add 'BSD' macro to compilation flags in package Makefile: CFLAGS+=3D -fcommon -DBSD Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255315-7788>