The port has USE_GCC=yes and SSL option breaks the build on i386 architecture with GCC 11, which is
soon to become the default GCC version.
PR: 264368
Reported by: exp-run (antoine)
Details
Details
Diff Detail
Diff Detail
- Repository
- rP FreeBSD ports repository
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 45783 Build 42671: arc lint + arc unit
Event Timeline
Comment Actions
I was unsure about bumping PORTREVISION or not. I choosed not to do it because:
- with the actual default version of GCC (10) the port fully supports SSL, even on i386;
- @gerald: I guess when the GCC default version update will be committed you will bump PORTREVISION anyway, am I right?
Comment Actions
Yes, and we are changing that default by this patch and packages built thereafter will provide different features (by default). So bumping PORTREVISION appears appropriate.
- @gerald: I guess when the GCC default version update will be committed you will bump PORTREVISION anyway, am I right?
In the past I have been doing it, and it's usually been quite involved and affected thousands of ports. With the update from GCC 9 to GCC 10 which linimon@ did, that bump did not take place and ... nothing happened. So for this time around I am actually wondering whether to skip that step again (though it might make sense to go for it).
Comment Actions
Approved with PORTREVISION bump added. (Technically that bump could be made conditional on i386, but that kind of conditional has proven to be a maintenance issue that's probably not worth the hassle, so I'd do it unconditionally.)