Help testing release candidate / mc-4.8.23-rc1
Henning
xaoxx at t-online.de
Mon Jun 17 14:42:47 UTC 2019
On 16/06/2019 20:56, Yury V. Zaytsev wrote:
> TLDR; I would appreciate if you could please test the following tarball
> on your systems and report any blocker regressions as compared to the
> previous 4.8.22 release:
Build and run ok on CYGWIN_NT-6.3 3.1.0s(0.338/5/3) 2019-06-05 i686.
Warnings (some may be cygwin related):
*** Warning: Trying to link with static lib archive /usr/lib/libiconv.dll.a.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because the file extensions .a of this argument makes me believe
*** that it is just a static archive that I should not use here.
----------------
more like the following:
warning: "__linux__" is not defined, evaluates to 0 [-Wundef]
#if __linux__ && (__GLIBC__ || __UCLIBC__)
----------------
mountlist.c: In function 'me_remote':
mountlist.c:245:9: warning: switch missing default case [-Wswitch-default]
switch (GetDriveType (drive))
^~~~~~
----------------
sfs.c: In function 'sfs_open':
sfs.c:281:10: warning: declaration of 'sfs_info' shadows a global
declaration [-Wshadow]
int *sfs_info;
^~~~~~~~
sfs.c:118:3: note: shadowed declaration is here
} sfs_info[MAXFS];
^~~~~~~~
-----------------
./.libs/lt-mc.c: In function 'lt_debugprintf':
./.libs/lt-mc.c:574:7: warning: function 'lt_debugprintf' might be a
candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
(void) vfprintf (stderr, fmt, args);
^
./.libs/lt-mc.c: In function 'lt_error_core':
./.libs/lt-mc.c:585:3: warning: function 'lt_error_core' might be a
candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
vfprintf (stderr, message, ap);
^~~~~~~~
-----------------
And finally, I'm not knowledgeable enough to know about blocker
regressions. If I can do something to provoke things, please tell
me.
Otherwise I'm looking forward to the final release. (I'm a long-time
[1998] and hardcore user of mc [linux]. So I'd like to thank all of you
a lot
for your work.)
Henning
More information about the mc-devel
mailing list