[MacPorts] #25186: arpack-1 Configure error - build failure
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: ------------------------------------+--------------------------------------- When installing arpack using: {{{ sudo port install arpack }}} the build fails and reports that there were undefined symbols. Some of these symbols are functions from blas, which is found in vecLib framework. I do have vecLib installed, so I am assuming that arpack is not linking to the vecLib framework properly. I am running: * Darwin 10.3.0 (from OS X Snow Leopard) * Xcode 3.2.2 * gcc-4.4 -- Ticket URL: <http://trac.macports.org/ticket/25186> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: ------------------------------------+--------------------------------------- Comment(by laurence@…): The error is reported as: {{{ shell command "cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_arpack/work/ARPACK && /usr/bin/ld -arch x86_64 -dynamic -dylib -single_module -dead_strip -x -all_load -L. -L/opt/local/lib/gcc44/x86_64 -L/opt/local/lib/gcc44 -L/opt/local/lib -dylib_install_name /opt/local/lib/libarpack.1.dylib -current_version 1 -compatibility_version 1 libarpack.a -o libarpack.1.dylib -latlas -llapack -lgfortran -lSystem" returned error 1}}} I have found that this error can be fixed by adding {{{-framework vecLib}}} to the end of the linking command. This changes the linking command from: {{{/usr/bin/ld -arch x86_64 -dynamic -dylib -single_module -dead_strip -x -all_load -L. -L/opt/local/lib/gcc44/x86_64 -L/opt/local/lib/gcc44 -L/opt/local/lib -dylib_install_name /opt/local/lib/libarpack.1.dylib -current_version 1 -compatibility_version 1 libarpack.a -o libarpack.1.dylib -latlas -llapack -lgfortran -lSystem}}} to {{{/usr/bin/ld -arch x86_64 -dynamic -dylib -single_module -dead_strip -x -all_load -L. -L/opt/local/lib/gcc44/x86_64 -L/opt/local/lib/gcc44 -L/opt/local/lib -dylib_install_name /opt/local/lib/libarpack.1.dylib -current_version 1 -compatibility_version 1 libarpack.a -o libarpack.1.dylib -latlas -llapack -lgfortran -lSystem -framework vecLib }}} -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: arpack ------------------------------------+--------------------------------------- Changes (by jmr@…): * owner: macports-tickets@… => mmoll@… * port: => arpack Comment: Please remember to fill in the Port field and cc the maintainer. -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: arpack ------------------------------------+--------------------------------------- Comment(by laurence@…): I have attached a patch {{{arpack.Portfile.patch}}} that lead to arpack compiling on my machine. -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: arpack ------------------------------------+--------------------------------------- Comment(by mmoll@…): I have exactly the environment as you and arpack installs fine for me (I just re-installed). There *has* to be some difference between your setup and mine. Can you attach the output of "port -dv install arpack +gcc44"? Also, can you check if instead of you change, adding "-lblas" to line 98 also fixes the bug? -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: arpack ------------------------------------+--------------------------------------- Comment(by adfernandes@…): Replying to [comment:4 mmoll@…]:
I have exactly the environment as you and arpack installs fine for me (I just re-installed). There *has* to be some difference between your setup and mine. Can you attach the output of "port -dv install arpack +gcc44"? Also, can you check if instead of you change, adding "-lblas" to line 98 also fixes the bug?
Hi, `mmoll` - I have exactly the same build problem as `laurence`, and his patch fixed it for me. (Same computer/os/compiler, too.) Been wondering what the problem was. I created specific patch based on `laurence`'s submission. Fixed it for me. -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: arpack ------------------------------------+--------------------------------------- Comment(by mmoll@…): I committed a possible fix in r68674. Please let me know if it works. -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: arpack ------------------------------------+--------------------------------------- Comment(by adfernandes@…): I reverted and built using `mmoll`'s r68674, and it works for me. Thanks! I'm guessing you can close this now. Now to try and figure out why `octave` won't use `arpack`, as per #24476. -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure ------------------------------------+--------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Keywords: | Port: arpack ------------------------------------+--------------------------------------- Comment(by laurence@…): Works for me too. Thanks. -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure -------------------------------------+-------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Resolution: fixed | Keywords: Port: arpack | -------------------------------------+-------------------------------------- Changes (by mmoll@…): * status: new => closed * resolution: => fixed -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS
#25186: arpack-1 Configure error - build failure -------------------------------------+-------------------------------------- Reporter: laurence@… | Owner: mmoll@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.0 Resolution: fixed | Keywords: Port: arpack | -------------------------------------+-------------------------------------- Comment(by takeshi@…): arpack should depend on atlas if -lblas and -llapack is used or link agains vecLib as have already been suggested. I attached a yet another patch. Octave uses arpack. Octave now depends on atlas, probably due to the problem with the *dot* problem arising from ABI differences ([http://developer.apple.com/hardwaredrivers/ve/errata.html#fortran_convention... solution]). Since atlas always takes long time to build and sometime falis I have tried to make vecLib back. See #21797. -- Ticket URL: <http://trac.macports.org/ticket/25186#comment:12> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts