Summary: | lang/gprolog updated 1.4.5 | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Detlef Sax <sax> |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Closed DUPLICATE | ||
Severity: | Affects Some People | CC: | mandree |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any | ||
Bug Depends on: | 231393 | ||
Bug Blocks: |
Description
Detlef Sax
2019-03-07 18:32:42 UTC
Detlef, can you shed any light on the issues brought up in Bug #231393? *** This bug has been marked as a duplicate of bug 231393 *** (In reply to Matthias Andree from comment #1) At ftp://ftp.gnu.org/gnu/gprolog/ you can see that 1.4.5 there is from February 2019. The comment you refer to as duplicate is dated from 2018. So there is likely a never version with same reviosion available. What I simply did is to copy ports/lan gprolog to my home, changed the Makefile to 1.4.5 and commented out the BROKEN and DEPRECEATED flags. I created a new distinfo file: SHA256 (gprolog-1.4.5.tar.gz) = bfdcf00e051e0628b4f9af9d6638d4fde6ad793401e58a5619d1cc6105618c7c SIZE = 3587361 Then I did a "su -" make install. No errors, everything fine. Then I used the gplc to compile a prolog file. No errors and works now for 2 days. That's all. Detlef |