build failed for me

25 views
Skip to first unread message

Raoul Duke

unread,
Aug 7, 2014, 12:51:00 AM8/7/14
to ats-lang-users
* i cloned git repo.
* had libgmp from having tried to install from tar gz file.
* futzed with getting automake installed; had to run make and then
configure and then make again, weird, unclear.
* it built for a while but then eventually bombed out:

Linux superlap2 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:43:42
UTC 2014 i686 i686 i686 GNU/Linux

make[1]: Leaving directory `/home/superman/Dev/ats2-lang/src/CBOOT'
cp -f src/CBOOT/patsopt bin/patsopt
make -C utils/atscc patscc
make[1]: Entering directory `/home/superman/Dev/ats2-lang/utils/atscc'
"/home/superman/Dev/ats2-lang"/bin/patsopt --output patscc_dats.c
--dynamic patscc.dats
Hello from ATS2(ATS/Postiats)!
The 1st translation (fixity) of [patscc.dats] is successfully completed!
The 2nd translation (binding) of [patscc.dats] is successfully completed!
The 3rd translation (type-checking) of [patscc.dats] is successfully completed!
The 4th translation (type/proof-erasing) of [patscc.dats] is
successfully completed!
"/home/superman/Dev/ats2-lang"/bin/patsopt --output atscc_main_dats.c
--dynamic atscc_main.dats
Hello from ATS2(ATS/Postiats)!
The 1st translation (fixity) of [atscc_main.dats] is successfully completed!
The 2nd translation (binding) of [atscc_main.dats] is successfully completed!
The 3rd translation (type-checking) of [atscc_main.dats] is
successfully completed!
The 4th translation (type/proof-erasing) of [atscc_main.dats] is
successfully completed!
"/home/superman/Dev/ats2-lang"/bin/patsopt --output atscc_print_dats.c
--dynamic atscc_print.dats
Hello from ATS2(ATS/Postiats)!
The 1st translation (fixity) of [atscc_print.dats] is successfully completed!
The 2nd translation (binding) of [atscc_print.dats] is successfully completed!
The 3rd translation (type-checking) of [atscc_print.dats] is
successfully completed!
The 4th translation (type/proof-erasing) of [atscc_print.dats] is
successfully completed!
Segmentation fault (core dumped)
make[1]: *** [atscc_print_dats.c] Error 139
make[1]: Leaving directory `/home/superman/Dev/ats2-lang/utils/atscc'
make: *** [utl_atscc] Error 2

gmhwxi

unread,
Aug 7, 2014, 12:59:43 AM8/7/14
to ats-lan...@googlegroups.com
Maybe it is GC related? Try to build without GC
(or with Boehm-GC):

http://www.ats-lang.org/DOWNLOAD/#ATS_packages

Raoul Duke

unread,
Aug 7, 2014, 1:11:02 AM8/7/14
to ats-lang-users
whatever it is, it is not clear nor easy to determine, at least with
the github repo clone. i'm just going to not bother trying on linux
any more; it worked on a mac via brew, i'm going to just leave it at
that. more is the pity. certainly doesn't give me warm fuzzies. other
people's mileage my vary of course.
> --
> You received this message because you are subscribed to the Google Groups
> "ats-lang-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ats-lang-user...@googlegroups.com.
> To post to this group, send email to ats-lan...@googlegroups.com.
> Visit this group at http://groups.google.com/group/ats-lang-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ats-lang-users/9c88cc48-1989-42d5-a9f1-041381189f5f%40googlegroups.com.

Yannick Duchêne

unread,
Aug 7, 2014, 2:35:53 AM8/7/14
to ats-lan...@googlegroups.com


Le jeudi 7 août 2014 06:51:00 UTC+2, Raoul Duke a écrit :

Segmentation fault (core dumped)
make[1]: *** [atscc_print_dats.c] Error 139
make[1]: Leaving directory `/home/superman/Dev/ats2-lang/utils/atscc'
make: *** [utl_atscc] Error 2

I had the same, except it was with using a SourceForge tarball (or Github tarball, can't remember). It was discussed on another news‑group. Here is what I did, and it solved the case, to be executed next after `./configure`:

(export CFLAGS="$CFLAGS --fno-aggressive-loop-optimization" && make GCFLAG=-D_ATS_NGC all);


Hongwei Xi said the same for me as for you: may be garbage‑collector related.

I don't know for you, for me, without compiling ATS with these options, there were random errors.
Reply all
Reply to author
Forward
0 new messages