Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variable redeclared in filevercmp_test5 #4358

Closed
mc-butler opened this issue Mar 27, 2022 · 8 comments
Closed

Variable redeclared in filevercmp_test5 #4358

mc-butler opened this issue Mar 27, 2022 · 8 comments
Assignees
Labels
area: tests Testing Midnight Commander prio: low Minor problem or easily worked around ver: 4.8.28 Reproducible in version 4.8.28
Milestone

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/4358
Reporter ats (ats-mc@….org)

In mc-4.8.28, the test filevercmp_test5 in tests/lib/strutil/filevercmp.c declares:

size_t _i;

However, the name _i is also used inside check's START_TEST macro, so GCC 11.2 complains:

filevercmp.c: In function ‘filevercmp_test5_fn’:
filevercmp.c:356:12: error: ‘_i’ redeclared as different kind of symbol

I've fixed this in the attached patch by renaming _i and _j, but you may prefer a different new name...

Note

Original attachments:

  • checki.diff (raw) by ats (ats-mc@….org) on Mar 27, 2022 at 14:44 UTC
@mc-butler
Copy link
Author

Changed by ats (ats-mc@….org) on Mar 27, 2022 at 14:44 UTC

Patch: rename _i/_j to ii/jj

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Mar 27, 2022 at 16:17 UTC (comment 1)

  • Component changed from mc-core to tests

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Mar 27, 2022 at 16:49 UTC (comment 2)

  • Milestone changed from Future Releases to 4.8.29
  • Status changed from new to accepted
  • Blocked by set to #4357
  • Owner set to andrew_b

Thanks!
Applied in 4357_cleanup branch.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Mar 28, 2022 at 3:28 UTC (comment 3)

Ticket #4359 has been marked as a duplicate of this ticket.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Apr 5, 2022 at 14:23 UTC (comment 4)

Ticket #4366 has been marked as a duplicate of this ticket.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jun 5, 2022 at 16:51 UTC (comment 5)

  • Blocked by #4357 deleted

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jun 5, 2022 at 16:51 UTC (comment 6)

  • Resolution set to fixed
  • Status changed from accepted to testing

[7435010]

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jun 5, 2022 at 16:56 UTC (comment 7)

  • Status changed from testing to closed

@mc-butler mc-butler marked this as a duplicate of #4359 Feb 28, 2025
@mc-butler mc-butler marked this as a duplicate of #4366 Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: tests Testing Midnight Commander prio: low Minor problem or easily worked around ver: 4.8.28 Reproducible in version 4.8.28
Development

No branches or pull requests

2 participants