Opened 15 years ago

Closed 4 years ago

Last modified 4 years ago

#20909 closed defect (fixed)

ncid-0.74 sip2ncid broken on 64-bit platforms

Reported by: meissnem@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 1.8.0
Keywords: haspatch LP64 Cc: david@…
Port: ncid

Description

It seems that sip2ncid from the ncid port is not 64-bit clean. This message appears in the log file repeatedly when using x86_64:

No SIP packets at port 10000 in 60 seconds
And it just doesn't work :)  Switching to 32-bit fixes the problem.

Until I can work out a proper patch and submit it upstream, I propose that the port just uses 32-bit archs instead.

Attachments (1)

ncid.diff (521 bytes) - added by meissnem@… 15 years ago.

Download all attachments as: .zip

Change History (10)

Changed 15 years ago by meissnem@…

Attachment: ncid.diff added

comment:1 Changed 15 years ago by jmroot (Joshua Root)

Cc: david@… added
Owner: changed from macports-tickets@… to ryandesign@…

comment:2 Changed 14 years ago by jmroot (Joshua Root)

Keywords: LP64 added; ncid x86_64 64-bit removed

comment:3 Changed 13 years ago by jmroot (Joshua Root)

Keywords: haspatch added

comment:4 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Is this still a problem with version 0.82.1? If so, have you reported it to the developer of ncid?

comment:5 Changed 5 years ago by kencu (Ken)

this ticket is crazy ancient. I presume this must be fixed by now, otherwise this software would be useless. I builds fine on mojave, but I don't know how to test whether the sip2ncid binary still errors out.

comment:6 Changed 4 years ago by kencu (Ken)

Resolution: fixed
Status: newclosed

fixed, presumably with an update along the way <http://packages.macports.org/ncid/ncid-0.83_0.darwin_10.x86_64.tbz2>

comment:7 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

The existence of an archive doesn't prove that the problem was fixed. It wasn't a build problem; it was a runtime problem.

comment:8 Changed 4 years ago by kencu (Ken)

Of course, however:

I presume this must be fixed by now, otherwise this software would be useless. It builds fine on mojave, but I don't know how to test whether the sip2ncid binary still errors out.

After 11 years, if it is still broken, and anyone cares any longer, someone can reopen the ticket with some new information. Decades are just too long to leave tickets open growing cobwebs. It's not reasonable to have tickets nobody will ever do anything about...

Feel free to reopen it if you like; I was on a cleanup mission, but I am not wedded to having this closed.

comment:9 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

No I'm fine with having this closed since the reporter did not reply to my question, and I'm glad you're cleaning up, but please be careful that you're not taking the existence of a binary archive as indication that a problem was fixed since not all tickets are about build failures.

Note: See TracTickets for help on using tickets.