Summary: | emulators/i386-wine{-devel}: broken on CURRENT | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Lorenzo Salvadore <salvadore> |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Closed Works As Intended | ||
Severity: | Affects Only Me | CC: | iwtcex |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any | ||
Bug Depends on: | 243947 | ||
Bug Blocks: |
Description
Lorenzo Salvadore
2020-02-07 13:11:38 UTC
That's curious. Can you run 32-bit binaries at all? (In reply to Alex S from comment #1) I guess not. I tried to compile a 32-bits application to test, but I was not able too. See my new comment on bug #243947. If you want to suggest me some 32-bits application to test, I can try, but please suggest it in bug #233947: let's keep this one wine-specific. (In reply to Lorenzo Salvadore from comment #2) I meant bug #243947 of course, not #233947. There is nothing Wine-specific there as far I am aware: i386-wine(-devel)/Makefile.inc doesn't explicitly call ldd32. It's better to close this issue altogether, it only contributes to confusion. (In reply to Alex S from comment #4) What's specific to wine is that wine is broken on CURRENT. If a wine user wants to report that wine is broken on CURRENT, s/he might be tempted to open a PR about wine, although, as you observed, the problem is more general. The role of this PR is to point to the general PR, in a similar manner as what is usually done with complex exp-runs. Other ports broken for the same reason should, in my opinion, have similar PRs that point to the general PR. Moreover, it is indeed likely that the general problem will be solved without modifications to the wine ports and that those ports will then work again untouched, but the opposite is not impossible: it is not impossible that wine ports will need to change to integrate with the general solution. That said, if bugzilla triagers or committers agree with you and want to close this PR, I will not object. I am only trying to adopt the best strategy to help people find existing bugs and understand the relations between them. Everything works fine: the problem was my fault. For more details, please see bug #243947. |