Description of problem:
LTP tests can`t be run if it been started at MC subshell, but if i
start at it without MC all tests run correctly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rebuild and install mc from FC1 package.
2. make and install LTP test suite
3. run default tests from LTP.
test can`t been exited.
Kernel trace is available at bug 123408.
mc upstream released another release candidate for mc (4.6.1-pre3) which I want
to include to RHEL3. The FC1 version of mc is very obsolete and many of bugs
were fixed in the mentioned prerelease. Some users replied to me that they're
happy with the version of mc I released for FC3 update in december and it works
fine for them.
mc subshell fixes were one of the main interests in recent development.
or the latest devel:
Note that FC1 is a legacy project now, which is not officially supported now.
can`t build under fully updated RH EL3(AS)
1) first it need gettext-devel. but this package can`t be found at RHN.
2) after this requestion comented - it stop configure with messages.
Upgrade gettext to at least 0.11.5 or downgrade to 0.10.40
# rpm -qa | grep gettext
but i can`t find these at beta channels also.
And I think this not a MC problem. If i right program frezed at signal delivery.
It posible trigered with MC but it not are MC bug.
To fix the compilation problem under RHEL3, please delete lines 56-59 in
autogen.sh. gettext-devel package isn't present in RHEL3 and you can safely drop
this requirement because it was done because of autopoint which is moved to
gettext-devel in development branch.
Right, it also doesn't look like a mc bug to me.
Who you set to this bug resolution - 'Not a bug', if this bug are stil and not
fixed? At start i set 'kernel' category and if its kernel bug please reasign to
person who can find and fix this bug.
I set the resolution to NOTABUG because an unsupported package (FC1 mc
on RHEL3) is used, therefore it's not a bug in RHEL3 distribution and
mc. On the second thought it's better to mark this bug as duplicate of
*** This bug has been marked as a duplicate of 123408 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.