VERSION 2.3.3 Problems
I have downloaded version 2.3.3 and I tested a simple example:
generate p p > t t~ [QCD]
output TTBAR_TEST
launch TTBAR_TEST
However amc@NLO fails to compile:
INFO: Compiling on 8 cores
INFO: Compiling P0_gg_ttx...
INFO: Compiling P0_uxu_ttx...
INFO: Compiling P0_uux_ttx...
WARNING: fct <function compile_dir at 0x1036285f0> does not return 0. Starts to stop the code in a clean way.
WARNING: fct <function compile_dir at 0x1036285f0> does not return 0. Starts to stop the code in a clean way.
WARNING: fct <function compile_dir at 0x1036285f0> does not return 0. Starts to stop the code in a clean way.
WARNING: Fail to compile the Subprocesses
I am using OS X 10.11.1, Apple LLVM version 7.0.0 (clang-700.1.76), and gfortran from gcc version 4.9.2 (Homebrew gcc 4.9.2)
Many thanks
Luca
Question information
- Language:
- English Edit question
- Status:
- Open
- Assignee:
- marco zaro Edit question
- Last query:
- Last reply:
Revision history for this message
![]() |
#1 |
Hi,
Actually for your system, (10.11)
I would advise that you download the official binary of gfortran:
http://
I have use that one (I have the same config as you) and it is working nicely. (I never use homebrew which is as you can see not up-to-date)
Cheers,
Olivier
> On Nov 24, 2015, at 19:32, Luca <email address hidden> wrote:
>
> New question #275386 on MadGraph5_aMC@NLO:
> https:/
>
> I have downloaded version 2.3.3 and I tested a simple example:
>
> generate p p > t t~ [QCD]
> output TTBAR_TEST
> launch TTBAR_TEST
>
> However amc@NLO fails to compile:
>
> INFO: Compiling on 8 cores
> INFO: Compiling P0_gg_ttx...
> INFO: Compiling P0_uxu_ttx...
> INFO: Compiling P0_uux_ttx...
> WARNING: fct <function compile_dir at 0x1036285f0> does not return 0. Starts to stop the code in a clean way.
> WARNING: fct <function compile_dir at 0x1036285f0> does not return 0. Starts to stop the code in a clean way.
> WARNING: fct <function compile_dir at 0x1036285f0> does not return 0. Starts to stop the code in a clean way.
> WARNING: Fail to compile the Subprocesses
>
> I am using OS X 10.11.1, Apple LLVM version 7.0.0 (clang-700.1.76), and gfortran from gcc version 4.9.2 (Homebrew gcc 4.9.2)
>
> Many thanks
>
> Luca
>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
![]() |
#2 |
It still fails, with the same error. I have downloaded a new version from scratch and I recompiled everything. Now my compilers are
[rottoli@
Using built-in specs.
COLLECT_
COLLECT_
Target: x86_64-
Configured with: ../gcc-
Thread model: posix
gcc version 5.2.0 (GCC)
[rottoli@
Configured with: --prefix=
Apple LLVM version 7.0.0 (clang-700.1.76)
Target: x86_64-
Thread model: posix
Revision history for this message
![]() |
#3 |
Looks the same as me:
[@Oliviers-
Using built-in specs.
COLLECT_
COLLECT_
Target: x86_64-
Configured with: ../gcc-
Thread model: posix
gcc version 5.2.0 (GCC)
[@Oliviers-
Configured with: --prefix=
Apple LLVM version 7.0.0 (clang-700.0.72)
Target: x86_64-
Thread model: posix
Since you install other version of gfortran, please check that all linker are the correct one. In my case, I have:
[@Oliviers-
/opt/local/bin/ld
Cheers,
Olivier
> On Nov 24, 2015, at 21:57, Luca <email address hidden> wrote:
>
> Question #275386 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Luca is still having a problem:
> It still fails, with the same error. I have downloaded a new version
> from scratch and I recompiled everything. Now my compilers are
>
> [rottoli@
> Using built-in specs.
> COLLECT_
> COLLECT_
> Target: x86_64-
> Configured with: ../gcc-
> Thread model: posix
> gcc version 5.2.0 (GCC)
>
> [rottoli@
> Configured with: --prefix=
> Apple LLVM version 7.0.0 (clang-700.1.76)
> Target: x86_64-
> Thread model: posix
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
![]() |
#4 |
In my case I have:
[rottoli@
/usr/bin/ld
[rottoli@
@(#)PROGRAM:ld PROJECT:ld64-253.6
configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em (tvOS)
LTO support using: Apple LLVM 7.0.0 (clang-700.1.76)
I have nothing installed in /opt/local/
Luca
Revision history for this message
![]() |
#5 |
oh I have another one:
[@Oliviers-
@(#)PROGRAM:ld PROJECT:ld64-236.3
configured to support archs: i386 x86_64 x86_64h armv6 armv7 armv7s armv7m arm64
LTO support using: LLVM version 3.4
I also have the same as you:
@(#)PROGRAM:ld PROJECT:
configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em
LTO support using: Apple LLVM 7.0.0 (clang-700.0.72)
and I have tested using that one and it works nicely as well.
I’m assigning this to Marco, maybe he will have an additional idea.
Cheers,
Olivier
> On Nov 26, 2015, at 01:42, Luca <email address hidden> wrote:
>
> Question #275386 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Luca is still having a problem:
> In my case I have:
>
> [rottoli@
> /usr/bin/ld
> [rottoli@
> @(#)PROGRAM:ld PROJECT:ld64-253.6
> configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em (tvOS)
> LTO support using: Apple LLVM 7.0.0 (clang-700.1.76)
>
> I have nothing installed in /opt/local/
>
> Luca
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
![]() |
#6 |
I have run 2.3.2 (which I downloaded using bzr) and I have additional info running in debug mode:
gfortran -o test_ME symmetry_
Undefined symbols for architecture x86_64:
void std::__
[.....]
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status
make: *** [test_ME] Error 1
So it seems it may be a problem with fastjet. I have re-downloaded fastjet and recompiled it, but it looks like it is not finding it/linking it for some reason. I have set the fastjet path doing (in case it was not find automatically, it should be in my path)
set fastjet /usr/local/
Revision history for this message
![]() |
#7 |
Did you try without fastjet (then we use fjcore which is the core of fastjet)
Cheers,
Olivier
> On Nov 26, 2015, at 02:07, Luca <email address hidden> wrote:
>
> Question #275386 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Luca is still having a problem:
> I have run 2.3.2 (which I downloaded using bzr) and I have additional
> info running in debug mode:
>
> gfortran -o test_ME symmetry_
> Undefined symbols for architecture x86_64:
> "std::_
> __ZNSt3_
> void std::__
> std::__
> std::__
> std::__
>
>
> [.....]
>
> ld: symbol(s) not found for architecture x86_64
> collect2: error: ld returned 1 exit status
> make: *** [test_ME] Error 1
>
>
> So it seems it may be a problem with fastjet. I have re-downloaded fastjet and recompiled it, but it looks like it is not finding it/linking it for some reason. I have set the fastjet path doing (in case it was not find automatically, it should be in my path)
>
> set fastjet /usr/local/
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
![]() |
#8 |
If I don't link fastjet it works - so maybe it was a problem related to how it is built.
Apparently it looks to be a problem related to lstdc++ - I had some problems in the past with fastjet related to that and I managed to solve them using the suggestion in https:/
Now the problem seems to be lhapdf - I have to change lstdc++ -> lc++ since it couldn't compile, but I find another error...
libc++abi.dylib: terminating with uncaught exception of type LHAPDF_
Program received signal SIGABRT: Process abort signal.
Backtrace for this error:
#0 0x1091af092
#1 0x1091ae3b0
#2 0x7fff88c09529
libc++abi.dylib: terminating with uncaught exception of type LHAPDF_
Program received signal SIGABRT: Process abort signal.
Backtrace for this error:
#0 0x1106d4092
#1 0x1106d33b0
#2 0x7fff88c09529
libc++abi.dylib: terminating with uncaught exception of type LHAPDF_
Luca
Revision history for this message
![]() |
#9 |
BTW, thanks a lot for the suggestion to use fjcore! I didn't know it was shipped with the latest versions of amc@NLO
Can you help with this problem?
Provide an answer of your own, or ask Luca for more information if necessary.