Opened 4 years ago
Last modified 5 months ago
#62735 assigned defect
optool @ 0.1_0+universal.darwin_15.i386-x86_64: synthesized property ('rule' | 'position') naming problems
Reported by: | thetrial (alabay) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.4 |
Keywords: | legacy-os, elcapitan | Cc: | |
Port: | optool |
Description
optool seems to be installed as dpependency or part, I did not request it. When build: error.
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_optool/optool/work/optool-0.1/optool/FSArgumentParser/CoreParse/CoreParse/Parsers/CPShiftReduceParsers/CPItem.m:20:13: error: synthesized property 'rule' must either be named the same as a compatible instance variable or must explicitly name an instance variable :info:build @synthesize rule; :info:build ^ :info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_sysutils_optool/optool/work/optool-0.1/optool/FSArgumentParser/CoreParse/CoreParse/Parsers/CPShiftReduceParsers/CPItem.m:21:13: error: synthesized property 'position' must either be named the same as a compatible instance variable or must explicitly name an instance variable :info:build @synthesize position; :info:build ^ :info:build 2 errors generated.
I think these might be the problems, but I’m not sure. So I’ll attach the main.log.
Attachments (1)
Change History (5)
Changed 4 years ago by thetrial (alabay)
comment:1 Changed 4 years ago by TallTed (Ted Thibodeau Jr)
comment:2 Changed 4 years ago by TallTed (Ted Thibodeau Jr)
Dependency appears to have been removed, as legacy-support
upgrade installed today without calling for optool
upgrade.
Bug appears to be resolved.
comment:3 Changed 4 years ago by thetrial (alabay)
The dependency seems to be dissolved, yes.
I tried to install optool to check what happens, after having updated legacy-support. First it stated:
Error: Requested variants "" do not match those the build was started with: "+universal". Error: Please use the same variants again, or run 'port clean optool' first to remove the existing partially completed build.
After running clean and rerequesting, it worked. So this is interesting. What was the mistake? Mentioned optool is old, the version is untouched since five years. So is there still the possibility of an error with +universal? Or is everything solved?
comment:4 Changed 5 months ago by raimue (Rainer Müller)
Owner: | raimue deleted |
---|
Dropping maintainership of port.
Same issue. Confirmed
optool
is being installed as dependency oflegacy-support
.