Opened 2 weeks ago

Last modified 13 days 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: raimue (Rainer Müller)
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)

main.log (349.7 KB) - added by thetrial (alabay) 2 weeks ago.

Download all attachments as: .zip

Change History (4)

Changed 2 weeks ago by thetrial (alabay)

Attachment: main.log added

comment:1 Changed 2 weeks ago by TallTed (Ted Thibodeau Jr)

Same issue. Confirmed optool is being installed as dependency of legacy-support.

Last edited 13 days ago by TallTed (Ted Thibodeau Jr) (previous) (diff)

comment:2 Changed 13 days 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 13 days 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?

Note: See TracTickets for help on using tickets.