Maude refuses to compile with clang : In file included from ./stringTerm.hh:28: ./../src/Utility/ropeStuff.hh:37:14: fatal error: 'ext/rope' file not found #include <ext/rope> How-To-Repeat: cd /usr/ports/lang/maude && make
Maintainer of lang/maude, Please note that PR ports/189390 has just been submitted. If it contains a patch for an upgrade, an enhancement or a bug fix you agree on, reply to this email stating that you approve the patch and a committer will take care of it. The full text of the PR can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/189390 -- Edwin Groothuis via the GNATS Auto Assign Tool edwin@FreeBSD.org
State Changed From-To: open->feedback Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
CC'ing maintainer again.
(In reply to cduret from comment #0) > Maude refuses to compile with clang : > In file included from ./stringTerm.hh:28: > ./../src/Utility/ropeStuff.hh:37:14: fatal error: 'ext/rope' file not found > #include <ext/rope> > How-To-Repeat: cd /usr/ports/lang/maude && make 'ext/rope' is part of gcc's libstdc++, but not part of clang's libc++. Unfortunately I don't have the resources to come up with a solution (e.g. porting ext/rope to clang), so I can only suggest a workaround: Add USE_GCC=any in lang/maude/Makefile. When reporting what happens if you do so, please also mention the versions of FreeBSD and the compiler(s) that you've used. Thanks! Johannes ps If you haven't noticed already, PR 191049 also deals with lang/maude. pps Sorry for my delayed response (mostly due to lack of connectivity during the last weeks.)
I think the maintainer has said his last word on the topic, 5 weeks ago, with no response. closing...
No it is still not working with USE_GCC=any in Makefile .... Making all in Mixfix --- surface.yy --- cat ./top.yy ./modules.yy ./commands.yy ./bottom.yy > surface.yy --- surface.cc --- --- surface.h --- --- surface.cc --- bison -dv surface.yy -o surface.c --- surface.h --- bison -dv surface.yy -o surface.c surface.yy:573.25: warning: a ';' might be needed at the end of action code surface.yy:573.25: future versions of Bison will not add the ';' surface.yy:1097.77: warning: a ';' might be needed at the end of action code surface.yy:1097.77: future versions of Bison will not add the ';' surface.yy:1102.77: warning: a ';' might be needed at the end of action code surface.yy:1102.77: future versions of Bison will not add the ';' --- surface.cc --- surface.yy:573.25: warning: a ';' might be needed at the end of action code surface.yy:573.25: future versions of Bison will not add the ';' surface.yy:1097.77: warning: a ';' might be needed at the end of action code surface.yy:1097.77: future versions of Bison will not add the ';' surface.yy:1102.77: warning: a ';' might be needed at the end of action code surface.yy:1102.77: future versions of Bison will not add the ';' mv surface.c surface.cc --- surface.h --- mv surface.c surface.cc mv: surface.c: No such file or directory *** [surface.h] Error code 1 make[5]: stopped in /usr/ports/lang/maude/work/Maude-2.6/src/Mixfix 1 error make[5]: stopped in /usr/ports/lang/maude/work/Maude-2.6/src/Mixfix *** [all-recursive] Error code 1 make[4]: stopped in /usr/ports/lang/maude/work/Maude-2.6/src 1 error make[4]: stopped in /usr/ports/lang/maude/work/Maude-2.6/src *** [all-recursive] Error code 1 make[3]: stopped in /usr/ports/lang/maude/work/Maude-2.6 1 error make[3]: stopped in /usr/ports/lang/maude/work/Maude-2.6 *** [all] Error code 2 make[2]: stopped in /usr/ports/lang/maude/work/Maude-2.6 1 error make[2]: stopped in /usr/ports/lang/maude/work/Maude-2.6 ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/lang/maude *** Error code 1 Stop. make: stopped in /usr/ports/lang/maude @
But in any case, move over to bug 191049 which deals with lexer issues. They are trying to fix your problem there. USE_GCC=any was a suggestion, I don't see the point of 2 PRs on the same topic so I'm closing this again. *** This bug has been marked as a duplicate of bug 191049 ***