Manual update to iXAFS
Hi Bruce, Regards from a far too hot Japan, Thanks for the update suggestions for iXAFS Bruce. I managed to get it to work, but I found a couple of problems. 1. There is another intermediate directory in your steps (3,4,5), e.g. " /Applications/iXAFS/Contents/Resources/bin" should read " /Applications/iXAFS/Contents/Resources/Horae/bin" The intermediate directory Horae is missing in each case. 2. SVN is installed by default on the Mac. When I tried to run the mkartemis.pl and friends after downloading the latest svn release, however, I found that the rc.pl files were missing. How does one generate these from the svn files? I used a rc.pl from a horae-70 release I had around and it apparently worked. 3. The version numbers in the SVN release conflict within the files from the SVN (at least when following the procedure you mentioned above). Some of the files from the SVN release have (ArtemisLog) $VERSION set to 0.8.014 while others (e.g. Group.pm had $VERSION = "0.0.8.061"). This triggers an error in the athena and artemis of a version mismatch. I "fixed" this by disabling the check, as the logic of the versioning is not very clear from a simple examination of the files. What should the "$VERSION" string (and any other version related strings) be set to in each of the files? In any case it work, but it sure would be nice to have a nice new official release! paul
On Tuesday 31 August 2010 02:19:50 am Paul Fons wrote:
Hi Bruce, Regards from a far too hot Japan,
Thanks for the update suggestions for iXAFS Bruce. I managed to get it to work, but I found a couple of problems.
1. There is another intermediate directory in your steps (3,4,5), e.g. " /Applications/iXAFS/Contents/Resources/bin" should read " /Applications/iXAFS/Contents/Resources/Horae/bin" The intermediate directory Horae is missing in each case.
Thanks for catching that. Obviously, I was not cutting and pasting when I wrote that email.
2. SVN is installed by default on the Mac. When I tried to run the mkartemis.pl and friends after downloading the latest svn release, however, I found that the rc.pl files were missing. How does one generate these from the svn files? I used a rc.pl from a horae-70 release I had around and it apparently worked.
Good point. Again, I was doing this while sitting next to my normal computer -- this is one of the inevitable gaps. The files rc.pl for both programs normally get generated at the "perl Build.PL" stage of the installation (as do the files in the bin/ folder). So you can either just run "perl Build.PL" or run the scripts mkathenarc.PL and mkartemisrc.PL by hand. Given that one, in fact, can upgrade the iXAFS installation by hand starting from an svn export, it would be really great to have a script that does all the steps to do the iXAFS update. Given that, I could incorporate it into the Build.PL file. Then you could imagine updating by doing an "svn export" followed by "perl Build.PL" followed by "perl iXAFS-install" (or some such). Given that svn and perl are already on the computer, that would be a relatively low impact avenue to an update.
3. The version numbers in the SVN release conflict within the files from the SVN (at least when following the procedure you mentioned above). Some of the files from the SVN release have (ArtemisLog) $VERSION set to 0.8.014 while others (e.g. Group.pm had $VERSION = "0.0.8.061"). This triggers an error in the athena and artemis of a version mismatch. I "fixed" this by disabling the check, as the logic of the versioning is not very clear from a simple examination of the files. What should the "$VERSION" string (and any other version related strings) be set to in each of the files?
There has to be some confusion here. What you describe cannot possibly be correct as written. Running from a terminal window, what is written to the terminal when you see this conflict? The way it works is that $VERSION for athena and Groups.pm have to match, and $VERSION from artemis, Path.pm, ArtemisLog.pm, and Parameter.pm have to match. But one group does not have to match the other.
In any case it work, but it sure would be nice to have a nice new official release!
I concur, but it would be nice to have an updater to incorporate into the Build script. Any takers? It doesn't even need to be written in perl (althoguh that would be easier to maintain). B -- Bruce Ravel ------------------------------------ bravel@bnl.gov National Institute of Standards and Technology Synchrotron Methods Group at NSLS --- Beamlines U7A, X24A, X23A2 Building 535A Upton NY, 11973 My homepage: http://xafs.org/BruceRavel EXAFS software: http://cars9.uchicago.edu/~ravel/software/exafs/
I believe that Bruce is correct in that an updater incorporated into a build script would be the proper way to update the iXAFS code. The cocoa code for iXAFS is very simple and rarely needs updating. Jeff On Aug 31, 2010, at 9:07 AM, Bruce Ravel wrote:
On Tuesday 31 August 2010 02:19:50 am Paul Fons wrote:
other.
In any case it work, but it sure would be nice to have a nice new official release!
I concur, but it would be nice to have an updater to incorporate into the Build script. Any takers? It doesn't even need to be written in perl (althoguh that would be easier to maintain).
B
--
Hi, I have made a little progress understanding and getting Ken McIvor's iXAFS build scripts to run on my Macbook Pro. I have not yet tackled a full 64-bit version, but have managed to get it to compile ifeffit 1.2.11c and everything up to horae, including Tk and PGPLOT. I could not get horae-066 to build from source, but did not pursue this in detail, as it is not the goal. I could also not get horae-070 to build cleanly from source, but I now believe that to not be a Mac-specific problem, but that horae-070.tar.gz is simply broken for building on clean machines. I will try the svn version today, and try to alter Ken's build script for the new horae build system. As I was looking at this, I also noticed several oddities in the layout, and will try to improve these (make them more like the Unix and Windows layouts). That is, iXAFS.app/Contents/Resources/Horae/lib/perl5 should become iXAFS.app/Contents/Library/perl5 and iXAFS.app/Contents/Resources/Horae/share/ifeffit should become iXAFS.app/Contents/Library/ifeffit I will also try to add the python module directly to iXAFS.app. I don't know what the best approach for making a Mac-specific updater is, as the updaters we've done in the past are fully encapsulated binaries. It is also definitely worth considering packaging an entire perl distribution under iXAFS.app. --Matt
On Tuesday 31 August 2010 10:42:02 am Matt Newville wrote:
I could also not get horae-070 to build cleanly from source, but I now believe that to not be a Mac-specific problem, but that horae-070.tar.gz is simply broken for building on clean machines.
Matt, Could I have a bit more information on what the problem is? B -- Bruce Ravel ------------------------------------ bravel@bnl.gov National Institute of Standards and Technology Synchrotron Methods Group at NSLS --- Beamlines U7A, X24A, X23A2 Building 535A Upton NY, 11973 My homepage: http://xafs.org/BruceRavel EXAFS software: http://cars9.uchicago.edu/~ravel/software/exafs/
Hi Bruce, OK, I tracked this down to a problem I was having with CPAN versus the system perl installation (on linux anyway). Somehow, doing
perl -MCPAN 'install Bundle::XasPerlBundle'
was not completing correctly. For one thing, this takes an insanely long time as it builds and tests, and "cleverly" rebuilds the CPAN code and about 400 modules, all going into a system folder: yikes. But I don't think that was the problem. I believe it was more likely related to piles of messages about YAML, but I can't reproduce the problem easily. That's because, a second
perl -MCPAN 'install Bundle::XasPerlBundle'
did build and install several more components, including rebuilding
and retesting Tk. Sheesh.
Then horae-070 did build from the top-level directory. It appears to
be working.
But that's not going to stop me complaining about perl.
OK, that was a half a day.... Now back to OS X and trying to build
perl and horae there...
--Matt
On Tue, Aug 31, 2010 at 10:07 AM, Bruce Ravel
On Tuesday 31 August 2010 10:42:02 am Matt Newville wrote:
I could also not get horae-070 to build cleanly from source, but I now believe that to not be a Mac-specific problem, but that horae-070.tar.gz is simply broken for building on clean machines.
Matt,
Could I have a bit more information on what the problem is?
B
--
Bruce Ravel ------------------------------------ bravel@bnl.gov
National Institute of Standards and Technology Synchrotron Methods Group at NSLS --- Beamlines U7A, X24A, X23A2 Building 535A Upton NY, 11973
My homepage: http://xafs.org/BruceRavel EXAFS software: http://cars9.uchicago.edu/~ravel/software/exafs/ _______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit
participants (4)
-
Bruce Ravel
-
Jeff Terry
-
Matt Newville
-
Paul Fons