Page 1 of 1

new version of mark executable for OS/X

PostPosted: Thu Jul 09, 2015 9:16 am
by cooch
Can be grabbed here: http://www.phidot.org/software/mark/rmark/linux/

Latest and greatest source. Should play nicely with latest RMark build. Usual caveats about 'you download it, you figure out how to make it work'. There is a fair bit of good advice on the download page, and elsewhere in the forum, on how to get things to work.

Couple of notes:

1\ 64-bit only.

2\ you'll need at least gfortran 4.8 installed on your Mac. I compiled it with 4.9, but 4.8 libs should support things. If not, update to 4.9.

3\ multi-processor support seems to be working as it should.

4\ remember, this is not GUI-based MARK 'classic', but rather, a standalone binary for the MARK executable, which contains all the 'numerical' routines that MARK uses. For the vast majority of users, you will use RMark as the 'front-end' to the executable.

Re: new version of mark executable for OS/X

PostPosted: Mon Aug 24, 2015 8:10 pm
by aber_r16
Coach - Thanks for releasing the next Mark executable for OS/X!

Understanding the usual caveats "you download it, you figure out how to make it work", putting a shout out to anyone on the forum who has it working to ponder my issue...

As the website hints, I think it has to do with where mark is looking for the gfortran libraries.

$ otool -L /usr/local/bin/mark (of the binary that isn't working)
/usr/local/bin/mark:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)
/usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/local/lib/libquadmath.0.dylib (compatibility version 1.0.0, current version 1.0.0)

but these libraries are in the usr/local/gfortran/lib directory.

In the previous install of the mark file that I did have working, mark looked for the libraries in the correct place.

$otool -L /usr/local/bin/mark (of the binary that is working)
/usr/local/bin/mark:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
/usr/local/gfortran/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/local/gfortran/lib/libquadmath.0.dylib (compatibility version 1.0.0, current version 1.0.0)


The website does continue to offer

"You can LDD the MARK executable to find out what it 'requires', then tweak the LD_LIBRARY_PATH as needed (if the preceding sentence doesn't make sense to you, you should either quit now, and ask a local 'guru' for help... ;-)"

Can anyone talk me through how to do that?

Thanks, Robin

Re: new version of mark executable for OS/X

PostPosted: Mon Aug 24, 2015 9:04 pm
by cooch
aber_r16 wrote:Coach - Thanks for releasing the next Mark executable for OS/X!

Understanding the usual caveats "you download it, you figure out how to make it work", putting a shout out to anyone on the forum who has it working to ponder my issue...

As the website hints, I think it has to do with where mark is looking for the gfortran libraries.

$ otool -L /usr/local/bin/mark (of the binary that isn't working)
/usr/local/bin/mark:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)
/usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/local/lib/libquadmath.0.dylib (compatibility version 1.0.0, current version 1.0.0)

but these libraries are in the usr/local/gfortran/lib directory.

In the previous install of the mark file that I did have working, mark looked for the libraries in the correct place.

$otool -L /usr/local/bin/mark (of the binary that is working)
/usr/local/bin/mark:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
/usr/local/gfortran/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/local/gfortran/lib/libquadmath.0.dylib (compatibility version 1.0.0, current version 1.0.0)


The website does continue to offer

"You can LDD the MARK executable to find out what it 'requires', then tweak the LD_LIBRARY_PATH as needed (if the preceding sentence doesn't make sense to you, you should either quit now, and ask a local 'guru' for help... ;-)"

Can anyone talk me through how to do that?

Thanks, Robin


Google is your friend. Try reading on

Code: Select all
 export LD_LIBRARY_PATH=someValue


as a starting point.