View | Details | Raw Unified | Return to bug 208391
Collapse All | Expand All

(-)Makefile (+2 lines)
Lines 3-8 Link Here
3
3
4
PORTNAME=	mc
4
PORTNAME=	mc
5
PORTVERSION=	4.8.24
5
PORTVERSION=	4.8.24
6
PORTREVISION=	1
6
CATEGORIES=	misc shells
7
CATEGORIES=	misc shells
7
MASTER_SITES=	http://ftp.midnight-commander.org/ \
8
MASTER_SITES=	http://ftp.midnight-commander.org/ \
8
		https://ftp.osuosl.org/pub/midnightcommander/
9
		https://ftp.osuosl.org/pub/midnightcommander/
Lines 56-61 Link Here
56
			smb-codepagedir=${LOCALBASE}/etc/codepages
57
			smb-codepagedir=${LOCALBASE}/etc/codepages
57
58
58
SUBSHELL_CONFIGURE_WITH=subshell
59
SUBSHELL_CONFIGURE_WITH=subshell
60
SUBSHELL_SUB_FILES=	pkg-message
59
61
60
X11_CONFIGURE_ENABLE=	x
62
X11_CONFIGURE_ENABLE=	x
61
X11_USES=		xorg
63
X11_USES=		xorg
(-)files/pkg-message.in (+21 lines)
Line 0 Link Here
1
[
2
{ type: install
3
   message: <<EOM
4
Midnight Commander does not recognize FreeBSD sh(1) as a supported concurrent
5
shell.  It means is that if mc(1) is started with the SHELL environment
6
variable set to "/bin/sh" (e.g., because it is a login shell) then mc(1) is
7
going to fail like this:
8
9
  $ env SHELL=/bin/sh mc
10
  common.c: unimplemented subshell type 1
11
  read (subshell_pty...): No error: 0 (0)
12
13
A workaround here is to pass the -u flag (--nosubshell) when starting mc(1):
14
15
  $ env SHELL=/bin/sh mc -u
16
17
See the following Bugzilla PR for more details:
18
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208391
19
EOM
20
}
21
]

Return to bug 208391