Ticket #18157 (closed defect: fixed)
piklab depends on arts, arts is broken, unbuildable, and unsupported
| Reported by: | dr2chase@… | Owned by: | jwbacon@… |
|---|---|---|---|
| Priority: | High | Milestone: | |
| Component: | ports | Version: | 1.7.0 |
| Keywords: | Cc: | ||
| Port: | piklab |
Description
See subject. Arts does not build, despite an entire afternoon spent whacking on it until the C++ weeds became too deep. The pervasive bugs (syntax errors in modern C++, most of them) suggest that arts has not been used for a long time. Upon further investigation, I discover that the arts maintainer is no longer interested in maintaining it. (http://www.arts-project.org/gen/newsarchive/news_2000.html)
If piklab depends on Arts, then it, too, is a waste of space.
Attachments
Change History
comment:1 follow-up: ↓ 2 Changed 4 years ago by blb@…
- Owner changed from macports-tickets@… to jwbacon@…
- Port set to piklab
comment:2 in reply to: ↑ 1 Changed 4 years ago by jwbacon@…
Replying to blb@…:
Looks like possibly adding --without-arts to configure for piklab should definitely avoid any dependency on arts.
Please see the attached diff.
Jason
comment:3 Changed 4 years ago by dr2chase@…
Tried the diffs, built it, installed it, it looks at least minimally functional (and I checked that I was running 0.15.4).
The debugging info while running is a little much, but that beats not building at all.
I'll test programming an actual chip when a necessary cable arrives, will report back then, but this is a definite improvement even without that testing.
Looks like possibly adding --without-arts to configure for piklab should definitely avoid any dependency on arts.