Opened 13 years ago

Closed 3 years ago

#31312 closed defect (duplicate)

yap fails to build under lion

Reported by: jody@… Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: gjasny@…
Port: yap

Description

Error during build on lion 10.7.1. Attached main.log

Tail of main.log:

:info:build /Developer/usr/bin/llvm-gcc-4.2 -fstrict-aliasing -freorder-blocks -fsched-interblock -Wall -Wstrict-aliasing=2 -c -pipe -O2 -arch x86_64 -DCUT_C=1 -fno-common  -DCOROUTINING=1 -DRATIONAL_TREES=1 -DDEPTH_LIMIT=1 -DHAVE_CONFIG_H -D_YAP_NOT_INSTALLED_=1 -I/opt/local/include -I/opt/local/include -I/opt/local/include  -I. -I./H -I./OPTYap -I./BEAM -I./MYDDAS ./BEAM/eam_am.c -o eam_am.o
:info:build /Developer/usr/bin/llvm-gcc-4.2 -fstrict-aliasing -freorder-blocks -fsched-interblock -Wall -Wstrict-aliasing=2 -dynamiclib -Wl,-install_name,/opt/local/lib/libYap.dylib -o libYap.dylib agc.o absmi.o adtdefs.o alloc.o amasm.o analyst.o arrays.o arith0.o arith1.o arith2.o attvar.o bignum.o bb.o cdmgr.o cmppreds.o compiler.o computils.o corout.o cut_c.o dbase.o dlmalloc.o errors.o eval.o exec.o globals.o gmp_support.o gprof.o grow.o heapgc.o index.o init.o  inlines.o iopreds.o depth_bound.o mavar.o myddas_mysql.o myddas_odbc.o myddas_shared.o myddas_initialization.o myddas_util.o myddas_statistics.o myddas_top_level.o myddas_wkb2prolog.o modules.o other.o parser.o readutil.o save.o scanner.o sort.o stdpreds.o sysbits.o threads.o tracer.o udi.o rtree.o rtree_udi.o unify.o userpreds.o utilpreds.o write.o yap2swi.o ypsocks.o ypstdio.o  load_foreign.o load_dl.o load_dld.o load_dyld.o load_none.o load_aout.o load_aix.o load_dll.o load_shl.o c_interface.o clause_list.o opt.memory.o opt.init.o opt.preds.o or.engine.o or.cowengine.o or.sbaengine.o or.threadengine.o or.scheduler.o or.cut.o tab.tries.o tab.completion.o eamamasm.o eam_showcode.o eamindex.o eam_am.o  -lgmp -lreadline -lncurses -ltermcap -lstdc++ -lm  -framework JavaVM -L/opt/local/lib -arch x86_64 -L/opt/local/lib -L/opt/local/lib
:info:build /Developer/usr/bin/llvm-gcc-4.2  -L/opt/local/lib -arch x86_64 -L/opt/local/lib -L/opt/local/lib -o yap yap.o libYap.dylib -lgmp -lreadline -lncurses -ltermcap -lstdc++ -lm  -framework JavaVM 
:info:build rm -f startup.yss
:info:build echo "bootstrap('./pl/init.yap'). module(user). save_program('startup.yss')." |  DYLD_LIBRARY_PATH=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_yap/yap/work/yap-6 ./yap -b ./pl/boot.yap
:info:build %
:info:build %
:info:build % YAP OOOPS: likely bug in YAP, segmentation violation.
:info:build %
:info:build %
:info:build 
:info:build    Exiting ....
:info:build make: *** [startup.yss] Error 1
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_yap/yap/work/yap-6'
:info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_yap/yap/work/yap-6" && /usr/bin/make -j8 -w all " returned error 2
:error:build Target org.macports.build returned: shell command failed (see log for details)
:debug:build Backtrace: shell command failed (see log for details)
    while executing
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"
:info:build Warning: the following items did not execute (for yap): org.macports.activate org.macports.build org.macports.destroot org.macports.install
:notice:build Log for yap is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_yap/yap/main.log

Attachments (4)

main.log (227.5 KB) - added by jody@… 13 years ago.
main.log for yap install
Portfile-yap-31312.diff (828 bytes) - added by gjasny@… 11 years ago.
Bump to latest stable and fix building with newer Xcode
fix-clause-creator.diff (1.6 KB) - added by gjasny@… 11 years ago.
nil-is-keyword.diff (556 bytes) - added by gjasny@… 11 years ago.

Download all attachments as: .zip

Change History (10)

Changed 13 years ago by jody@…

Attachment: main.log added

main.log for yap install

comment:1 Changed 13 years ago by mf2k (Frank Schima)

Owner: changed from macports-tickets@… to pmoura@…

comment:2 Changed 13 years ago by pmoura (Paulo Moura)

The problem is fixed on the current git version of YAP 6.3 and, I think, on the current git version of YAP 6.2. Hopefully, YAP 6.2.2 stable will be released soon.

Changed 11 years ago by gjasny@…

Attachment: Portfile-yap-31312.diff added

Bump to latest stable and fix building with newer Xcode

Changed 11 years ago by gjasny@…

Attachment: fix-clause-creator.diff added

Changed 11 years ago by gjasny@…

Attachment: nil-is-keyword.diff added

comment:3 Changed 11 years ago by gjasny@…

Cc: gjasny@… added

Cc Me!

comment:4 Changed 5 years ago by kencu (Ken)

So this port is quite broken, at least on Lion, and I suspect everywhere, although I didn't try any other systems.

The software has moved to <https://github.com/vscosta/yap-6.3/> and the homepage is <http://www.dcc.fc.up.pt/~vsc/yap/> now.

I tried making a github port, using cmake, and the cxx11 1.1 PG, and I got through for a while. It builds a version of itself along the way, maybe for testing, maybe for bootstrapping, around 85%. The build fails there, although you can get farther by using install_name_tool on the yap binary and showing it where it's support lib is (same directory). Then it fails later on with

no member named unordered_map in namespace std.

At that point I gave up. It's still listed as a preview release on github. Not sure -- if it doesn't work on any other systems either, we should probably just delete it as non-functional.

comment:5 Changed 5 years ago by mf2k (Frank Schima)

Owner: pmoura deleted
Status: newassigned

See #58428.

comment:6 Changed 3 years ago by kencu (Ken)

Resolution: duplicate
Status: assignedclosed

yap fails to build on everything.

we'll call this a dup of #55370 where there is at least some interest in trying to give it CPR...

Note: See TracTickets for help on using tickets.