Opened 6 weeks ago
Closed 6 weeks ago
#71012 closed defect (fixed)
nbsmtp @1.00: error: incompatible integer to pointer conversion assigning to 'char *' from 'char' [-Wint-conversion]
Reported by: | Buadhai | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.10.2 |
Keywords: | Cc: | ||
Port: | nbsmtp |
Description
No idea what goes here.
Attachments (1)
Change History (5)
Changed 6 weeks ago by Buadhai
Attachment: | main.log.gz added |
---|
comment:1 Changed 6 weeks ago by ryandesign (Ryan Carsten Schmidt)
Port: | nbsmtp added |
---|---|
Summary: | nbsmtp failed to build → nbsmtp @1.00: error: incompatible integer to pointer conversion assigning to 'char *' from 'char' [-Wint-conversion] |
comment:2 Changed 6 weeks ago by ryandesign (Ryan Carsten Schmidt)
The project's web server no longer exists. Here is the last archived copy of the project's homepage from 2007:
https://web.archive.org/web/20071013050201/http://nbsmtp.ferdyx.org/
so unless the project has moved somewhere else that we don't know about, I don't expect any help from its developers.
Repology doesn't know of a new home for the project either:
https://repology.org/project/nbsmtp/information
We could look at what other distributions are doing. Maybe they already have a patch for this. And in fact it looks like this might be it:
https://cgit.freebsd.org/ports/commit/?id=584050b16c033f5e0ffa14a03103f6fde716827f
Let me test it…
comment:3 Changed 6 weeks ago by ryandesign (Ryan Carsten Schmidt)
According to https://ports.macports.org/port/nbsmtp/builds/ we have not built this port successfully on any OS version in the five years that we've been keeping track of build status, so there will be more to fix than just this.
comment:4 Changed 6 weeks ago by ryandesign (Ryan Carsten Schmidt)
Owner: | set to ryandesign |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Thanks for the report. The log tell us the problem is:
So we either need to update the port to a fixed version from its developers or, if none exists, we'll have to develop a fix for this ourselves.