Re: dolfin issue
Gideon Simpson writes: > I did a port uninstall and a port clean, and I got the same error. Huh. I'll try to reproduce this, then. > I do have petsc/slepc installed with mpich, if that’s part of the problem. I > suspect that petsc is built as a C library, while dolfin is C++. Perhaps > that’s the incompatibility? It's perfectly fine to link C to C++. Dolfin has been doing this with PETSc for years. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: dolfin issue
I did a port uninstall and a port clean, and I got the same error. I do have petsc/slepc installed with mpich, if that’s part of the problem. I suspect that petsc is built as a C library, while dolfin is C++. Perhaps that’s the incompatibility? -gideon On Sep 30, 2014, at 2:35 AM, Sean Farley wrote: > > Ryan Schmidt writes: > >> On Sep 29, 2014, at 7:45 PM, Gideon Simpson wrote: >>> >>> I don’t seem to have that file >> >> Ok, looks like the compiler name is just being specified as >> "mpicc-mpich-mp", without a path, and cmake is incorrectly inferring that it >> is in the build directory. >> >> Do you have any of the mpich ports installed? >> >> port installed name:mpich >> >> Do any of them provide this file? > > The issue is that dolfin needs a clean configure. I don't know why it > has trouble with this (do any cmake people know?). Try 'port clean > dolfin' before attempting to build dolfin again. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: dolfin issue
Ryan Schmidt writes: > On Sep 29, 2014, at 7:45 PM, Gideon Simpson wrote: >> >> I don’t seem to have that file > > Ok, looks like the compiler name is just being specified as "mpicc-mpich-mp", > without a path, and cmake is incorrectly inferring that it is in the build > directory. > > Do you have any of the mpich ports installed? > > port installed name:mpich > > Do any of them provide this file? The issue is that dolfin needs a clean configure. I don't know why it has trouble with this (do any cmake people know?). Try 'port clean dolfin' before attempting to build dolfin again. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: dolfin issue
On Sep 29, 2014, at 7:45 PM, Gideon Simpson wrote: > > I don’t seem to have that file Ok, looks like the compiler name is just being specified as "mpicc-mpich-mp", without a path, and cmake is incorrectly inferring that it is in the build directory. Do you have any of the mpich ports installed? port installed name:mpich Do any of them provide this file? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: dolfin issue
I don’t seem to have that file -gideon On Sep 29, 2014, at 8:00 PM, Ryan Schmidt wrote: > > On Sep 29, 2014, at 3:48 PM, Gideon Simpson wrote: > >> The following combination generated an error: >> sudo port install dolfin +mpich +petsc +slepc +suitesparse >> ---> Computing dependencies for libgcc >> ---> Cleaning libgcc >> ---> Computing dependencies for dolfin >> ---> Configuring dolfin >> Error: org.macports.configure for port dolfin returned: configure failure: >> command execution failed >> Please see the log file for port dolfin for details: >> >> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_dolfin/dolfin/main.log >> To report a bug, follow the instructions in the guide: >>http://guide.macports.org/#project.tickets >> Error: Processing of port dolfin failed >> > > Hmm, it says: > > > :info:configure The CMAKE_CXX_COMPILER: > :info:configure > :info:configure > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_dolfin/dolfin/work/dolfin-1.4.0/build/mpicxx-mpich-mp > :info:configure > :info:configure is not a full path to an existing compiler tool. > > > Does > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_dolfin/dolfin/work/dolfin-1.4.0/build/mpicxx-mpich-mp > exist? Does it work? Is it perhaps a broken symlink? > > ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
