64 bit linking error
I'm trying to compile something using the macports openmpi (built on macports gcc48), and am getting the following linking error: openmpicxx -I/Users/gideon/software/sprng4.4/include -o sprng_mpi sprng_mpi.cpp -L/Users/gideon/software/sprng4.4/lib -lsprng -I/opt/local/include/openmpi -L/opt/local/lib -lmpi_cxx -lmpi Undefined symbols for architecture x86_64: std::ctypechar::_M_widen_init() const, referenced from: mult_48_32(int*, int*, int*) in libsprng.a(libsprng_a-lcg.o) operator(std::ostream, BigNum const) in libsprng.a(libsprng_a-bignum.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [sprng_mpi] Error 1 This is using a library called SPRNG (http://www.sprng.org), which I built on the macports gcc 48. Going through the listserv archives, there was something about this over 2 yeas ago, but it was unclear to me how/if it was resolved. -gideon ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Installed MacPorts 2.2.1, now to install Octave dependencies
I have installed the MacPorts 2.2.1 package and am interested in installing Octave and its dependencies. I thought I saw somewhere that Octave installs these dependencies automatically but that might have been an error. I have downloaded Octave 3.4.6 in a folder in my /users directory and am attempting to run it on Mavericks which I have heard has has a lot of issues with compatibility. The folders/files that I have in my /users directory are: 'man3-has files like LAPACK, BLAS,etc, 'ports' which has a 'devel' folder among many others, a 'Portfile.txt' that contains octave 3.2.4, also a 'readline', a 'gcc48', 'llvm-gcc48', gawk, and a 'math-BSD-atlas' set of Portfiles among others which I could acquire. I also have the 'octave 3.4.6' folder that contains many files and folders for installation, make, run, etc. I also have a 'general' folder and files, an 'audio' folder and files and a Portfile.txt file for DSDP. I believe that some combination of these files or file types must be installed, compiled, built and run to use Octave from the command line or from Xcode which I use regularly. Any suggestions on how to bring these tools together to use Octave would be greatly appreciated. Thank you for your time, Patrick ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installed MacPorts 2.2.1, now to install Octave dependencies
On Tue, Nov 26, 2013 at 3:56 PM, Patrick Hinkle avmac1...@gmail.com wrote: I have installed the MacPorts 2.2.1 package and am interested in installing Octave and its dependencies. I thought I saw somewhere that Octave installs these dependencies automatically but that might have been an error. I have downloaded Octave 3.4.6 in a folder in my /users directory and am attempting to run it Why? There is an octave port. Or, if you're just going to install stuff by hand, why bother with a package manager? -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installed MacPorts 2.2.1, now to install Octave dependencies
On Nov 26, 2013, at 15:43, Brandon Allbery wrote: On Tue, Nov 26, 2013 at 3:56 PM, Patrick Hinkle wrote: I have downloaded Octave 3.4.6 in a folder in my /users directory and am attempting to run it Why? There is an octave port. Or, if you're just going to install stuff by hand, why bother with a package manager? Well, the octave port is for version 3.2.x which is old and has some problems, including not working on Mavericks: https://trac.macports.org/ticket/41211 The octave-devel port is for version 3.6.x and is better; this should be used for now, if possible. This will be changed soon so that the octave port is for version 3.6.x. See https://lists.macosforge.org/pipermail/macports-dev/2013-November/025163.html ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: 64 bit linking error
On Nov 26, 2013, at 09:10, Gideon Simpson wrote: I'm trying to compile something using the macports openmpi (built on macports gcc48), and am getting the following linking error: openmpicxx -I/Users/gideon/software/sprng4.4/include -o sprng_mpi sprng_mpi.cpp -L/Users/gideon/software/sprng4.4/lib -lsprng -I/opt/local/include/openmpi -L/opt/local/lib -lmpi_cxx -lmpi Undefined symbols for architecture x86_64: std::ctypechar::_M_widen_init() const, referenced from: mult_48_32(int*, int*, int*) in libsprng.a(libsprng_a-lcg.o) operator(std::ostream, BigNum const) in libsprng.a(libsprng_a-bignum.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [sprng_mpi] Error 1 This is using a library called SPRNG (http://www.sprng.org), which I built on the macports gcc 48. Going through the listserv archives, there was something about this over 2 yeas ago, but it was unclear to me how/if it was resolved. What version of OSX? If Mavericks, you may be having the problem that you cannot mix software compiled with libc++ (i.e. anything compiled with clang) with software compiled with libstdc++ (i.e. anything compiled with FSF GCC). ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: 64 bit linking error
This is 10.8, not mavericks. -gideon On Nov 26, 2013, at 7:42 PM, Ryan Schmidt ryandes...@macports.org wrote: On Nov 26, 2013, at 09:10, Gideon Simpson wrote: I'm trying to compile something using the macports openmpi (built on macports gcc48), and am getting the following linking error: openmpicxx -I/Users/gideon/software/sprng4.4/include -o sprng_mpi sprng_mpi.cpp -L/Users/gideon/software/sprng4.4/lib -lsprng -I/opt/local/include/openmpi -L/opt/local/lib -lmpi_cxx -lmpi Undefined symbols for architecture x86_64: std::ctypechar::_M_widen_init() const, referenced from: mult_48_32(int*, int*, int*) in libsprng.a(libsprng_a-lcg.o) operator(std::ostream, BigNum const) in libsprng.a(libsprng_a-bignum.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [sprng_mpi] Error 1 This is using a library called SPRNG (http://www.sprng.org), which I built on the macports gcc 48. Going through the listserv archives, there was something about this over 2 yeas ago, but it was unclear to me how/if it was resolved. What version of OSX? If Mavericks, you may be having the problem that you cannot mix software compiled with libc++ (i.e. anything compiled with clang) with software compiled with libstdc++ (i.e. anything compiled with FSF GCC). ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
