form not working after installation

[aerolivo]

Hello,

I am trying to work with form from macos catalina. After following the instructions of the INSTALL file, when I run the command make check, it ends with the following,

Finished in 3.757018 seconds.
--------------------------------------------------------------------------------
203 tests, 208 assertions, 185 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
8.867% passed
--------------------------------------------------------------------------------
54.03 tests/s, 55.36 assertions/s
FAIL: check-help.sh
FORM 4.2.1 (Aug 28 2019, v4.2.1-4-g0b3ab5d) 64-bits
Program terminating at ./formunit/fu.frm Line 47 --> 
FAIL: benchmark-fu.sh
==========================================================
2 of 2 tests failed
Please report to https://github.com/vermaseren/form/issues
==========================================================
make[2]: *** [check-TESTS] Error 1
make[1]: *** [check-am] Error 2
make: *** [check-recursive] Error 1

It is my first time trying to use form. It's my second try to install it. Do you know what may be causing this?

Thank you in advance.

[tueda]

To make it sure, could you directly run FORM with the benchmark (not inside the testsuite)?

./sources/form check/formunit/fu.frm

Maybe it just fails and doesn't help. But maybe gives additional information, error messages etc...

Configuration with --enable-debug will build a debugging version (sources/vorm) without any compiler optimizations, which also might help.

[vermaseren]

Personally I have not yet upgraded to catalina, because it does not allow 32-bit programs to run, which would disqualify a program that I like to keep. My guess is that, as usual, Apple has moved some things around and do not care what developers of non-Apple products have been doing.

Jos

On 20 Nov 2019, at 18:36, Takahiro Ueda notifications@github.com wrote:

To make it sure, could you directly run FORM with the benchmark (not inside the testsuite)?

./sources/form check/formunit/fu.frm Maybe it just fails and doesn't help. But maybe gives additional information, error messages etc...

Configuration with --enable-debug will build a debugging version (sources/vorm) without any compiler optimizations, which also might help.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/335?email_source=notifications&email_token=ABJPCEWBV5T5N5DVDBQCPCDQUVYSVA5CNFSM4JPULPDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEETDCBY#issuecomment-556151047, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJPCETLZGPVIBYP44ZEUJDQUVYSVANCNFSM4JPULPDA.

[aerolivo]

Hello,

@tueda After running ./sources/form check/formunit/fu.frm, I have this:

FORM 4.2.1 (Aug 28 2019, v4.2.1-4-g0b3ab5d) 64-bits  Run: Thu Nov 21 11:31:15 2019
    #-
Program terminating at check/formunit/fu.frm Line 47 --> 
  0.00 sec out of 0.00 sec

I suspect that the problem is catalina, as noted by @vermaseren . @tueda Do you know if I can make anything to fix this?

Thank you again! Ernst.

[vermaseren]

