#35542: petsc: :info:configure Fortran could not successfully link C++ objects ------------------------------------+--------------------------------------- Reporter: jmstephensjr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: petsc ------------------------------------+--------------------------------------- Comment(by jmstephensjr@…): Attaching ''configure.log'', found in ''/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_petsc/petsc/work/petsc-3.3-p2''. -- Ticket URL: <https://trac.macports.org/ticket/35542#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35542: petsc: :info:configure Fortran could not successfully link C++ objects ------------------------------------+--------------------------------------- Reporter: jmstephensjr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: petsc ------------------------------------+--------------------------------------- Comment(by mmoll@…): Does the attached patch of the petsc Portfile fix the problem? -- Ticket URL: <https://trac.macports.org/ticket/35542#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35542: petsc: :info:configure Fortran could not successfully link C++ objects ------------------------------------+--------------------------------------- Reporter: jmstephensjr@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: petsc ------------------------------------+--------------------------------------- Comment(by jmstephensjr@…): Replying to [comment:4 mmoll@…]:

Does the attached patch of the petsc Portfile fix the problem?

I want to make sure I am on the same page before I clobber anything. Here are the steps: 1. Copy ''Portfile.diff'' to ''/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/petsc'' 2. execute ''/usr/bin/patch Portfile < Portfile.diff'' Thanks. -- Ticket URL: <https://trac.macports.org/ticket/35542#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35542: petsc: :info:configure Fortran could not successfully link C++ objects ------------------------------------+--------------------------------------- Reporter: jmstephensjr@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: petsc ------------------------------------+--------------------------------------- Comment(by jmstephensjr@…): OK, I uninstalled slepc and deactivated petsc. I still have petsc @3.3-p0_0 installed, but not active. I ran the steps, and the upgrade failed. I have attached new logs. If you would like, I can completely uninstall petsc, run ''clean --all petsc'', and start with a fresh install. After it fails (how do you download only?), I will run the patch to the portfile, and try to reinstall, and give you an update. Note: as we are heading into Monday, I want to make clear that this is not urgent on my end... and of course, thanks for all your help. -- Ticket URL: <https://trac.macports.org/ticket/35542#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35542: petsc: :info:configure Fortran could not successfully link C++ objects ------------------------------------+--------------------------------------- Reporter: jmstephensjr@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: petsc ------------------------------------+--------------------------------------- Comment(by jmstephensjr@…): New error... ''Incomplete LAPACK install? Perhaps lapack package is installed - but lapack-dev/lapack-devel is required.'' Here is what I did. I already had ''hdf5-18 @1.8.9_0'' installed on account of ''octave''. I ran ''uninstall'' and ''clean --all'' on ''hdf5-18 @1.8.9_0'' and installed the gcc45 variant (which is the variant used in ''openmpi'', ''atlas'', etc). I then ran ''uninstall'' and ''clean --all'' on ''petsc'' and did a fresh install. I got the new error. Logs to follow. -- Ticket URL: <https://trac.macports.org/ticket/35542#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35542: petsc: :info:configure Fortran could not successfully link C++ objects ------------------------------------+--------------------------------------- Reporter: jmstephensjr@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: petsc ------------------------------------+--------------------------------------- Comment(by jmstephensjr@…): Success. Firstly, I deactivated ''atlas @3.10.0_0+gcc45'', which required that I also deactivate ''qrupdate @1.1.2_1+atlas+gcc45'' and ''octave @3.2.4_8+atlas+gcc45''. Secondly, I ran ''clean --all'' on ''petsc'' and did a fresh install. It failed. Thirdly, I applied ''Portfile.diff'' and tried again to install. This time it worked. I now have ''petsc @3.3-p2_1+openmpi (active)''. I will attached logs for your reference. What now? Does this mean that ''petsc'' is looking in the wrong place for LAPACK or is ''atlas'' writing the files in the wrong place? Should I open a ticket on ''atlas''? Can I reactivate the deactivated ports? -- Ticket URL: <https://trac.macports.org/ticket/35542#comment:12> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35542: petsc: :info:configure Fortran could not successfully link C++ objects ------------------------------------+--------------------------------------- Reporter: jmstephensjr@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: petsc ------------------------------------+--------------------------------------- Comment(by jmstephensjr@…): Replying to [comment:12 jmstephensjr@…]:

What now? Does this mean that ''petsc'' is looking in the wrong place for LAPACK or is ''atlas'' writing the files in the wrong place? Should I open a ticket on ''atlas''?

I went back and read your last comment again. I realize that you already answered the question. I will wait for an ''atlas'' and ''accelerate'' variant. -- Ticket URL: <https://trac.macports.org/ticket/35542#comment:14> MacPorts <http://www.macports.org/> Ports system for Mac OS

#35542: petsc: :info:configure Fortran could not successfully link C++ objects -----------------------------+--------------------- Reporter: jmstephensjr@… | Owner: mmoll@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: fixed | Keywords: Port: petsc | -----------------------------+--------------------- Changes (by mmoll@…): * status: new => closed * resolution: => fixed Comment: Should be fixed in r100485. -- Ticket URL: <https://trac.macports.org/ticket/35542#comment:16> MacPorts <http://www.macports.org/> Ports system for Mac OS