Changes between Initial Version and Version 1 of Ticket #67475, comment 2
- Timestamp:
- May 22, 2023, 2:12:32 PM (12 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #67475, comment 2
initial v1 1 1 This is happening because you are using the universal variant, thus requesting both a 32-bit and 64-bit build. The 32-bit build is the one producing this complaint. The suggestion to use `-m64`, to cause a 64-bit build to be performed, is thus inapplicable. If you wanted a 64-bit-only build you wouldn't use the universal variant. 2 2 3 This complaint is part of gnulib, which diffutils uses. Other ports that use gnulib also need to work around this complaint for 32-bit builds. gnulib has already twice changed the mechanism by which the complaint can be disabled. When diffutils updates to a newer gnulib, it will need to have the complaint suppression method updated as well. See #55643 for the initial method we used in the coreutils port. See #65457 for how coreutils had to be adapted after gnulib changed the first time. (Although the error message you showed is different, this fix looks like it will be the one to use for the version of gnulib diffutils currently uses.) See #67277 for how it needed to be changed after the second gnulib change in coreutils.3 This complaint is part of gnulib, which diffutils uses. Other ports that use gnulib also need to work around this complaint for 32-bit builds. gnulib has already twice changed the mechanism by which the complaint can be disabled. When diffutils updates to a newer gnulib, it will need to have the complaint suppression method updated as well. See #55643 for the initial method we used in the coreutils port. See #65457 for how coreutils had to be adapted after gnulib changed the first time. (Although the error message you showed is different, this fix looks like it will be the one to use for the version of gnulib diffutils currently uses.) See #67277 for how coreutils needed to be changed after the second gnulib change.