Looks like a problem with `timer_’. Most likely they have changed things there. These guys can never leave things that work untouched.

Jos

On 21 Nov 2019, at 11:46, Andrés R Olivo notifications@github.com wrote:

Hello,

@tueda https://github.com/tueda After running ./sources/form check/formunit/fu.frm, I have this:

FORM 4.2.1 (Aug 28 2019, v4.2.1-4-g0b3ab5d) 64-bits Run: Thu Nov 21 11:31:15 2019

-

Program terminating at check/formunit/fu.frm Line 47 --> 0.00 sec out of 0.00 sec I suspect that the problem is catalina, as noted by @vermaseren https://github.com/vermaseren . @tueda https://github.com/tueda Do you know if I can make anything to fix this?

Thank you again! Ernst.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/335?email_source=notifications&email_token=ABJPCEUDYLR4UJD5ZFZ4ATTQUZRH7A5CNFSM4JPULPDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEZZGFY#issuecomment-557028119, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJPCEQJP5K5YOUZA3LNVOLQUZRH7ANCNFSM4JPULPDA.

[tueda]

As Jos said, maybe the timer causes the problem. When you run ./configure, do you see the following line in the output?

checking for the POSIX thread clock... yes
checking for library containing clock_gettime... none required

[aerolivo]

Hello,

yes, those lines appear when I run ./configure.

Below checking for library containing clock_gettime... none required, it appears

checking for library containing clock_gettime... (cached) none required

among the other checks.

[tueda]

it appears

checking for library containing clock_gettime... (cached) none required

among the other checks.

This is OK. You can see it also in a successful build log on macOS High Sierra 10.13.3: https://travis-ci.org/vermaseren/form/jobs/577830375#L211-L213.

[jPhy]

I confirm this problem. It seems to be related with the latest OSX (Catalina, 10.15) not with xcode as form runs fine on travisCI who use Mojave (10.14) as the latest osx in their containers, see https://travis-ci.org/mppmu/secdec. The problem further seems to be related to creating expressions: I can run the "Hello World" program without error:

$ ./sources/form hello_world.frm 
FORM 4.2.1 (Nov 21 2018, v4.2.1) 64-bits         Run: Fri Dec  6 11:25:33 2019
    #message Hello World
~~~Hello World
    .end
  0.00 sec out of 0.00 sec

A program just creating an expression, however, errors when run with "form":

$ ./sources/form simple.frm      
FORM 4.2.1 (Nov 21 2018, v4.2.1) 64-bits         Run: Fri Dec  6 11:28:03 2019
    Local ex = 1;
    .end
Program terminating at simple.frm Line 1 --> 
  0.00 sec out of 0.00 sec

but it runs without error using vorm:

$ ./sources/vorm simple.frm 
FORM 4.2.1 (Nov 21 2018, v4.2.1) 64-bits         Run: Fri Dec  6 11:28:27 2019
    Local ex = 1;
    .end

Time =       0.00 sec    Generated terms =          1
              ex         Terms in output =          1
                         Bytes used      =         20
  0.00 sec out of 0.00 sec

[emivilla]

Hello,

This is the first time I use form. Unfortunately, I am trying to work with form from macos catalina. I installed it successfully, but when I run make check I get the same error as @aerolivo . I would like to ask if you find a solution to this issue. Thanks in advance.

[aerolivo]

Hello,

This is the first time I use form. Unfortunately, I am trying to work with form from macos catalina. I installed it successfully, but when I run make check I get the same error as @aerolivo . I would like to ask if you find a solution to this issue. Thanks in advance.

Hello, sorry, I did not keep trying to solve it.

I installed FORM in a linux machine and I am working with it through ssh from the mac. (which is not a solution)

I don't know if someone has installed it successfully on Catalina.

[vermaseren]

One of the problems with developing on MacOS is that a few upgrades ago gdb stopped working. I never managed to get it working again, even though some people seem to have been able to do it. With catalina it is probably even worse. The result is that I can only debug there with lots and lots of print statements. Hence all the debugging is done under Linux. My own Macbook still runs Mojave and by what I read on the internet, I am not much motivated to go to catalina. Form would not be the only program that would cause problems. Most likely the editor with which I develop Form will give even more problems and without it I can not even start thinking about Form.

Jos

On 13 Jan 2020, at 16:29, Andrés R Olivo notifications@github.com wrote:

Hello,

This is the first time I use form. Unfortunately, I am trying to work with form from macos catalina. I installed it successfully, but when I run make check I get the same error as @aerolivo https://github.com/aerolivo . I would like to ask if you find a solution to this issue. Thanks in advance.

Hello, sorry, I did not keep trying to solve it.

I installed FORM in a linux machine and I am working with it through ssh from the mac. (which is not a solution)

I don't know if someone has installed it successfully on Catalina.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/335?email_source=notifications&email_token=ABJPCESLFQXMFEEX6BQIJUDQ5SCFJA5CNFSM4JPULPDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIZEH2I#issuecomment-573719529, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJPCEXPDD4Z4I4MJ4KH5TLQ5SCFJANCNFSM4JPULPDA.

[go-mishima]

hello, in my case, it is possible to install FORM on MacOS Catalina successfully. I installed gcc9, autoconf, automake, cmake via MacPorts and that is basically all what I did. More precisely, I have clean installed Catalina and then installed the latest version of Xcode and then installed MacPorts in the usual way. Afterwards, (as I said above) I installed related stuff via MacPorts. I got the latest file by "git clone https://github..." and as usual, autoconf -i ./configure make make install. I tried some simple test codes and they worked.

[go-mishima]

...and "make check" says "All 2 tests passed".

[tueda]

I asked a student (@Tnagura) to try to build FORM, who uses a macOS Catalina laptop. The usual installation and make check succeeded, but he uses Homebrew and so I guess a brewed glib was used instead of the Apple's one. This could be a workaround to avoid Apple's problematic library.

[aerolivo]

Hello, I reinstalled FORM with the recommendations by @go-mishima. I was missing the cmake, so, I installed it, and now FORM works, all tests passed. Thanks.

[emivilla]

Hello, I have done the same. I reinstalled FORM following the procedure described by @go-mishima and now it works. Thank you all for the help.

[tueda]

Although the procedure with MacPorts seems to be a solution, I tried to seek the cause of this problem with Github Actions, which is now based on Catalina. One culprit is the compiler flag: here is a failed job while this job succeeded. The difference is setting COMPILEFLAGS=-O2. So, configuring with

./configure COMPILEFLAGS=-O2

might avoid the problem.

Edit: somehow COMPILEFLAGS='-Wall -Wextra -Wpadded -O3 -march=native' (i.e., without -fomit-frame-pointer) worked (log).

[jPhy]

The problem is gone with xcode11.3.1.