Opened 11 years ago
Closed 5 years ago
#40412 closed defect (wontfix)
swig @2.0.10_0: swig-allegro, swig-mzscheme, swig-pike fail to compile
Reported by: | mojca (Mojca Miklavec) | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | cooljeanius (Eric Gallager) | |
Port: | swig |
Description
With the exception of swig-allegro
which works on 10.6, the three bindings fail to compile on all three OS versions:
Attachments (1)
Change History (13)
comment:1 Changed 11 years ago by mojca (Mojca Miklavec)
Changed 11 years ago by mojca (Mojca Miklavec)
full build log for swig-pike
comment:2 follow-up: 3 Changed 11 years ago by jmroot (Joshua Root)
This is not the swig bindings failing to build, it's their dependencies. The pike failure is #31384 and the mzscheme one is #21853.
As for allegro, it looks like the dependency may be wrong, as the swig docs seem to be saying it supports Allegro CL, which is not what the allegro port installs.
comment:3 Changed 11 years ago by mojca (Mojca Miklavec)
Replying to jmr@…:
As for allegro, it looks like the dependency may be wrong, as the swig docs seem to be saying it supports Allegro CL, which is not what the allegro port installs.
Oh, interesting. I didn't check that, I only needed a particular subport. Given that MacPorts doesn't provide Allegro CL it probably makes most sense to disable allegro altogether. On the other hand it's interesting to see that the compilation proceeds successfully on 10.6 even without Allegro CL being installed.
I also noticed that configure
often reports:
checking for boostlib >= 1.20.0... configure: We could not detect the boost libraries (version 1.20 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in <boost/version.hpp>. See http://randspringer.de/boost for more documentation.
Should the port depend on boost
? (Apparently it's optional, but I wonder if it compiles differently if boost is present.)
I'm also sorry for the wrong report about the other two dependencies. I wasn't careful enough when looking for the cause of the error(s). Thanks for pointing it out.
What should be done with this ticket? Left open until the other two ports are brought back to life?
comment:5 Changed 10 years ago by michaelld (Michael Dickens)
Owner: | changed from kevin@… to michaelld@… |
---|
comment:6 Changed 10 years ago by michaelld (Michael Dickens)
Moving to allegro5 fixes that port's issue. allegro (4) is outdated anyway.
comment:7 Changed 10 years ago by michaelld (Michael Dickens)
I added a patch to ticket #31384 that allows swig-pike to work again (via fixing a broken pike build).
comment:8 Changed 10 years ago by michaelld (Michael Dickens)
In r120784, I switched swig-allegro to use allegro5; this works for me.
comment:9 Changed 10 years ago by michaelld (Michael Dickens)
Meh; looking at the build log for swig-allegro, it's not doing what I thought it was. It's looking for "alisp", which MacPorts does not seem to provide (Allegro Common Lisp). So, I'm going to just remove that subport since it can't work; not with the allegro port nor with allegro5.
comment:12 Changed 5 years ago by michaelld (Michael Dickens)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
allegro:
mzscheme:
pike: